-
1
- #1
The specs:
W2K SP2 DC running terminal server licensing
W2K SP3 Member server running Terminal Service Server
Cisco VPN dialer 3.03
Terminal Server client
Cisco PIX 506 Firewall
Clients:
2 Win XP
1 WIN MILL
Problem:
We use terminal services through a ipsec Tunnel. There are six client that connect to the terminal server. However three of the clients are having problem connecting to the terminal server. The weird thing is that three of us are connecting fine and some of us are using almost the same specs that some of the people that are not able to connect. such as ISP and operating system. Clients that have a issue connecting are able to connect when I removed the registry keys under MSLincensing. Yet, when they disconnect and try to connect again the problems appears and the only way to connect again is if I remove those keys. Now this problems does not exist if they are connecting to the terminal sever inside the network. I have tried almost everything and Microsoft and Cisco are investigating this weird problem but in the mean time just wanted to see if anybody here have had similar experience.
Thanks,
Javy
W2K SP2 DC running terminal server licensing
W2K SP3 Member server running Terminal Service Server
Cisco VPN dialer 3.03
Terminal Server client
Cisco PIX 506 Firewall
Clients:
2 Win XP
1 WIN MILL
Problem:
We use terminal services through a ipsec Tunnel. There are six client that connect to the terminal server. However three of the clients are having problem connecting to the terminal server. The weird thing is that three of us are connecting fine and some of us are using almost the same specs that some of the people that are not able to connect. such as ISP and operating system. Clients that have a issue connecting are able to connect when I removed the registry keys under MSLincensing. Yet, when they disconnect and try to connect again the problems appears and the only way to connect again is if I remove those keys. Now this problems does not exist if they are connecting to the terminal sever inside the network. I have tried almost everything and Microsoft and Cisco are investigating this weird problem but in the mean time just wanted to see if anybody here have had similar experience.
Thanks,
Javy