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

Wrong IP when i Ping client name?

Hi, smart people!
I have a Win 2003 SBS, which is set up to run DHCP, WINS.
I am trying to roll out some Anti Virus on our clients from the server, but it already failed when trying to roll out on my test pc...
I believe that the problem maybe lies in the DNS, but I am not sure.
I have set up a VPN connection, where the router deals the IP [10.10.16.x]
But the server deals IP's from[10.10.10.x]
However, when I am not logged on through VPN, but at work, the VPN IP i registered to my netbios name.
I.e. I ping test computer via netbios name from the server:
It fails to ping as it pings the VPN IP.
When I ping the IP on the test computer, the ping is performed perfectly.
I believe this is why I cannot roll-out my Symantec Antivirus 10.0... ?
How do I get the netbios name to correspond with the correct IP?
HELP
br
Jessalster
0
jessalster
Asked:
jessalster
  • 5
  • 4
2 Solutions
 
dooleydogCommented:
somewhere, either in DNS or WINS, there is an incorrect mapping. Find it, and your problem is solved.

Usually you can sort by computer name and/or IP.

Good Luck,
0
 
jessalsterAuthor Commented:
How do I find that then?
I have looked in the registered IP's in wins, but the one that I get is not registered there. Help?
0
 
feptiasCommented:
A couple of suggestions:
1. Perhaps you've got dynamic DNS active on the VPN connection, but not on the NIC.
2. Perhaps the VPN address is being held in the DNS cache on the server. "ipconfig /flushdns" can fix that.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
feptiasCommented:
and another suggestion:
3. On the LAN connection you use when you are in the office, what IP is set for "Preferred DNS server"? It needs to be the local internal DNS server, probably on the main DC, not some external ISP's DNS server.
0
 
jessalsterAuthor Commented:
I found a Host (A) dokument under DNS/server name/ forward lookup zones/ server.local  where the wrong IP was saved. I changed the IP and now it works (pinging)
How do i avoid that this shit happends again, when I connect through VPN?
BR
Jess Alster
0
 
feptiasCommented:
Did you check my suggestions 1 and 3?
0
 
jessalsterAuthor Commented:
The server IP is static,
the flush dns didn't help,
dns points to server self.
But I fixed as stated previously :)
thx for your help guys
br
Jess
0
 
feptiasCommented:
I was talking about the settings on your test PC, not on the server.
0
 
feptiasCommented:
To clarify:
Forget about suggestion 2, it is clearly not the problem.
Suggestions 1 and 3 relate to the settings on the network interfaces on your test PC. There is probably one for the VPN and another for the cabled (or maybe you use wireless) connection that is used when the PC is in the office. If you have Dynamic DNS set onthe VPN interface, but don't have it set on the "in-office" connection then it would cause the problem you described. Suggestion 3 relates to which DNS server is set as preferred server. Even if dynamic DNS is set for the "in-office" interface, then having the wrong DNS server as your preferred would mean the registration would fail. The setting for Dynamic DNS registration option is in the Advanced options in the TCP/IP properties on the DNS tab. It is shown as a check box entitled "Register this connection's address in DNS".

You could also try unticking this option in the VPN interface to fix the problem.
0
 
jessalsterAuthor Commented:
Thanks for the clarification.
The DNS is set to be obtained automaticly, both at home, VPN, LAN and WLAN, however, I will check the tab for registering in DNS to see if it works.
Thank you very much :-D
BR
Jess
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!

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now