W7 computers cannot see domain resources

I have a mixed domain XP, W7, server 03 and 08. My W7 desktops have stopped being able to see other computers in "network" and in a net view from cmd line. XP boxes have no issues. I have IPv6 disabled but do have netbios over tcpip enabled from the DHCP server. I have a WINNS server as well. Users can access resources via URL from shortcuts or run line, can ping, FW disabled network discovery and IO mapper are enabled.  
LVL 1
jiggyflyAsked:
Who is Participating?
 
jiggyflyConnect With a Mentor Author Commented:
I solved this by stopping the computer browser service on the master browser. I remotely ran nbtstat -RR using psexec on affected systems then started the computer browser service on the DC.
0
 
theruckCommented:
what do you get as an output of the net view command?
0
 
speak2abCommented:
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
Tony GiangrecoCommented:
Check the nics on the Win 7 boxes. They shiould all be obtaining an IP and dns.

On the Win7 os'd, open a command box and type in
ipconfig /flushdns
ipconfig /register
ping yahoo.com      See if you get four replies
ping (your domain Controller IP) see if you get four replies

If you still have the problem, see if all your Win 7 boxes are on the same network switch. If so, swap it out to see if that's the problem.
0
 
jiggyflyAuthor Commented:
to answer the Qs posed:

A net view on the affected computers produces 3 servers,
\\BANSHEE  HyperV, 2008R2
\\FILE-SVR-03          Server Room, file server 2003
\\SQLSVR               SQL 2005, VQ 6.5.2
The command completed successfully.

There is no crrelation with the servers, different OS, HW and switch.

I have flushed DNS and ran nbtstat -RR to release netbios cache and register in winns
PINGs all work fine it is not a connectivity or TCP/IP  problem per se.
*new development XP boxes are now becoming affected. This means it is not related to IPv6 or the new network discovery methodology in W7.
0
 
jiggyflyAuthor Commented:
fixed.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.