General discussion

Locked

Intermittant slow network connection

By mark ·
I have pure TCPIP ethernet network consisting of one Windows 2000 server and three Window 2000 Professional. Internet access is provide by Verizon DSL modem and a Linksys DSL router/4 port switch. When I connect my Fluke Network one touch diagnosis tool, I see alot of broadcast such as 80 to 100 percent. The DSL router acts as a DHCP and assinges IP address of 192.168.1.* with subnet mast of 255.255.255.0. This router also acts as a Gateway. Currently all stations are connected to the Linksys DSL router/switch.

Every now and then accessing file and printer on the server as well as accessing the internet becomes extremely slow. The last change I made was to make all stations network cards from auto sensing to 100 full duplex and on the server from hardware seclect to 100 full duplex.

When I connect my Fluke Network tester to any of the stations I see to IP addresses one on the local 192.168.1.* and another on 169.254.*.* networks. But when I look at the IPCONFIG I only see one address on the 192.168.1.*. Any idea please?

Mark

This conversation is currently closed to new comments.

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

All Comments

Collapse -

by evkuo In reply to Intermittant slow network ...

It's hard to say, but generally speaking, whenever I've seen similar issues that crop up, I tend to think a virus. It'd be worth while to run a scan just to be sure. Also, if you hard code 100FD on the workstation/server side, I'd also do the same on the switch side, but that doesn't sound like it is your problem.
I'd say if you've run an IPCONFIG /ALL on all the workstations and the server and you don't see any 169.254.*.* listed, then I'd check the Linksys unit.

Collapse -

by shawn In reply to Intermittant slow network ...

As to the slow network connectivity: are ayou sure that the router you're connected to support full duplex? If it doesn't, or it does but it's not enabled for full duplex, that could cause some of the lag times working amongst the machines connected to it.

As to the IP addressing: do you have more than one network card in the machines? the 169.254.x.x address range is used by Windows machines (Windows 98 and newer) for automatic IP addressing - it's a default IP that a system can use when it can't contact a DHCP server to get an actual IP address.

Hope this helps.

Cheers,
Shawn

Collapse -

by joshua.stroud In reply to Intermittant slow network ...

It seems to me that there is a configuration problem in your TCP/IP protocl stack/DHCP implementation.

The reason that I say this is that 169.254.x.x is the IP range that Windows 2000 uses to autoconfigure a NIC that could not obtain a valid DHCP address lease.

Try configuring your PCs and Server (especially the server) with static IP addressing and see if the problem goes away. If it does (as I suspect that it will), simply change the address scope for your DHCP to exclude the static IP for the server and you can either keep the workstations on static addressing or reconfigure them to use DHCP through the router, or through the Windows 2000 by installing the DHCP Server Service.

Collapse -

by joshua.stroud In reply to

As for the speed problem that you are having, It could be due to the addressing problem, or it could be due to another issue. You mentioned a Windows 2000 server and workstations. Is the server configured as a stand-alone server or as a domain controller?

Collapse -

by steffeno In reply to Intermittant slow network ...

Firstly, just to repaint the picture of this scenario. You connected 4 stations (1 server and 3 workstation) to the 4 port Linksys DSL router. The Wan port goes to the Verizon DSL Modem. In regards to broadcast, there's a couple of possibility. It could be you have a faulty network card or patch cable. And are you running other services on the server? DHCP/DNS/WINS? the dhcp could be giving out the same range of ip addresses as the router. You could check your tcp/ip settings on every machine. Remove those protocols that you are not using. Or you could setup the network in a way that the workstations gets ip address from the windows 2000 server DHCP and the server point to the router. You will need to enale RRAS on the server. Its not difficult to do. Hope it helps.

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums