Printable View
Guys and gals,
I've got a p2 333 64 megs ram win98 ie5.5 that acts as a file server on a peer-to-peer 10base2 network. Everytime the system boots, it sits for like a minute when the desktop appears (before it makes it's network connections or runs any startup programs). It has a Realtek RTL8029 nic.
Any ideas what makes this thing sit like it does during startup?
Thanks.
OK
Here's what I did. Let me know if this there is a problem with this. I changed my primary network logon from Client for MS Networks to Windows Logon. I saw a program (mrpexe) that was hanging on startup. It was described as: WIN32 Network Interface Service Process. I figured this was connected to the Client for MS Networks being the primary net logon, so I changed the primary logon.
Everything seems to work ok, but I'm wondering if this messed something up that I can't see right now.
Thanks.
How many protocols do you have loaded in the Network Properties. Having a number of different protocols load can slow the boot time.
Due to the nature of networking, the PC may be looking for a server and other clients on the network, which can also take a while, especially when they don't exist.
There is your problem. You need 10baseT (twisted pair). Is 10base2 something I should know about...(just kidding, couldn't resist.)Quote:
Originally posted by klintman:
<STRONG>Guys and gals,
peer-to-peer 10base2 network.
Thanks.</STRONG>
Play nice now. I still have a number of clients using 10base2 (RG58 Thin COAX).....Quote:
Originally posted by Ya_know:
<STRONG>
There is your problem. You need 10baseT (twisted pair). Is 10base2 something I should know about...(just kidding, couldn't resist.)</STRONG>
This is probably because your network card is looking for a DHCP server. To fix this problem:
In the Windows Control Panel, select Network (Start > Settings > Control Panel > Network)
Select the entry for TCP/IP -> Ethernet card (NIC)
Click the Properties button and select the IP Address tab.
Enter a "non-routable" IP Address* (e.g.: 192.168.0.100) and Subnet Mask (255.255.255.0).
Click "OK" several times to close the control panel. (You may be prompted for the Windows install disc.)
Re-boot your machine to implement the changes.
This happens on my home DSL service, maybe this applies here as well.
OK,
Changing the Primary Logon didn't solve my problem.
We use TCP/IP. There are no other protocols. We use Wingate 3.x (it's installed on another machine on the network). That may be the problem. I don't think I can configure TCP/IP like MacGyver suggested without messing up the Wingate Client configuration.
I'll give it a try next week.
Thanks.
P.S. I don't think I can talk my boss into upgrading to a server-client network, upgrading all of the NICs, re-wiring the office, and buying a hub.
I have limited experience with this topology--only seen it on networks with no more than three nodes. Termination was something of a trouble spot more often than you would expect, and correction can cure unexplained problems.
How long is the bus, and where is this PC in relation to the terminated ends? For giggles, replace the terminators, and the T-connectors on the Ends, and perhaps the T on the PC in trouble. Resistance on the terminator must be constant...I believe it's 50 ohm's, (help me out Sowulo). If the resistance isn't just right, the network may suffer with difficult to diagnose issues. It's less than $10.00 in parts. There is a minimum distance between nodes, 3 feet of cable, or something of that nature. Go over your topology and ensure every inch is within spec. to Thinnet limitations. I can't think of anything else except what you may have already tried...updated NIC drivers, new NIC, scandisk, defrag'matize (got that from an old timer, he hates PC's)...I wish you luck!
You did fine. One more thing...with 10base2 if one system is flaking out it affects the entire network. Try pulling the T-connector off of one workstation at a time (leave the cables connected though) and see if your system reboots any quicker. One of the workstations could have a failing NIC.Quote:
Originally posted by Ya_know:
<STRONG>I have limited experience with this topology--only seen it on networks with no more than three nodes. Termination was something of a trouble spot more often than you would expect, and correction can cure unexplained problems.
How long is the bus, and where is this PC in relation to the terminated ends? For giggles, replace the terminators, and the T-connectors on the Ends, and perhaps the T on the PC in trouble. Resistance on the terminator must be constant...I believe it's 50 ohm's, (help me out Sowulo). If the resistance isn't just right, the network may suffer with difficult to diagnose issues. It's less than $10.00 in parts. There is a minimum distance between nodes, 3 feet of cable, or something of that nature. Go over your topology and ensure every inch is within spec. to Thinnet limitations. I can't think of anything else except what you may have already tried...updated NIC drivers, new NIC, scandisk, defrag'matize (got that from an old timer, he hates PC's)...I wish you luck!</STRONG>
Sometimes it is better to check resistance at the tees with both terminators on. The reistance should be aprox. 25 ohms +- 2 ohms. Much more deviation from that and you will have problems. Also I have seen this problem with the Realtek cards on 10base100 and have been able to correct it by using updated drivers. Good Luck.
Oh forgot to explain. The terminators are 50 ohms but when both are in place (ie. both connected to the cable) you get 25 ohms.