Strange Terminal Server problem
- From: "Mike" <google@xxxxxxxxxxxxxxx>
- Date: 16 Sep 2005 13:00:27 -0700
Hi,
I have two terminal servers on a private network. One TS is running on
Win2k, the other on Win2k3. Both are on a private network that can be
accessed from the outside through a VPN.
Sometimes, the Win2k3 TS will not allow connections from the outside
when a user is on a Windows machine, but if the user is running Linux,
or MacOS, they can connect fine, and users on the private network (not
connecting through the VPN) can connect fine.
It doesn't appear to be a VPN issue because:
I can ping the Win2k3 TS.
I can telnet to port 3389 on the Win2k3 TS.
I can connect to the Win2k TS through the VPN
I can use a Linux or MAC Remote Desktop client to connect to the Win2k3
TS
We are not running out of CALs, and the system isn't running out of
recourses/memory.
The only fix we've found it to reboot the Win2k3 TS, which obviously is
not a real good solution, so I'm looking for a better one...
Anyone ever run into anything similar? Any advice?
Thanks,
Mike
.
- Follow-Ups:
- Re: Strange Terminal Server problem
- From: Jeff Pitsch
- Re: Strange Terminal Server problem
- From: Vera Noest [MVP]
- Re: Strange Terminal Server problem
- Prev by Date: Re: No Remote tab on Win2K Server Properties
- Next by Date: Re: Strange Terminal Server problem
- Previous by thread: No Remote tab on Win2K Server Properties
- Next by thread: Re: Strange Terminal Server problem
- Index(es):
Relevant Pages
|