RRAS on Terminal Server troubles - any diagnoses?
David Corwin Shackelford
I've got a machine (128mb RAM, 400mhz P-III) running Terminal Server (SP4)
and am using the RRAS version of RAS to allow remote users into my network.
I'm using an 8-port DigiBoard and have the ports divided between an outgoing
modem pool (using Spartacom SAPS) and an incoming pool.
Lately, users have been sporadically unable to connect to the modem pool,
even though they hear the carrier and connection. There is a "No server
available" message, or something to that effect. Other times users connect,
but are unable to reach any network resources. Today I had a user ping some
different machines, and while the RAS server itself could be pinged by the
client, other servers on the LAN only return one successful ping out of
four, always the first ping. If the client disconnects and calls back a few
times, eventually he gets full connectivity, despite coming in on the same
phone line.
Terminal client connections have started to hang, and the RPC service ends
up locking up and most functionality at the console is then unavailable. I
look for memory leaks or evidence of an RPC attack or some other DoS, but
processor and memory utilization on the machine remain very very low (near
8%). If I reboot the machine, things are fine for a while for terminal
sessions, RAS sessions are still patchy, and performance deterioration for
terminal clients eventually sets in.
Loading Service Pack 4 didn't seem to change things much.
Anybody had any experience with problems like this?
Dave Shackelford
Network Engineer