• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 366
  • Last Modified:

NT4 Server , no VPN access from WKS

I have set up a NT4 Server SP6a, port 1723/47 opened on router, on a different broadband connection, I can setup VPN and connect using the domain name, so I assume the FQDN is working, with just TCP/IP enabled, the connection take around 5-10 seconds, but after its connected, I cant seem to access or even see any of the NT4 server resources, as if the server does not exist.

I tried to add NetBUEI, but this caused the connection to 'hang' for about a minute, then error 733, the NT4 Server is on a different ISP via router, and the Win2000WKS is on a separate ISP also by router connection.

Am I missing something on the setup ?

Many thanks
0
robertdims
Asked:
robertdims
  • 3
  • 2
  • 2
  • +1
3 Solutions
 
grbladesCommented:
Hi robertdims,
PPTP VPN requires UDP port 1723 and GRE (IP protocol 47). GRE is not a port and I suspect you have inadvertinly permitted tcp/udp port 47 instead.
0
 
robertdimsAuthor Commented:
Thanks for the reply, but I am told its TCP port 1723 and GRE47 (I assume this is the UDP port)
0
 
grbladesCommented:
Sorry it is TCP port 1723 not UDP.
GRE however is IP protocol 47 which is neither TCP or UDP.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
rindiCommented:
If VPN is on a different box, you shouldn't need to open any port (1723). Port 80 or 8080 (normal port used for webaccess) should be enough. If you are connected via VPN, can you ping your internal network?
0
 
robertdimsAuthor Commented:
Yes I can ping the server, but the strange thing is even though I have DHCP enabled on the server, the 2000WKS assigned an IP thats within the range specified by the server, but the Gateway is the same as the IP, and the subnet is strange.

Server IP  10.0.0.100
Subnet     255.0.0.0
Gateway   10.0.0.2

WKS assigned IP   10.0.0.110
Subnet                  255.255.255.255
Gateway               10.0.0.110

The connection seems to be painless, just no access to any resources as if the server does not exist.

Thanks
0
 
grbladesCommented:
The IP address and gateway etc... that you have been assigned is correct. Basically what is means is that to go anywhere the traffic should be sent to itself. The VPN software encrypts the data and sends it out of the network directly.

TCP/1723 is used for authentication.
GRE (47) is used for the encrypted traffic. Therefore if GRE is blocked you will be able to log in but not transfer any encrypted traffic.
0
 
vandCommented:
If GRE is blocked you will never be able to connect at all. GRE is necessary for the authentication, so if he is connecting, GRE is not the issue.

Can you connect to the server by UNC \\10.0.0.110?

Make sure all of your scope settings are configured on the NT Server as well. You can assign the default gateway from there. The Subnet should have been established when you created the scope for the remote connections. Also make sure that this is the only DHCP service on the network.
0
 
rindiCommented:
Is there a software Firewall installed on your Workstation? Are you trying to connect to a Domain Account on the server? To connect to your VPN, are you using a software on your win2k PC, or is this being done by a separate box?
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now