Cannot anymore connect on TS 2003 from remote office
- From: OxygeN <SPAMbonnyfusedSPAM@xxxxxxxxxxxxxxxxx>
- Date: Tue, 18 Mar 2008 17:35:22 +0100
Hello there.
It'll be a slightly long description, but it is a complicated issue and I don't know how to solve it. Let's start...
Got a Windows 2003 Server (SP2 and almost the latest updates installed) which is being used as a Terminal Server. I got a bunch of 20 clients in LAN connecting without any troubles (Win95 clients). Same sort of clients (Win95 with RDP client) are being used in a remote office on a different subnet (Class C). All has been working fine since someday in the morning the users started their clients and got no connection to the Terminal Server. I checked today with some GUI netstat and I could see that the connection *is being created*, but after some time it fades out (maybe timeout). Using a Windows Vista client on that remote subnet works well: got connected immediately.
Using a client from the remote site in the main offices' LAN also works ok.
Using a client from the LAN (same Win95 config) at the remote site DOESN'T WORK at all.
I don't feel like it's a networking issue, but *where* could the lack be sitting? Server has also been rebooted... I was thinking about the Terminal Server License Service: it has some 6 free licenses available.
Changed also NIC on the remote client...
Don't know where to look for. Any help will be appreciated.
Thanks.
.
- Prev by Date: Re: Client printing problems
- Next by Date: Windows Server 2008, TS Web Access: Problems with ActiveX
- Previous by thread: TS 2003 stops processing Group Policy
- Next by thread: Windows Server 2008, TS Web Access: Problems with ActiveX
- Index(es):
Relevant Pages
|