Printable View
I have a peer to peer network setup between my laptop and my desktop. I recently changed my motherboard on my desktop unit. After reinstalling the network drivers, windows has almost a 5 min delay during bootup. I know that its trying to logon to the network, but because its peer to peer It never finds the network. I've tried using the quick logon option, but it doesn't help.Using either logon option produces the same result. Any Idea's?
Certain ISA Network cards with NE2000 drivers will slow the system boot speed down considerably (also the shutdown time). There is very little you can do about this!
------------------
<_-ShaGGy-_>
What protocols are you running with this network ?
A lot of times the 5 minute delay is caused by the fact that it is checking each protocol for a network connection. If you run strictly TCP/IP (No NetBEUI, No IPX) you will get the best performance out of a microsoft Peer-to-Peer, but TCP/IP is harder to troubleshoot than an IPX one. Try using one protocol, whatever it may be. Also, if you have anything installed referring to a netware network, remove it. You may also want to set one machine as the Browsemaster and the other to NEVER be Browsemaster. You can do this by going to Network Properties, then to the properties of "Client for Microsoft Networks," then in the "Advanced" tab select "Master." Change it from Auto to Yes or No. Yes will make that machine browsemaster, no will make it never browsemaster.
Definition of Browsemaster:
In a Microsoft Peer-to-peer network, one machine holds all of the info on what machines are connected to the netwrok at any given time. Any time a machine opens Network Neighborhood, it makes a call on the network for the browsemaster to respond with a current list of machines. Any time a machine is added to the network, it tells the browsemaster it is now on. If you do not manually set the browsemaster then every time a new machine is added to the network it will start an "election." It will wait for a reply from an existing browsemaster. If it receivs a reply it will not become master and will tell the master it is now on the network. If it receivs no reply it will become the master itself. The elections take bandwidth, add traffic to the network, and will cause machines to take longer to boot while they negotiate a master. When shutting down a machine will also take a long time because it has to release it's master status and start another election if it was master, or if it was not, it has to notify the master that it is no longer on the network.
Sorry for being so long-winded, but I like to tell people the why behind what I tell them to do so they can make more educated guesses as to what else may be wrong https://forums.windrivers.com/images.../2000/09/1.gif
-Steve Zap