Search results for query: *

OK, here is one more thing you need to check out. Go to the TCP/IP properties of your server's lan connection. Set the primary DNS and secondary DNS server IP address to be the IP address of your server. Next, start the DNS manager. Right-click on your server and go to the forwarders tab...

I have had a similar problem as well. I have a Windows 2000 Server that is the primary domain controller (internal name is newserver). I have another Windows 2000 Server that is simply a member server without Active Directory installed. The website is hosted on the member server. The...

First, make sure routing and remote access is running on the server. Next, check your firewall or router and make sure you have TCP Port 1723 and TCP Port 47 open and forwarded to your server. Also, enable protocol 47 and forward that to your server as well. If you can VPN inside the network...

Are you using NAT at both offices? If so, the private addresses have to be on different networks. For example, if office A is using 192.168.1.0, then office B will need to use 192.168.2.0 (or something like that). I had this same problem...a Windows XP Home machine would work, but A Windows...

Ken, Thanks for replying...I have since solved this problem. I was accessing the office network from my home network. Both networks use NAT in the 192.168.1.0 network (that was the problem). I changed my home network to 192.168.100.0 and everyhting works great now.

Windows XP Home edition can access shares/resources when connected to W2K Server VPN, but W2K Pro cannot access shares/resources. Both machines successfully connect to the VPN, but the W2K Pro machine access any of the shares/resources, etc. Any ideas?

Be sure that you have port 1723, port 47 and protocol 47 open and enabled. Also, try rebooting the server. I had a similar problem when I only had port 1723 and protocol 47 forwarded. When I opened port 47, it started working