this may help. quoted from
http://www.ChicagoTech.net
Connection issues on DC, ISA, DNS and WINS server as VPN server
Symptom: You have a Windows 2000/2003 server is configured as VPN running
DNS, WINS, you may experience some connection issues. 1) the internal
computers can't ping the server by name; 2) if the server is a DC and Master
Browser, you may have a computer browsing issue; 3) you may receive Event
ID: 4319 - A duplicate name has been detected on the tcp network; 4) You may
receive error messages like "No Logon Servers Available to Service your
Logon Request" when you try to open file shares or map network drives to the
Routing and Remote Access server; 5) if the server is also a DC, you may not
be able to logon the domain; 6) if the server is also running ISA, you
cannot browse the Web from client computers on the local network, regardless
of whether the computers are configured to use Web Proxy or the Microsoft
Firewall Client. For example, "The page cannot be displayed" may appear in
the Web browser with a "cannot find server or DNS" error message.
Cause: When a VPN client connects to the VPN server, the server creates a
PPP adapter to communicate with the remote computer. The server may then
register the IP address of this PPP adapter in the DNS or the WINS database.
When the internal computers try to connect to the IP address of the PPP
adapter, them cannot reach the PPP adapter, then the connections fail.
--
For more and other information, go to
http://www.ChicagoTech.net
Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
Networking Solutions,
http://www.chicagotech.net/networksolutions.htm
VPN Solutions,
http://www.chicagotech.net/vpnsolutions.htm
VPN Process and Error Analysis,
http://www.chicagotech.net/VPN%20process.htm
VPN Troubleshooting,
http://www.chicagotech.net/vpn.htm
This posting is provided "AS IS" with no warranties.
"Mike Schumann" <mike-(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
>I have a Windows Server 2003 that is configured as a WINS Server. The IP
>address of the LAN interface on the server is 192.168.1.20. I have
>configured the TCP/IP protocol on this server to also use 192.168.1.20 as
>the WINS server so that the server has visibility of other computers
>located at remote subnets on my network.
>
> This same server is also configured to accept inbound dial-ups and vpn
> connections. I have configured the RAS service to use addresses from
> 192.168.1.200 to 192.168.1.220. This address range does not conflict with
> my DHCP server, which is running on a router on the network (the Windows
> Server is not configured with DHCP services).
>
> All of my computers in my network are configured to use this server
> (192.168.1.20) as the WINS server.
>
> Here's the problem: Periodically (about once a day), my computers at
> remote subnets start trying to use address 192.168.1.200 as the address
> for the server, instead of 192.168.1.20. It almost looks like WINS is
> handing out this address as the address of the server. If I do a ping
> from one of these remote computers, it starts pinging 192.168.1.200.
>
> I looked at the WINS server database on the server, and it shows the
> address of the server as 192.168.1.20.
>
> This all used to work great with the identical setup on Windows NT 4.0.
> Does anyone know what is going wrong, and how I can fix it?
>
> Thanks,
> --
> Mike Schumann
>
Similar Threads
Linear Mode
