Cannot log onto Terminal Server via VPN
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
Cannot log onto Terminal Server via VPN

 
Post new topic   Reply to topic    Windows Server Forum Index -> General Discussion
Author Message
Jeremy



Joined: 17 Jan 2006
Posts: 2

Posted: Tue Jan 17, 2006 2:53 pm    Post subject: Cannot log onto Terminal Server via VPN Reply with quote

Hi,
I have a client with 3 sites. Sites B & C are connected to site A via VPN with Dlink DI804HV VPN routers

Site A has SBS2003 and a Windows 2000 Server running Terminal Server in Application mode.

Sites B has 3 pcs connected to the network and login to the domain over the VPN.

1 PC is fine, but the other two are having problems. They cannot connect to the Terminal Server via the internal VPN. They can ping the SBS server and Terminal Server. They can also telnet to the terminal server port 3389

If I delete the MSLicensing under HKLM\software\microsoft they connect first time, but will not connect a 2nd time.

Terminal Server Licensing is installed on the SBS2003 server and is using "existing Windows 2000 Server - Terminal Services CAL Token (Per device) with unlimited licenses.

One thing to note is that if the 2 PCs with the problem connect over the internet (to site A's public IP address / I have port 3389 forwarded to the terminal server) then they connect fine. This is all ok, but I need them to be able to connect via the internal IP/VPN

Site A: 192.168.0.0 / 255.255.255.0
Site B: 192.168.2.0 / 255.255.255.0

All computers can connect to Exchange over the VPN, and browse shared folders.

Has anyone got any suggestions?

Cheers
Jeremy
Back to top
View user's profile Send private message
Jeremy



Joined: 17 Jan 2006
Posts: 2

Posted: Wed Jan 18, 2006 1:07 am    Post subject: Reply with quote

Problem resolved.

Ended up being a MTU problem.

I used ping -l <size of packet> targetIP

from the branch office site to the DC and vice versa in a trial and error method reducing the size of packet from 1500 down to whatever size it started working. And then subtract overheads from that and used this figure to set the MTU on the PCs

The 1 PC that was fine - someone had already set the MTU to a lower figure.
Back to top
View user's profile Send private message
 
Post new topic   Reply to topic    Windows Server Forum Index -> General Discussion All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB