[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference chefs::ms-exchange

Title:Microsoft Exchange Server
Notice:
Moderator:FLASK2::SYSTEM
Created:Fri Feb 17 1995
Last Modified:Thu Jun 05 1997
Last Successful Update:Thu Jun 05 1997
Number of topics:1099
Total number of notes:5174

948.0. "Remote Access Clients Hang" by HYDRA::KLIGER () Fri Mar 21 1997 00:34

    We have a number of users that are experiencing problems using Exchange
    over dialup lines.  The Clients will sporadically hang and they will
    have to CTRL-Alt-Del to 'end the task' and restart.  Other Network
    applications do not seem to be affected (Netscape, terminal emulators,
    etc.).  
    
    This seems to be happening primarily to users coming in on PPP lines 
    although that may be because more of our users use PPP than RAS.
    
    We are running Exchange Server V4.0 with SP3.  
    
    Are other people experiencing these problems?  Is there a know fix?
T.RTitleUserPersonal
Name		DateLines
948.1modem card driversMUDGEE::ZORBASNULL JuniorFri Mar 21 1997 04:325
    try reinstalling the drivers for your modem card.
    
    cheers,
    
    Stuart
948.2we all hang togetherLEXS01::PUCHRIKField RatFri Mar 21 1997 13:1515
    Sidebar:  Most people are using PPP when they use RAS.  Or are you
    trying to distinguish between dialing into a DEChub 900 or a RAS
    server?
    
    I assume your clients are running the updated (SP2, SP3) Exchange
    clients.  The fact that your clients' systems can still run Netscape and
    other apps with only Exchange hanging seems to point to the Exchange
    server and not a network driver.  Any bottlenecks on the server?  Is
    there sufficient memory, cpu, and I/O?  Is there anything funny about
    the network where the server is located? (an overloaded site?)
    
    That being said I use Exchange morning and night every day.  I
    frequently have Exchange hangs and have to snuff the process.  The
    Close Program box shows Exchange "not responding".  My server is
    DASEXC1 (Dascomb Road).
948.3MUDGEE::ZORBASNULL JuniorFri Mar 21 1997 14:494
    Sometimes you just need to wait a few minutes for a 'not responding' to
    clear up. But as they say "when in doubt, reboot".
948.4CRC errors makes Exchange stop respondingPTOSS1::BREZLERWed Jun 04 1997 23:5018
    I, too, am experiencing this problem. I am dialing into the PTO office
    using PPP thru a DECserver 700. I had this problem on my desktop W95
    and couldn't explain it. Now that I have switched to WNT 4.0, I am
    using the Dial-Up Networking Monitor to check errors and find that this
    "hanging" feature on Exchange comes from unwanted CRC errors. I have
    eliminated my phone lines because I have experienced the problem from
    several different telephone exchanges. Also, when I get the CRC errors
    they seem to have little effect on KEA and Netscape. But they
    absolutely shut down Exchange.
    
    It would seem that this is a little unknown to the CCS support folks.
    At times I really want to throw my desktop unit onto the ground and go
    golfing....it is very difficult to work in this environment.
    
    I'd appreciate anyone else who can give some indication as to what kind
    of errors they are getting when Exchange stops responding.
    
    Gil