Computer runs slow once connected to a network

[tkistre]

I just built 2 identical computers for a friend to put in a office setting. They already had what I'll call the server (running WinXP PRO) on the network, though this IS a pier to pier network, NOT Server/Client. The 2 pc's I built also have WinXP Pro. I wasn't there, but when he connected the 2 computers to the network, they both ran very slow. Sometimes it took up to 2 minutes just to open "My Computer," plus they will not see the server computer. The server computer sees them, but he didn't try to access them since he didn't set up sharing yet. I only know they are using TCP/IP, same workgroup, all wiring is good, etc... My friend is network knowledgable, more than me, and has tested the basics, such as cables good, connected, etc... I'm going there with him in the morning to see if we can determine what's going on.


The 2 PC's I built have 256mb Micron memory, Gigabyte GA-7VKML Integrated V/S/L (REaltek LAN), AthlonXP 1800+, 40gig Maxtor HD, Floppy & MSI 52x CDRom, that's it. I have built about 25-30 systems for workstations using these parts and never had any problems like this before in network conditions.

I plan on disconnecting the 2 PC's I built to see if they still run slow, because the ran fine at my home & passed 24hr. burn in. I had them connected to my local network to update windows and they had no problems. Off hand, is there anything anyone can suggest to make sure I check for, that could be making these PC's run so slow on the network? (Assuming they run fine not on the network.) Also, anything to make sure I check for so the computers will see each other?

Any help greatly appreciated!

 

[spidey07]

<rant on>

That's xp for ya...

First please post an "ipconfig/all" from every single workstation on the network.
Then post what protocols are loaded on the machine
Then post what the workgroup and DNS settings on each machine.

My first guess is you have a name resolution/DNS/wins problem. the "ipconfig/all" from every station will help us diagnose alot..

 

[tkistre]

If we can not get them working correctly, I'll try and post the configurations tomorrow. I don't have access to them right now.

I could understand this causing them to have problems network wise, but would that have anything to do with them operating so slowly? Although I know WinXP is not flawless, I have to admit that I have had tremendous luck with it.

 

[ScottMac]

Maybe XP isn't spec'd for a maritime environment?

The network can be slowing them down if there are lots of broadcasts. The network can be slowing them down because the machines are busy trying / waiting on or for network communications.

Maybe the network is slowing them down because they are busy defending their turf from one another ("It's mine!!"..".NO!! It's MINE!! ...).

XP, even the Pro version, is NOT meant to be any kind of server, and certainly not in a commercial environment.

You've chosen poorly. I hope you aren't charging for this.

Sorry to be harsh but your network, as presented, is suboptimal (especially if this is for commercial use).

(Tell us about the cabling too....homemade? Store-bought? ...Hub? Switch?)

Good Luck

Scott

 

[spidey07]

I've seen XP completely slow to a crawl if not configured properly from a client and server side.

XP will spend a few minutes searching for drives, netbios names and domain. Especially when opening explorer or using MS office and the file open dialog box.

Sorry to rant but I've been on many conference calls with the XP "network engineers". They are complete idiots and have no idea how a network actually functions. I've sent them traces of their fvcked up code and they still don't believe it.

MS - "but XP doesn't rely on netbios for locating resources"
spidey - "then why the hell are you broadcasting, even though you have wins servers, dns servers, search domains configured, active directory working perfectly, dynamic DNS is flawless, why the fvuck are you waiting 30 seconds for a reply to your broadcast that isn't going to reach you and you shouldn't be broadcasting anyway?"
spidey - "stupid fvcks"

Sorry, I've spent about 140 man hours on this problem and I'm sick of XP networking.

 

[tkistre]

Well, I fixed the problem after looking at the computer for about 2 minutes. I forgot I had installed a firewall on both computers until I was sitting in front of them. I had built these more than 2 weeks ago and have built about 7-8 since. I thought these computers had Broadband Internet access so I installed Norton's Internet Security that came with the motherboards on them. The friend I built them for had never seen Norton's Internet Security so he didn't realize what the icon was in the System Tray. Once we uninstalled it, since we didn't need it, everything was the way it should be. Both computers ran quick and saw each other on the network as they should.

Thanks for the input guys! I'm happy it was a easy and quick fix.