G
Guest
I have an odd Terminal Server question. We have a small 2 site point to
point PIX VPN. There is a terminal server and a file server in Boston.
(Both are Windows 2000 Server SP 3, NO exchange).
In Roxbury users connect to the Terminal server fine that are running
Windows 2000 workstation through the tunnel. There is one machine that
recently was replaced with a Windows XP box. RDC to the IP address for the
terminal server ends with an error and does not connect on this one machine.
The user does not know if it ever connected since it was replaced, she is not
sure. From that machine you can ping the terminal server and open shares
from the terminal server, just can't rdc to it.
Is there some kind of compatibility issue with Windows XP Pro client going
to an older Windows 2000 server back end terminal server?
Let me know if you have any ideas.
point PIX VPN. There is a terminal server and a file server in Boston.
(Both are Windows 2000 Server SP 3, NO exchange).
In Roxbury users connect to the Terminal server fine that are running
Windows 2000 workstation through the tunnel. There is one machine that
recently was replaced with a Windows XP box. RDC to the IP address for the
terminal server ends with an error and does not connect on this one machine.
The user does not know if it ever connected since it was replaced, she is not
sure. From that machine you can ping the terminal server and open shares
from the terminal server, just can't rdc to it.
Is there some kind of compatibility issue with Windows XP Pro client going
to an older Windows 2000 server back end terminal server?
Let me know if you have any ideas.