Discussion Locked

Network Neigborhood

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am running a Win NT 4.0 server with 3 workstations. I frequently run an internet sharing program for the workstations. The internet sharing is still fast but the icons in Network Neighborhood take forever to show up and once they do it takes as long to bring up the drive on the workstation. My NIC cards are Netgear FA310TX 10/100 with an Intel 8 Port 10/100 Auto sensing port hub. I have setup the network so many times due to issues when clicking on a workstation in network neighborhood myhair is turning green. After the original setup which includes a format and complete reinstalation of all operating systems and nic cards with all the latest drivers the network works fine. Very fast access speeds and fast file transfers and also fast internet sharing. Eventually when I click on a workstation in Network neighborhood it just sits there trying to find the workstation. It does finally find the workstation but it is very slow. What gives. Why does it work initially and then slow to a crawl. I have pinged the workstations and this is the result. (1) Workstation = Ping Statistics for 192.168.0.3. Round trip times in milli-seconds: Minimum=oms, Maximum = 1ms, Average = oms. (2) Workstation = Ping Statistics for 192.168.0.2 Round trip times in milli-seconds: Minimum=1ms, Maximum=1ms, Average=1ms. I would certainly appreciate any help in stabilyzing my system so that I may use my network as it is suppose to work. I try rebooting the server and workstations but to no avail. Still very slow. I have run virus programs including F-Prot and Mcafee and their are no viruses. Again this rebuild is only a few days old.

Please help.

Thanks

Mike R. Davis

4 replies

by gandalfen

If you haven't already, my best bid is to run a WINS server on the NT4 server. My guess is that this at least solves you problem with the Network Neighborhood being slow list.
If you use DHCP on the server, this is easy to implement. Also, using the NT4 server as a domain controller, and letting the clients log on to this domain, makes the network browsing a lot faster.

by watskyd

With only a handful of computers on the network, a quick solution may be to make an LMHOSTS file with the #PRE extension for each of the machines on the network. The sample file that is on each computer can be opened with Notepad, and it will give an overview of how to write the file for your network. If more computers are planned in the future, WINS would be the way to go.

by m-burt

We recently upgraded out primary domain controller to Win2k Server edition, but recently we have been experiencing some problem on out network....the main problem is that we can not always see all of the machines on the network some show up and others don't. The only thing that we have seen is that when we add the NetBeui protocol to certain clients they can see more machines but not always all....but with just the TCP/IP protocol we can't see those machines...any insight would be appreciated.
Mario

by ig-88

Hi Mike,

I had (have) a similar problem but on a peer to peer network running Win98se. The Workstation that is acting as the "Server" is setup with DSL, I have Sygate 4.0 running to share the net access to the other peer workstations. It worksgreat but the Win98 "Server" is slow as a snail in heat, I get the same problem you mentioned in network neighbourhood, when trying to access the other workstations! Its very weird, I can access the "Server" in the NetHood from all the other Workstations but when trying from the "Server" its soooooo sloooow! I ended up using the "net share" command from dos to map drives.

I'm sorry that I can not answer your question. But at least you know its not just YOU! =)

Cheers!

Robert

This discussion is closed to new replies.