Discussion Locked

URGENT - Need suggestions - Slow LAN

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

Hi,

I've just started a new job...3 days! and their network is MEGA-Slow. Server = W2000, about 7 workstations = W98 & 1=XP. This is my 1st experience with a HUB.

I havent collected all the info yet on the setup of the LAN (inc hardware) but if possible i need some suggestions on where to check, what to look for in setup etc. of the lan. I dont have the tools to check cabling faults, so if i can't find anything will have to call on some techs to check that.

it's really slow. to the point where work is weeks behind. I've had faster performance on slower machines over greater distance.

Any suggestion on what to look for will be greatly appreciated.

Thankyou
Gernot.

24 replies

by bklein

I don't know what your budget will allow but...

1) Replace the hub with a switch.

2) Check the protocols on all machines. You should be able to strip all machines down to TCP/IP. If you come across any machines running NetBIOS/NetBEUI, this would probably be the problem.

by gernotlg

i found one WS with NetBIOS/NetBEUI so i removed it & re-booted.

would that mean the server has to be reset?

by bklein

Stripping a protocol on a WS should have no impact on the server as long as both have TCP/IP enabled.

Please keep us posted, I would like to know if your one WS with NetBEUI was screwing the whole network, since this is such a common situation.

by carsten.holfelder

What type of hub is it and what speed is it as this could make a difference. A 10/100Mb Switch is a better option.

Your cable can also be a problem. Are you using stranded between the hub and the network point where the conputers are plugged into. It should be a solid core cable.

What distance are the computers from the hub they should be less than 100 meters.

What protocols are your computers using IPX/SPX and netbuie are mainly broadcast protocols. If you can change to TCP/IP.

by gernotlg

it's not a solid core cable (like at my old job, they had COAX)

this is the blue cable with the phone-type plugs. thats twisted pair isnt it?

I'll have to check on the speed of the hub.

also, the server is upstairs with an 8 port hub, downstairs is a smaller hub/switch connecting the downstairs workstations.

i'll have to check on cable length, i doubt that its too long.

thanx

by joemcse2001

You have server upstairs on a hub and workstations downstairs on another hub. This means all network traffic between workstations and server travel on a single line (presumably 10Mbps)uplinking the downstairs hub to the upstairs one. Upgrading to 100Mbps switches will improve bandwith.
BTW - twisted pair can be solic core or stranded wire - twisted pair is 8 wires in 4 pairs twisted together

by djent

Check your NIC configs for 10mbps cards or locked speed, get a switch. watch collision lights on each port, could indicate dirty connectors or bad cable.

by gernotlg

ok, 4th day on the job.

removing the NetBEUI didnt seem to make a diff.

All WS's are now on TCP/IP only.

Oh, btw , thanx all for ya responses.

anyway, i managed to get in contact with the previous person who was in charge of the system,and he advised me that he has often suggested that they upgrade to a 16 port switch and upgrade the server and install Terminal Services.

I also got into contact with the provider/supporter of the main DB application that is being used and i was told they also recommend using TS.

The server is W2000server. so, as i've found out, it will do it. Having read some of the discussions on TS, it seems like the way to go.

i s'pose. (i'm just a programmer !!!! damit!)

by techmule

If you have a LAN with 1 server and 8 - 10 clients, and it's running slow, I don't thin Terminal Services is going to do much for you. In the long run, it may be a good solution, but if there's a network issue, it won't go away until you fix it.The key here is, are all PCs slow? Only one or two? Is it the server that's slow (CPU maxing out, memory issues)? If you can narrow down/isolate the problem you're miles ahead.

A couple of "gotcha's" that you might want to check....cabling can be a culprit....one or more bad/flaky cables. You're using CAT 5, but if one of the cables has been crushed or damaged it can be an issue(usually only affecting the computer using that cable). Also, you could try turning PCs off one at a time....I've seen a flaky network adapter bring down a LAN.

The switch idea is a good one as it can isolate a problem to a single port, which helps in ultimately solvong the problem.

Anyway, just my 2 cents...hope it's helpful.

Good luck

by tbragsda

I?m sure it?s slow, but we don?t even know what part of this setup is slow. From a workstation, ping the server, and another workstation. Should be ~1MS on something like this.

You brought up a DB. What?s the backend for this, SQL? On what sort of hardware? Could just be the DB that?s slow, and everyone says ?Network?. Are you making lots of query requests to the DB, or more data entry?

When everyones off (at night) try stoping whatever service is running for the DB on the server. Move some files back and forth to the server. Whats the speed like now? Bring the service back up repeate. Run some of the processes that the users preform, while completing the same file copy.

by gernotlg

apparently its written in visual foxpro. i havent had a chance yet to have the network to myself.

I will try those file copy suggestions of yours, thanx.

by tbragsda

Look through everyone?s posts, and start making some tests. You need to isolate this a little. It could be related to the 10mbps hubs discussion that is going on, or could be server related, as in the extra services running, errors etc. It could also be the app its self.

Many of the suggestions given so far will help break down the problem. Keep all the tests isolated at first. By that I mean, don?t replace the hub and change where the app runs, and turn off DNS. This will lead to too many options. One at a time. Once you see some improvement, then you can start looking at fixing ALL your problems.

by madmark

"Tbragsda" has it right. Don't go off half-cocked or you will be chasing ghosts through the LAN. Calm down and take a look at what EXACTLY you are having issues with. "The Network" means different things to users than to IT staff.

What is being seen as slow? Moving files? Copying data? DB access? Login? What happens when people are gone? Does it happen only at a certain time? Have you tried turning ALL systems off, and bringing them up one at a time? Have you put a sniffer on the wire to examine packets? If you are unaware of how to troubleshoot the LAN, call in someone that can, and insist on "knowledge transfer". We all started from the same place. Zero knowledge.

I inherited a network a few years back that had an issue every morning and every afternoon. The network would slow to a crawl. Less than 2Mbs throughput, lost packets, all manner of trouble. I spent several days examining the traffic and looking at cables, NICs and such. Turns out that an improperlyshielded cable was run through the wall next to a really old photocopier. When the copier was turned on and used, it caused crosstalk. I noticed that the receptionist's routine of copying for everyone in the office occurred at the same times as the outages. I moved the copier and was a hero for a day and a half.

Another result of this exercise was finding several older network interface cards (NICs) that were "jabbering". They were failing, and as a result, outputting garbage packets on the wire. Replacing them increased the speed of the network immensely.

In the long run, you WILL want to go to a switched environment, but do it with forethought, planning and good reason. Not as a knee jerk reaction to an unexplained error condition. Your credibility is at stake if you don't find and correct the error.

by gernotlg

I've found some warnings on the servers event log, dunno if these would affect it....

"The DNS server for this DC does not support dynamic DNS. Add the DNS records from the file '%SystemRoot%\System32\Config\netlogon.dns' to the DNS server serving the domain referenced in that file. "

"The Windows Time Service was not able to find a Domain Controller. A time and date update was not possible. "

these and a few related ones are happening regulary.

by jose mir

Here is half point of help.
Does the Applications (programs) every machine run are installed in these machines? In other words, do your launch icons refer to applications which resides in the server?
If this is the case you will need to install every application localy to every machine, otherwise your network will ever be slow!

Regards,

Jose P Mir
jpm@jpmir.net

by gernotlg

The main app is on the server, other apps local. But the main app shared, so has to be in one spot, otherwise each WS will end up with different data.

by techmule

Sounds like your DNS isn't configured properly....taht may cause some slowness right there. Double check that it's configured correctly.

Also, are you running DHCP? For 8 PC's and a server, I'd (personal opinion) dump DHCP and configure the network on each PC/server. Just a little cleaner, can eliminate problems, and it's not like it's a major undertaking in this case. It might even be related to slowness as well.

As for the time server message (and possibly the dynamic DNS message aswell) it's common for services to get installed/turned on during the server build, but never get configured. It's entirely possible your slowness is related to this. unconfigured services can eat up extra resources, slowing the server down. Bottom line is, if you don't needit, turn it off.

Micro$oft is kind enough to take the "turn everything on" approach, with out bothering with "proper configuration". A good example in Win2000 server is SNMP. Try doing an SNMP scan of an Internet subnet....Win2K servers will telll you all kinds of info including EVERY account set up on the server. The default is SNMP on and read community string (password) "public". Try it sometime....you'll be blown away.....but I digress.

Anyway, go through your services, figure out what you don't need and turn it off....your server will be healthier for it.

have a good one.

by joemcse2001

Ignore the Windows Time Service error

Examine DNS forward lookup table to confirm entries for each workstation. If entries are missing workstations will use NETBIOS broadcasts for name resolution.

by admin

the scientific way and start testing response times, #'s of packets etc. and continue to isolate it to it's source possibly with analyst software like Etherpeek or whatever you chose or even start using the built in DOS\Windows tools? Maybe ya got a bad card spewing extra packets or something.

Also, cable testers don't have to be real expensive. We paid for ours in the first time we didn't have to have someone come out. You can again use software to determine throughput from point to pointafter you establish basic conductivity with an inexpensive fox and hound style tester.

1 W2K server and 8 clients shouldn't take too long to figure out as soon as you map out when and where it's all coming from and going.

by magnito

Check to see are you using more than one network protocol. I suggest if there are protocols that are not needed get rid of them they will slow down your network. Also try enabliing WINS because W2k seems to network better when this is enabled. Couldalso be Network Card related as stated before or even a hub. If you have a switch lying around ;p try it .. or borrow one .. see if its an issue with the hub
hope it helps
Paul

by jose mir

Yes, you should install this app. in every machine, so the execution (wich is local, to every workstation) uses modules locally. So, it needs to do the same with temp files and swapp space.
The only portion that you must locate centralized is the data base. With data base centralized in the server and the app distributed in every workstation you should have the beter performance.
There is no reason why you shouldn't do that.

Regards,

Jose P Mir
jpm@jpmir.net

by gernotlg

the printer in the downstairs office is connected to the hub/switch via a "NetComm Mini Print Server (NP3620)" This operates at 10BASET. However, I dont think it is the cause, because the switch/hub that its connected to is 100/10 and has different color leds showing which speed each port is running at. The port from the server and those going to the workstations show 100, and the port to the printer(via the miniprint server) shows 10.

any comments?

gernotlg@hotmail.com

by tbragsda

What you have described sounds just as it should. A 10mbps device plugged into a 10/100 switch or autosense hub should show 10mbps while a 100mpbs device attached to same will show 100.

Whats the results of some of the testing?

This discussion is closed to new replies.