ok, i have a windows server 2003 domain with a few Vista clients. i recently changed the local subnet from 192.168.1.0/24 to 192.168.25.0/24. one of my vista clients can no longer be pinged or have any of it's resources viewed. it's a Vista x32 Ultimate PC running SP2. it's also a member of the domain. it works fine...it can ping other machines, it can go on the internet, and it appears to be working fine. but from any other machine it cannot be pinged. if you open Network on another computer, it appears in the list. but when you double-click on it it hangs for about a minute and says the machine cannot be found. i have tried removing it from the domain, running "Set Network Location", picking private, and adding back to the domain. no luck. it's getting a dhcp address from the windows server. it logs in with a roaming profile with no errors. if it helps, the way i made the machine in question get the new ip address was disabling the nic, and then re-enabling it. it seemed to work fine as it got the new ip from the dhcp server. the reason for the need to fix this issue is it is sharing it's locally installed printer and no one can print to it. Network Discovery, File Sharing, Public Folder Sharing, and Printer Sharing are all set to ON. any thoughts???
Can't Ping vista machine after IP subnet change
- Thread starter richa1974
- Start date
persiagulf4ever
New Member
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.
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.
My Computer
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.