VPN Client Names Resolving to Old IP

  • Thread starter Thread starter Jeremy Chamilliard
  • Start date Start date
J

Jeremy Chamilliard

Good day,

Setup is 3 separate W2K servers: ISA/RAS, DNS, DHCP/WINS. RAS
configured with DHCP relay agent.

The problem is when my remote clients connect with VPN, their computer
names are not resolved correctly on my LAN XP workstation. I would
like for their names to be resolved correctly so I can use remote
assistance with them easily.

I have checked the WINS after a client connects, it updates properly.
The record in the forward lookup zone of DNS does not update however.

Any help is greatly appreciated.

Sincerely,

Jeremy Chamilliard
IT Analyst
Priority One Packaging Machinery
Waterloo ON CA
 
posting the result of vpn client ipconfig /all may help.

--
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 process.htm
VPN Troubleshooting, http://www.chicagotech.net/vpn.htm
This posting is provided "AS IS" with no warranties.
 
Have you set the remote clients to register their connection in DNS (in
the connection properties | TCP/IP)? If you have and it doesn't happen, you
will need to troubleshoot where it fails.

If the client registers in WINS, can't you see it by its Netbios name? Are
the remotes doing a domain login?
 
Here we go:

Windows IP Configuration

Host Name . . . . . . . . . . . . : sphinx
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : priorityone.ca

PPP adapter Priority One VPN:

Connection-specific DNS Suffix . : priorityone.ca
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 193.1.7.59
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 193.1.7.59
DNS Servers . . . . . . . . . . . : 193.1.7.1
193.1.7.1
Primary WINS Server . . . . . . . : 193.1.7.223

Thanks,

Jeremy
 
Yes, I have a test VPN client set to register the connection in DNS...I
can't figure out why it isn't. Also, you're right I can get the correct
ip address from mmc to WINS server, but not by pinging the name or
remote assisting the name. I was hoping to configure a slightly less
complicated solution for my guys to offer remote assistance to the VPN
clients (since the computer names are known) -- if it's not possible
then that's fine. And no, the remotes are not doing a domain login.
Thanks,

Jeremy
 
can you ping both dns ad wins?

--
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 process.htm
VPN Troubleshooting, http://www.chicagotech.net/vpn.htm
This posting is provided "AS IS" with no warranties.
 
From the test VPN Client:

C:\Documents and Settings\jchamilliard>ping polo

Reply from 193.1.7.1: bytes=32 time=221ms TTL=127

Ping statistics for 193.1.7.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 213ms, Maximum = 226ms, Average = 218ms
----------------------

C:\Documents and Settings\jchamilliard>ping upshot

Pinging upshot.priorityone.ca [193.1.7.223] with 32 bytes of data:

Reply from 193.1.7.223: bytes=32 time=236ms TTL=127
....

Ping statistics for 193.1.7.223:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 194ms, Maximum = 236ms, Average = 209ms

Also, a new development: I have found that sometimes the computer is
actually registered; however, disconnecting and reconnecting leads to
internal computers using the former address. Does this indicate some
type of timing or refresh interval issue?
 
Back
Top