Server may be too busy

  • Thread starter Thread starter brian street
  • Start date Start date
B

brian street

Hello everyone,

I'm fairly new to Windows and I have a client that asked
me to switch their router out; they upgraded from IDSL to
ADSL and didn't know what to do.

I went over and established the internet connection with
the new router and line but a screwy thing appeared to
happen - the Terminal Server will only let 1 client
connect through the VPN. I don't think this has anything
to do with Terminal Services (the error says the server
may be too busy and to try again later - quite generic I
understand) since I didn't make any changes to it, but I
just don't know.

The major change with the router swap was the internal IP
range; it was 192.168.0.x and now is 192.168.1.x and I'm
thinking the problem is either with that swap or the
router itself (Netopia Cayman model 3341) but I can't find
any documentation to support either conclusion.

Any ideas on how to isolate the Terminal Server? I am able
to establish local VPN connections (internal network) but
only 1 external connection.

Thanks,
Brian.
 
Is there an eventlog message on the Terminal Server, when users aren't able
to connect?

Rob
 
There is no event logged when the users receive the server
too busy error.

After some more troubleshooting I'm leaning toward a
bandwidth issue. The main site is 384kb and the remote
sites are 144kb.

Can this be a timeout issue?

Brian.
 
Back
Top