Question Locked

regarding slow network

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

Hi,
In our organization we are using a file server and a local intranet server. this file server is connected to the local intranet server. we need to access the file server frequently for updation, file transfer etc. but nowadays our network is very slow. i don't know what to do. We are using "Net Gear manageable switches". regarding cabling there is no problem. so please can anyone help me in this issue.

Thanks in advance.

6 replies

by norman

You don't say how big the network is, or the topology / topography. What is accessed on the file server (database, files, distributed software, etc). Are all connections slow or just connections to the file server? Have you attempted to time any of the connections?

If possible can you isolate parts of the network and time connections?

Is there much network traffic?

What nature is the traffic? Web surfing, downloads (music, images, software,etc).

by kamal_rajans

At present we have 30 computers in the network and we need to access the file server for accessing image files (frequently).(since it is a production company),all the connections are slow when accessing files from the file server (such as file retrieval, editing etc) . we don't need to connect to the internet. the workstations are getting hanged, while files are being accessed from the file server.

by daveo2000

There are more things that can go wrong just based on hardware and software choices. Also, please don't look at the questions we are asking as just wanting you to provide us information so we can solve your problems. Think of it like this: we are providing you questions that you should research and try to solve by yourself. If, after doing that, you come up with more questions, then you should come back and ask more. We will be happy to help.

There can be quite a few issues that can slow a network down. Some that I have seen include:

New PC with an existing IP address (2 computers on the net with the same IP address)

DNS confused: All too often a person with less network experience than needed will be the one that sets up the network servers (DNS and friends). At one company where I worked we would have times when you couldn't even ping a Unix box by IP address. The only fix was to reboot the Windows DNS server. It had gotten confused and would interfere with direct IP pings! They finally called in somebody that knew how to set DNS up properly.

Really talkative applications: You should get a traffic monitor (like MRTG) to see what the traffic is and where it comes from. At one company we figured out that about 15% or our background noise (traffic when nothing was being done) was from Exchange/Outlook and Windows Network Share advertising. Every new Windows PC you put on the net will usually be shouting every couple of seconds "Hey, I am here. Who wants to connect to my file system?" That may not be as true with newer versions but it is worth checking.

by norman

Without more information regarding your setup, it is impossible to provide you with an answer however here are some obvious ideas assuming the network was faster at some point:
1) If network traffic is higher than you might expect:
1a check for virus infections.
1b if a single NIC is malfunctioning it can produce this effect, try switching each PC off to see if you can isolate the problem.
1c lack of server memory or damaged memory will cause speed issues, you may require new or more memory.
2If the network was always slow maybe you need to:
2a upgrade the switch (if you have one), consider a gigabyte switch and a gig NIC for the server.
2b NICs if they are not already 100Mb
2c cables (look for sharp bends, loose connectors)

by mellsworth

I have been bit time and time again with this one, especally on managed swtiches. Force the switch and the nic in the server to 100 Full duplex, there is an issue with all compliant switches (except those with a workaround) that if one is manually set to 100 full (server) the other (switch) set to auto can only see that the connection is 100MBS and not negotiate the duplex and defaults to half.
The other test I have is a down and dirty tool wsttcp.exe a simple commandline utility.
This will benchmark the connection with raw TCP traffic. If it is working within 80-99% on 100MB and 75-90% 1GB then it is a windows setting, if not, time for some layer 1 stuff ;)

Here is a server.bat for wcttcp
:home
wsttcp -r
goto home

and client.bat
wsttcp -t -n152513
pause

Good luck

This discussion is closed to new replies.