Discussion Locked

Continuing NT 4.0 Problem

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I previously posted a question about the server service on my NT Workstation not working. I got an answer for that one. The one that I currently have is as follows: When I select Network Neighborhood and double click on a workstation's icon, the resources that are shared on the drives don't show up for quite a while. The pointer arrow turns into a hourglass and sits there for a long time. Eventually the resources show up but it is taking an inordinately long time. I suspect a problem with the NIC card even though I have changed the card and the interrupt. Any one have a good idea what it is and what to try?

9 replies

by allan

I've seen this problem when using more than one protocol.
If you can, eliminate what you don't need.
IPX/SPX can cause this if your also running TCP/IP
If you need all the protocols, setup the binding order so tcp/ip is first.
If you need more info let me know.

by mikel~t

I concur with Answer #1. I ran into the same problem you described, and once IPX was removed, the time frame was greatly reduced for the shares to show up.

Mike

by shardy

A key thing to know to proceed in problem definition is what are you using for name resolution? wins,dns,or just default browser
functions within a peer to peer network.If
using wins with tcp/ip,check the wins server and hope and pray that someone did not include the netbios protocol on the network.(wins uses netbios over tcp)If you are using
simple browser functions,check for browser wars going by looking thru event logs . I have actually seen situations where a win 3.1
pc has become a browser master in what it thought was a little peer to peer network.Trouble is when the machine was shut down ,a browser election occured and wreaked havoc on the domain with wins serving as the master browser.Remove all unnecessary protocols on all machines!!!! Also , if you are not using wins you could be having broadcast storms.

This discussion is closed to new replies.