id="info"

Question

Locked

Browsing the Local Area Network...

By Shaun.G ·
I am using Win XP home. connecting to a lan of four pcs. One is a win2k standalone server. It is not a Primary Domain Controller.

When I try to browse the network, it takes up 20 seconds or more to respond, and shows that the explorer window is not responding for a period then it shows the workgroup. Then to open the workgroup, it takes the same length of time and does the same thing.

Can someone please advise me how to stop this occurring?

This conversation is currently closed to new comments.

10 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

You'll need to look at the setup of the W2k unit

by HAL 9000 Moderator In reply to Browsing the Local Area N ...

Make sure that it's sending out IP addresses or that you have Static IP Addresses on every computer that are different but in the same series.

Also make sure that every computer is on the same workgroup as this can slow things down considerably. You can also install the networking Protocol ISP/SXP NetBios and that may help you with connection speeds.

Col

Collapse -

Setup

by Shaun.G In reply to You'll need to look at th ...

Hi Hal,

The win2k machine is connected to a router and the router is a DHCP server. There are no static ip's.

I Will install those protocols onto all the pc's.

Thank you for the prompt response. It is much appreciated.

Collapse -

personally

by Dumphrey In reply to Setup

I would give the router interface and the server a fixed IP and use the server as a dhcp provider, that may speed up your network browsing as well. Another thought is to simply give each computer a fixed ip and create a custom hosts file for each =\ A little 1980's darpa but it works in small environments.

Collapse -

Router v Server

by Shaun.G In reply to personally

Hi Isaak,

I could do that, but the router is how I get my broadband, and I am not sure how it would be effected if I made the server the DHCP. These areas of networking are unknown to me, I hae a basic understanding of what it does, but that is it.

You mention a custom hosts file for each... this is not too much of an issue, I could possibly do this, but I am looking for the least maintenance route if possible. Surely host files can become tedious? I know its a small network.

I may try this suggestion yet, as the speed has not yet improved. As said, there is a second Win XP home pc on the network and this one has no problem with browsing.

Collapse -

Basiclly

by Dumphrey In reply to Router v Server

The advantage to using the router to provide dhcp is that it will import all DNS information as well as provide an ip address. But, this takes resources. Usually a server, no matter how old, has more resources then a router. Also, a server performs better if it has a consistent ip address, and other computers know exactly where to go to get information or shares. I would definitely assign a permanent ip to the server, get the dns info from an ipconfig /all on one of the XP boxes to use when assigning a fixed ip. I would be more then glad to expand at great length on any of this that interests you.

Collapse -

ISP/SXP NetBios

by Shaun.G In reply to You'll need to look at th ...

Hi Hal,

I added the ISP/SXP NetBios protocol, and has not helped the speed.

However, on the network, there is a second Win XP home machine, and this one does not have the same issues with network browsing speed as I do.

I do have a wireless network connection running too, would this have a negative effect on the connection speed?

Also, IPv6 is installed...will this effect it?

Collapse -

OK in that case look at the setup of that working XP Box

by HAL 9000 Moderator In reply to ISP/SXP NetBios

And see what if anything is different. As the other person who responded said set the Server a Static IP Address at the very least.

As for the WiFi connection these are slower than wired connections but shouldn't adversely affect things unless you are connecting through it. The current Max Speed on any WiFi Connection is 11 MBS where as the average wired LAN is 100 MBS so the wired one is just under 10 times faster. If you are using wireless that could be a reason for the slow response times.

Have you tried using NSLookup and pinging the server to see what happens?

Also if this is a wired connection are you sure that the Lead is working properly. I've seen some poorly made CAT5 leads cause some major problems over time and once someone made up a crossover cable and inserted it into the LAN which caused all sorts of problems. As today Crossover Cables are not made in a different colour cable or have anything but some sticky paper markings on them which fall off over time this is another possibility.

PM me if you need any help.

Col

Collapse -

Solution

by Shaun.G In reply to Browsing the Local Area N ...
Collapse -

re:browsing the local area network

by spamme In reply to Browsing the Local Area N ...

Try going to a command prompt and typing nbtstat -R. Also if one is windows XP and there ale older pc's reboot it.

Joe webmaster
http://www.networkbits.net

Back to Networks Forum
10 total posts (Page 1 of 1)  

Hardware Forums