Our company has two locations. We have a dedicated ISDN line with two CISCO-802 ISDN routers connecting the two locations to create a WAN. One PC at the main site is set up with Windows NT 4.0 Terminal Server, where some of the users from the remotelocation log in to run a database application. Everything has been working just fine for several years, but suddenly last week the remote users could not log into the Terminal server. The message they get is: ?The Client could not connect to Terminal Server. The server may be too busy. Please try connect later.? I have no problems connect to the terminal server with a client locally over the LAN. The remote users have no problems accessing mapped drives on the PC acting as Terminal Server, or any of the other servers. The phone company have checked the ISDN line and found them OK. CISCO cannot find anything wrong in the routers either. I even reformatted the Terminal server?s hard disk and reinstalled Windows NT Server & terminal server. Also tried a new NIC.
Does anyone here have this happen to his or her Terminal server setup, or know what could cause this sudden connection problem?
Thank you,
Gus Skiaker
Titan Inc.