Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Solutions for Network Slowness?

Status
Not open for further replies.

libroos

Technical User
Feb 16, 2001
195
SG
Hi all,

I have two client PCs, which are reading data from the main server via the network (thru' the hub).

Whenever the PCs attempted to log on to the main server or the application which requires log on, it is very slow, usually takes around 2 mins before we can see the log on screen.

Any advice?

Thank you.

Cheers,
Choon : )
 
Usually an indication that the cards are having difficulty talking to each other. Same Manufacturer? Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 
Hi Edfair,

Thank you for your keen response.

The two PCs are from the same manufacturer, hence the network cards are the same, from 3COM.

I am suspecting the settings from the protocols. Do I have to add in the NetBEUI protocols or is that TCP/IP protocols good enough?

Regards,
Choon : )
 
NetBEUI would not be a good idea... IPX/SPX might help (chatty, i know)...

install IPX/SPX and allow NetBIOS default through IPX/SPX Shane
and now for the impressive abbreviations:
DOA, SOL, AWOL, PEBKAC, id10t, FUBAR
 
You might also want to check out your cabling. Make sure that they are not run across florescent lights or close to power plugs.
 
Best to remove any services and protocols you are not using.TCP by itself is fine. Minimal probably should be:
Client for MSN
adapter
protocol
FPS for MSN
And look for IRQ conflicts with the NICs. Also look for link lights mostly off. You can get a broadcast storm that will cause problems like this. Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 
Hi all,

Thank you for all the responses. I have tried all the ways. The cables are not near any flourescent bulbs and others. Anyway the UTP cable is quite short.

I am suspecting the problem to be due to the server.

Have found another work-around way is to map the two userworkstations together and share the application between the two PCs. It helped, log on was much faster.

Cheers,
Choon : )
 
Take a look at your server's logs lately? You just might try it after firing off that application from the workstations. There's a chance something is going just slightly haywire on that server, anything from password mismatches to NIC driver problems and so on.

I also wouldn't rule out your UTP cable from the hub to the server, and I'd even check the hub out by using a crossover cable and direct wiring a workstation to the server, see if you still get the delays.

Another thing - check the hub itself, make sure you aren't taking partition errors (most hubs have a light for this).
 
Adding another protocol is unlikely to resolve any kind of network issue - more like obscure it!

NetBEUI will slow things down if you have more than 6 clients on your network - and if you're pure IP, then you don't need it.

If you have multiple users connecting to a share on a fileserver, then it's possible you're running out of WorkItems on that server - especially if you're seeing Remote Procedure Call errors.

If the log is showing rpc errors, then that is part of your issue. The time wasted in attempting to resolve these calls will slow login times in the manner you describe.

Do you have mapped network drives in your login script? If one or more of these is not resolving correctly, then login times will be slowed.


Hope this helps
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top