Vista Forums - View Single Post - Can't Ping vista machine after IP subnet change

richa1974 · 07-06-2009

Quote: Originally Posted by persiagulf4ever

hehe!

do you ping your destination computer by its FQDN?
FQDN = computer name + domain name + suffix
all Domain controller machines have two service runned :
1.DNS client
2.DNS server ( if DC is DNS server too)

if you ping from server, the machine ty to send ICMP echo request by the previous subnet mask...192.168.0.1....to resolving this problem...please clean your dns client cache and netbios cache...run=> cmd => ipconfig /flushdns and use nbtstat -R

use this command too on your others machines.

moreover dont forget that domain clients can logon without actually connecting to the dc...it has a cache...dont use this cache at all...this has a security reason.
fo doing this: config your domain group policy at DC.

MOREOVER DONT FORGET TO USING ROUTER WHEN YOU HAVE A MORE THAN ONE SUBNET.

If I ping by the FQDN or the machine name, it resolves to the correct IP. If I ping the correct IP directly, they still both come back as "Request Timed Out". If I ping the server from the affected machine it replies fine. The affected machine is working normally, other than being invisable to the other computers on the same network. I'm starting to think it's a Vista security issue.

07-06-2009	#3 (permalink)
richa1974 all flavors 2 posts	Re: Can't Ping vista machine after IP subnet change Quote: Originally Posted by persiagulf4ever hehe! do you ping your destination computer by its FQDN? FQDN = computer name + domain name + suffix all Domain controller machines have two service runned : 1.DNS client 2.DNS server ( if DC is DNS server too) if you ping from server, the machine ty to send ICMP echo request by the previous subnet mask...192.168.0.1....to resolving this problem...please clean your dns client cache and netbios cache...run=> cmd => ipconfig /flushdns and use nbtstat -R use this command too on your others machines. moreover dont forget that domain clients can logon without actually connecting to the dc...it has a cache...dont use this cache at all...this has a security reason. fo doing this: config your domain group policy at DC. MOREOVER DONT FORGET TO USING ROUTER WHEN YOU HAVE A MORE THAN ONE SUBNET. If I ping by the FQDN or the machine name, it resolves to the correct IP. If I ping the correct IP directly, they still both come back as "Request Timed Out". If I ping the server from the affected machine it replies fine. The affected machine is working normally, other than being invisable to the other computers on the same network. I'm starting to think it's a Vista security issue.
My System Specs