Network Stalls/Judders.

[David H.]

Hello,

Sorry for the poor subject line, but the best way to explain
is appears like the network stutters, or pauses momentarily.

2 * Win 98SE, 1 * WinXP Home, 1 * Wn XP Pro.
I have only noticed the problem on Win XP Pro.

I notice problems when copying to the XP Pro PC, or when
Browsing the network from the XP Pro PC, It's like it looses
connection to the network.

The only things I have found,
I managed to sit and ping the XP Pro PC for a while and
observed tome outs when pinging it from another PC:

c:\>ping 192.168.0.100

Pinging 192.168.0.100 with 32 bytes of data:

Reply from 192.168.0.100: bytes=32 time=7ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.0.100: bytes=32 time=29ms TTL=64

Ping statistics for 192.168.0.100:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 29ms, Average = 18ms

I have searched the news group for other indicators of what
maybe wrong. I read a response on another thread from
Steve Winograd regarding "NODE TYPES"

Interestingly on the WinXP Home, I have Node type of
"Broadcast" but there is no NODE Type in the registry??

On the Win XP Pro I have NODE Type "UNKNOWN"
also again there is no NODE Type in the registry???

All PC's have static IP's, XP PC's NetBios over TCP enabled.

Any help greatly appreciated.

Many Thanks - David

 

[Ron Lowe]

First off, ensure all firewall software on the problem machine is disabled,
or better still, un-installed as per the mfr's instructions.

Then try to ping the problem machine from itself, using it's own IP address.

This section here:


c:\>ping 192.168.0.100

Pinging 192.168.0.100 with 32 bytes of data:

Reply from 192.168.0.100: bytes=32 time=7ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.0.100: bytes=32 time=29ms TTL=64

would have me looking at the _hardware_ on the problem machine.
7ms and 29ms are way too long, and obviously timeouts are no good.

Bad / intermittent / incorrectly home-made cable?
Bad port on hub / switch?
Bad network card?

Set a non-stop ping from another machine going with the -t option:

ping -t 192.168.0.100

then go wiggle cables, swap cables, swap hub ports, etc.
See what makes any difference.

 

[David H.]

Hi Ron,

Thanks for that.
I'm actually on a Peer 2 Peer(Ad-Hoc?) Wireless network.
I have swapped the NetGear Wireless adapters and USB cables.
I have left ping running for quite a while on and from PC to PC.

The results are always the same, The XP Pro PC seems to time out.

The only thing I can see is this "Node Type" in ipconfig /all
There is no value in the registry, and it shows type "Unknown"
The XP Home PC is type "Broadcast", even though no value in registry.

From one of Steve W's links to MS I see the description.. But I don't
understand enough to know if I should add a "Node Type" to try and
force it to "Broadcast"??

Also I don't actually know what the right value should be?
I'm using Win98SE ICS, BUT with DHCP "disabled",
I have Static IP's set on all the PC's.
The XP PC's have Net BIOS over TCP/IP enabled.

Many Thanks - David

"Ron Lowe" <ron-msng@{d.e.l.e.t.e.}lowe-family.me.uk

 

[Ron Lowe]

Hi Ron,

Thanks for that.
I'm actually on a Peer 2 Peer(Ad-Hoc?) Wireless network.
I have swapped the NetGear Wireless adapters and USB cables.
I have left ping running for quite a while on and from PC to PC.

The results are always the same, The XP Pro PC seems to time out.

All the stuff about node type and netbios is irrelevant to the immediate
problem.
( unknown and broadcast are ok, since you ask.
The only issue arises if it's set to PtoP and you don't have a WINS
server. )

You need to get the IP layer working,
then worry about the other stuff which sits on top later.

The ping results you have strongly suggest a link-layer problem.
( cabling or wireless hardware / signal path type issue. )

I hadn't realised it was wireless.
In that case, I'd be looking at signal-to-noise ratio issues.

Interference issue?
Try changing channel numbers.
Re-position things away from any possible source of interference.

Range problem?
Try moving them closer.

Driver problem?
Have you installed the latest driver for the card..

Is there a diagnostic util that came with the wireless adapter?
It should show S/N ratio, interference levels,
signal strength, channel number etc.

Windows XP will give a signal strength report, what does it say?

 

[David H.]

Hi Ron,

I will try to answer your specific questions:

I hadn't realised it was wireless.
In that case, I'd be looking at signal-to-noise ratio issues.

+++ I have swapped around Wireless Adapters,
+++ The issue always points at the XP Pro PC.
+++ All D-Link drivers are uptodate.

Interference issue?
Try changing channel numbers.
Re-position things away from any possible source of interference.

+++ Tried various channels, always the same.
+++ I now have the XP PC's about 5 ft apart, still the same issue.
+++ Also switched off the Cordless Phone, just in case.

Is there a diagnostic util that came with the wireless adapter?
It should show S/N ratio, interference levels,
signal strength, channel number etc.
Windows XP will give a signal strength report, what does it say?

+++ When in Ad-Hoc mode the utilities don't give full diagnostic info
+++ This is also confirmed in the users docs.
+++ XP indicates very Good to Excelent signals.

Maybe I have an issue with USB ports on MOBO??
I will check if updates are availble for USB Mobo Drivers?

Many Thanks - David