marvin Posted March 1, 2010 Posted March 1, 2010 Hi guys Bit of a problem this morning... Came to install kaspersky on one of our admin machines which has vista business sp2 installed with all updates! The problem i am having is that i can't ping the machine from the server using its name but i can actually ping it using its ip address! Everytime i try to install the antivirus from the server, its failing and i can only put this down to the fact that there is a conflict between the server and the machine! Has anyone come accross this problem before? I have tried the ip/release and ip/renew but it keeps taking the old ip from dhcp again!
glennda Posted March 1, 2010 Posted March 1, 2010 sounds a bit like a DNS issue, if you can ping the ip, is the name resolving? most av stuff install by using the name rather then an ip
marvin Posted March 1, 2010 Author Posted March 1, 2010 Just also noticed that if i ping using the computer name, it returns this: pinging computer1.server.local [*.*.*.99] but when i do ipconfig on the local machine, its ip address is actually *.*.*.40
glennda Posted March 1, 2010 Posted March 1, 2010 Just also noticed that if i ping using the computer name, it returns this: pinging computer1.server.local [*.*.*.99] but when i do ipconfig on the local machine, its ip address is actually *.*.*.40 defo a DNS error, reload the DNS on the server
marvin Posted March 1, 2010 Author Posted March 1, 2010 Wouldn't that affect anything on the network? We have up to 200 machines on the network?
glennda Posted March 1, 2010 Posted March 1, 2010 it shouldn't do, most of your servers addresses are probly cached by them neway. have u got 2 dns servers? as while one is reloading the other should be okay to carry on working for few mins while the first one reloads.
marvin Posted March 1, 2010 Author Posted March 1, 2010 I have just looked at the DNS, found the pc name and double clicked on it and found that the ip address is *.*.*.99 which is not the one on the local pc!
glennda Posted March 1, 2010 Posted March 1, 2010 double check in the DNS to check it is actually wrong, it could just be the server has a cached address for that pc, if so just do ipconfig/flushdns and it will clear the local cache and then look against your server. EDIT: its not this!!!
marvin Posted March 1, 2010 Author Posted March 1, 2010 only have one server! The ip address on the server is definately wrong! Do i run the flushdns command on the local machine or server?
glennda Posted March 1, 2010 Posted March 1, 2010 only have one server! The ip address on the server is definately wrong! Do i run the flushdns command on the local machine or server? ignore that comment, i don't think it applies, you should be able to get away with reloading dns, if you want further help troubleshooting the dns look here Troubleshooting DNS servers: Domain Name System(DNS)
Dos_Box Posted March 1, 2010 Posted March 1, 2010 Local machine. Also check to see if DHCP has not issued 2 addresses for it, or had a bad one listed as the one you actually want.
marvin Posted March 1, 2010 Author Posted March 1, 2010 Under DHCP, the IP address for that particular machine is *.*.*.40 where is on the DNS it is down as *.*.*.99! Do you still think i should reload DNS? If so how do i achieve that with only one server on the network!
PeterG Posted March 1, 2010 Posted March 1, 2010 I wouldnt reload DNS just yet as it will lead to all sorts of related issues if you are using exchange and AD, in DNS there is an option to scavange old and stage DNS Records. Start immediate scavenging of stale resource records: Domain Name System(DNS) Theres the microsoft Article obviously do this at your own risk etc . Regards Peter
marvin Posted March 1, 2010 Author Posted March 1, 2010 Yeah, we have exchange on the server and i am a bit wary that it will affect things on the network!
PeterG Posted March 1, 2010 Posted March 1, 2010 I would personally remove stale records .......Is it only one machine that you currently have this issue with ? .....
marvin Posted March 1, 2010 Author Posted March 1, 2010 So far only 3 machines, in the admin office! 1 is on vista and the other 2 are running xp!
PeterG Posted March 1, 2010 Posted March 1, 2010 Deffo a DNS Issue, i would recove the stale records and go from there ....... reloading DNS would be a last resort and could cause major issues with Exchange and AD.
glennda Posted March 1, 2010 Posted March 1, 2010 yeah i wouldnt do it on an exchange box! scavaging the records is probly a good start - i just didnt think of that! have you checked to see if there are an other errors with machines not pointing to the right place? also you may want to check that DHCP is set up to update the DNS, theres a guide here Using DNS servers with DHCP: Dynamic Host Configuration Protocol (DHCP)
PeterG Posted March 1, 2010 Posted March 1, 2010 If i was you do that scavange the records now and then do a DNS Flush on your local machine (ipconfig /flushdns). Then type nslookup (Machine Name) this will return to you the IP address that is associated with that computer name in DNS. Let us know Pete :-)
marvin Posted March 2, 2010 Author Posted March 2, 2010 Did scavenge the records and nslookup shows the ip address which is on DNS but then checked the ipconfig of the machine and it is the one listed on DHCP! Now what would happen if i deleted the IP address on DHCP and rebooted the machine? Would that renew the ip address of that machine to the one on DNS?
glennda Posted March 2, 2010 Posted March 2, 2010 Did scavenge the records and nslookup shows the ip address which is on DNS but then checked the ipconfig of the machine and it is the one listed on DHCP! Now what would happen if i deleted the IP address on DHCP and rebooted the machine? Would that renew the ip address of that machine to the one on DNS? you may find that it still gets the same lease, try just deleting the DNS record for the PC then do ipconfig/renew, should then register itself with the DNS servers again. what are you DHCP lease times? also is DHCP set to update DNS? Toby
marvin Posted March 2, 2010 Author Posted March 2, 2010 DHCP lease time is set to 8 days and DNS is set to update as well! I reckon there is a conflict somewhere between the 2003 server R2 and this vista machine! So do you think i should delete the DNS entry and reboot the machine?
glennda Posted March 2, 2010 Posted March 2, 2010 DHCP lease time is set to 8 days and DNS is set to update as well! I reckon there is a conflict somewhere between the 2003 server R2 and this vista machine! So do you think i should delete the DNS entry and reboot the machine? delete the address, i wouldnt say its a conflict between the machine, but personally i wouldn't have the DHCP set to that length of time, ours is set for 12 hours, as we shut down all machines at night they then get a new address in the morning plus the DNS gets updated with a new lease time, is there any DNS errors in event viewer, or any thing related in the clients? Toby
marvin Posted March 2, 2010 Author Posted March 2, 2010 no errors in event viewer for DNS! When you say delete the address, do you mean delete the machine name under DNS?
glennda Posted March 2, 2010 Posted March 2, 2010 no errors in event viewer for DNS! When you say delete the address, do you mean delete the machine name under DNS? yep, just find the record thats wrong and delete it, but i would consider reducing the time for the DHCP lease, just my personal view but think it could save problems in the long run. Toby
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now