Having trouble with one computer on my network. I have 4 computers in the network, 2 desktops, and 2 laptops.
3 are running Win7 Home Premium, 1 is running XP sp3.
3 of the computers have no trouble accessing the other machines. (one of these is the XP machine).
But my desktop machine (Win7) is only able to see my laptop. The other 2 don't appear in the network map.
I can ping the absent computers.
I am not using HomeGroup.
Workstation running
DHCP Client running
DNS Client running
Server running
TCP/IP Netbios helper running
Computer Browser running
Network Discovery is ON
File and Printer sharing is ON
Windows Firewall OFF
All computers running BWMeter with firewall. (Turning BWMeter off...
Having trouble with one computer on my network. I have 4 computers in the network, 2 desktops, and 2 laptops.
3 are running Win7 Home Premium, 1 is running XP sp3.
3 of the computers have no trouble accessing the other machines. (one of these is the XP machine).
But my desktop machine (Win7) is only able to see my laptop. The other 2 don't appear in the network map.
I can ping the absent computers.
I am not using HomeGroup.
Workstation running
DHCP Client running
DNS Client running
Server running
TCP/IP Netbios helper running
Computer Browser running
Network Discovery is ON
File and Printer sharing is ON
Windows Firewall OFF
All computers running BWMeter with firewall. (Turning BWMeter off changes nothing)
I ran the Network Diagnostics tool, and after running for 1.5 hours, it was still "Waiting for results", so I canceled it.
Router is a Buffalo WRT-HP-54G with DD-WRT firmware.
I don't know what else to try. I can't understand why my desktop can detect one, but not the other two computers on the network.
Any help will be much appreciated.... I have very little hair left to pull out at this point.
Now when you attempt to access the absent machines can you use \\machinename\sharename or \\ipaddressOfMachine\sharename is either one successful?
Also trying using ping - a 192.168.nnn.nnn (the ip of the missing machine) from the machine that can't see it and see if the first line of the return results indicates the netbios name of the missing machine. If it does...is it accurate? if not try typing nbtstat -R to flush the netbios cache on the problem machine.
I should have said in the earlier post that you can examine the contents of the netbios cache by typing nbtstat -c at a command prompt.
Also reboot everything and bring the problem machine up last just to make sure all resources are available to it when it starts polling.