• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Network Neighborhood

L

LuDaCriS66

Platinum Member
I have a Linksys BEFSR41 4-port router. I've got it setup with 2 computers and an aDSL connection. I've also got ZoneAlarm (free version) on both computers. On one of the computers, opening up Network Neighbourhood always displays the computers in the LAN. The other computer is a different story. It only shows all the computers occasionally. Usually, nothing will show up if I open up Network Neighborhood.. but sometimes they show up. Which is weird. This isn't a huge problem but it is annoying when I need to access the other computer but i can't. Any ideas?
Could it be the generic NIC? In the other computer, I'm using a D-Link ethernet card that was provided by my DSL ISP.

Thanks

 
what protocols do you have installed? file and printer sharing? client for microsoft networks?

as a work-around, you could always just map the shared drives then you wouldn't need network neighborhood anymore...
 
Sohcrates, are you saying that if I map the shared drives on both machines, I don't need NN? Howdo I map a drive? Thanks.. (Be patient, I learn fast.)
 
Im having the same problem Ludacris66. I have two computers networked together on the same router, both running Win2k (one has Tiny Personal Firewall, the other has ZoneAlarm) and the one with ZoneAlarm can see my computer (and itself) the majority of the time and access my computer (transfer fiels from) when I turn off Tiny but my computer cant see (or even get into Network Neigbhorhood) no matter what. I hate this problem
 


<< Sohcrates, are you saying that if I map the shared drives on both machines, I don't need NN? Howdo I map a drive? Thanks.. (Be patient, I learn fast.) >>



what OS are you using?

NN will still be there and all, but if computers only show up sometimes, you might be able to get away with networking the drives, and that way you don't have to go into NN everytime...you need all the same protocols installed (file and printer sharing, client for ms networks, and tcp/ip of course)

in win2k, you would right click any shared folder in network neighborhood and choose "map network drive" then assign it a drive letter and you're off!
 
are you guys using WinMe? if you are, then it is a known issue. too lazy to go find the kb artice #. but there is a fix available. MS says you have to call them for it and don't provide a link to d/l it from.
i triede to call them to get it but I am using an Oem version and according to MS, that is not supported by them.
 
First off, get rid of the firewall software. After that we'll talk.

Try searching for a computer name in, well, the seach section of your start menu. Sometimes the computer will show up with a search, even when its not in Network Neighborhood.

Also, there is a function of the OS called BrowseMaster. Its a kind of self hosting WINS, it keeps a list of computers on the network so that it doesn't take forever when each computer wants to find out what is out there. You need to make sure that you start one computer at least half an hour before the other so that you don't get conflicts about which computer is the Master. When the computer starts up it searches the network for an existing master. That 30 minutes will help make sure that one computer has time to search the network and find that there are no other masters.
 
If you know the network name of the computer you want to access,t then simply type \\NETWORK_NAME in IE. (substitute NETWORK_NAME with computer name). There is no need to go to NN
 
Network neighborhood is bunk. Dont depend on it for connectivity tests. Usind the UNC like marat suggested, or searching like igiveup suggested (Searching for NetBIOS name of the remote PC's), though it always works, not sometimes. However NN is a nice quick access way as well, and this problem is almost always caused by browsemaster issues, though the software firewalls could certainly come into play. My question is why you have a firewall installed on machines behind a router? No point really. A simple hosts file will also clear up this dilemma and is easy to create and maintain on small LAN's.
 
Here is another one I just picked up on....

Open a command prompt and type: \\192.168.1.3 (substitute IP addy of other computer)

It should connect just fine. Never knew this would work, but I found it in a MS Knowledgebase article when I was troubleshooting a XP Pro and TCP/IP connection problem.
 
Same thing Marat suggested yesterday just with IP instead of NetBIOS name (computer name) and I restated with the technical term for it UNC (Universal Naming Convention) You can do this from a command prompt or straight from the run command.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top