Long delay to find the other computer on network

[BP]

I have a simple 2 computer home network set up with a crossover cable. The
serving machine runs XP-SP2 and the client runs W98SE. The XP server had an
on-board Gigabit LAN controller (Asus P4C800-E) that was connected to the
cable modem and a Linksys NIC to connect to the LAN. At one time everything
worked perfectly, very fast, and no burps, beeps, or delays. Then my
server's mainboard died. A new (Intel) mainboard was installed and a repair
install of XP was performed. The new board does not have built in Gigabit
LAN, so a 3-Com NIC was added and connects to the modem. The same Linksys
NIC connectsto the LAN. After the system was back up and running there were
a *lot* of bugs in the works. One was that the network connection could not
be re-established. After much research I was able to find and delete phantom
devices from the system, including the phantom Gigabit LAN controller and
gain access to the network connection. But only by changing the setting
under TCP/IP properties from "Obtain IP address automatically" and
manually assign address 192.168.0.1 (and the 255 subnet mask). By default
the "Use the following DNS server address" option is selected, but I left
this blank. Now the network works, but it is very slow to find the W98
computer in both Network Neighborhood and in Windows Explorer. The hourglass
shows for 30 to 60 seconds before the files on W98 show up. Same with the
shared printer connected to the W98. Sometimes it won't even show at all
(grayed out). But, going the other way (from the W98 computer) everything is
just like before: no delay, very fast. Shared printers on the XP machine
work great. ICS works great. And, once the XP does find the W98,
transferring files, data, and print jobs goes normally, no delays. It is
only *finding* the W98 computer on the network that goes slow.
I have lived with this setup like this for several months now. It works, but
it's just annoying as all hell. Every now and then I see a post or webpage
that seems to relate to my problem and I try the fix suggested, make the
setting changes, edit the registry, hang garlic from the monitor, but no
solution. I've tried a *lot* of things, all the usual suspects,
so please bear with me if you offer stuff I've done before. This also means
that a lot of original settings, files, and the printer's driver have been
changed, reinstalled, or deleted. I know the ultimate solution is to clean
install XP, but I wonder if anyone knows a less painful fix. Please let me
know if you need any more info, I'm attempting to keep this long story
short.

 

[windwalker]

Did u try adding the windows 98 computer name and ip address onto the
windows xp hosts file (hosts file location -
\%windir\system32\drivers\etc\hosts
and do you have netbios/netbeui installed on both computers
Fahim Mohammed

 

[Chuck]

I have a simple 2 computer home network set up with a crossover cable. The
serving machine runs XP-SP2 and the client runs W98SE. The XP server had an
on-board Gigabit LAN controller (Asus P4C800-E) that was connected to the
cable modem and a Linksys NIC to connect to the LAN. At one time everything
worked perfectly, very fast, and no burps, beeps, or delays. Then my
server's mainboard died. A new (Intel) mainboard was installed and a repair
install of XP was performed. The new board does not have built in Gigabit
LAN, so a 3-Com NIC was added and connects to the modem. The same Linksys
NIC connectsto the LAN. After the system was back up and running there were
a *lot* of bugs in the works. One was that the network connection could not
be re-established. After much research I was able to find and delete phantom
devices from the system, including the phantom Gigabit LAN controller and
gain access to the network connection. But only by changing the setting
under TCP/IP properties from "Obtain IP address automatically" and
manually assign address 192.168.0.1 (and the 255 subnet mask). By default
the "Use the following DNS server address" option is selected, but I left
this blank. Now the network works, but it is very slow to find the W98
computer in both Network Neighborhood and in Windows Explorer. The hourglass
shows for 30 to 60 seconds before the files on W98 show up. Same with the
shared printer connected to the W98. Sometimes it won't even show at all
(grayed out). But, going the other way (from the W98 computer) everything is
just like before: no delay, very fast. Shared printers on the XP machine
work great. ICS works great. And, once the XP does find the W98,
transferring files, data, and print jobs goes normally, no delays. It is
only *finding* the W98 computer on the network that goes slow.
I have lived with this setup like this for several months now. It works, but
it's just annoying as all hell. Every now and then I see a post or webpage
that seems to relate to my problem and I try the fix suggested, make the
setting changes, edit the registry, hang garlic from the monitor, but no
solution. I've tried a *lot* of things, all the usual suspects,
so please bear with me if you offer stuff I've done before. This also means
that a lot of original settings, files, and the printer's driver have been
changed, reinstalled, or deleted. I know the ultimate solution is to clean
install XP, but I wonder if anyone knows a less painful fix. Please let me
know if you need any more info, I'm attempting to keep this long story
short.

First, make sure that you have only NetBIOS Over TCP/IP, and TCP/IP, installed
as protocols. Extra protocols like IPX/SPX and NetBEUI will cause this problem.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

Next, look at the browser (no, I'm not talking about Internet Explorer)
situation. When you combine Windows 98 and XP on the network, this is a
problem.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

 

[BP]

Did u try adding the windows 98 computer name and ip address onto the
windows xp hosts file (hosts file location -
\%windir\system32\drivers\etc\hosts

No, I didn't. Something new.
Currently the hosts file contains only " 127.0.0.1 Local Host "
What would I add? The W98 machine is set to automatic IP. Would I still use
192.168.0.2?

The "Hosts.ics" file contains:
192.168.0.1 [Correctname].[WrongWorkgroup].net
192.168.0.95 [Correctname].[WrongWorkgroup].net
WrongWorkgroup is MSHOME rather than the name given on both computers. But
ICS works fine. Nothing?

No entries in Lmhosts.
Networks file onlt contains "loopback 127"

and do you have netbios/netbeui installed on both computers Yes.

Fahim Mohammed

Thanks

 

[BP]

First, make sure that you have only NetBIOS Over TCP/IP, and TCP/IP,
installed
as protocols. Extra protocols like IPX/SPX and NetBEUI will cause this
problem.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>

Got that covered

Next, look at the browser (no, I'm not talking about Internet Explorer)
situation. When you combine Windows 98 and XP on the network, this is a
problem.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

This I haven't seen. I will give that a try (time permitting) and post back.
Hadn't seen your site before either. Looks good. I'll read more.

Thanks

http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
Got that covered

http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html
This I haven't seen. I will give that a try (time permitting) and post back.
Hadn't seen your site before either. Looks good. I'll read more.

Thanks

 

[BP]

Did u try adding the windows 98 computer name and ip address onto the
windows xp hosts file (hosts file location -
\%windir\system32\drivers\etc\hosts

No, I didn't. Something new.
Currently the hosts file contains only " 127.0.0.1 Local Host "
What would I add? The W98 machine is set to automatic IP. Would I still
use 192.168.0.2?

The "Hosts.ics" file contains:
192.168.0.1 [Correctname].[WrongWorkgroup].net
192.168.0.95 [Correctname].[WrongWorkgroup].net
WrongWorkgroup is MSHOME rather than the name given on both computers. But
ICS works fine. Nothing?

No entries in Lmhosts.
Networks file onlt contains "loopback 127"

and do you have netbios/netbeui installed on both computers Yes.

Fahim Mohammed

Thanks

OK. That didn't work. It messed thing up. I can ping the W98 at 192.168.0.95
so I added that IP along with the W98 computer name using Wordpad and saved.
Rebooted. Windows explorer was slower than before and once the"Microsoft
Windows Network" folder did open (45sec) the Workgroup folder took even
longer to open and when it did the W98 computer was not listed. I replaced
the backup host file and rebooted, still no W98 computer showing. So I
pinged it, and then it showed up in WExplorer. Wierd?

 

[BP]

First, make sure that you have only NetBIOS Over TCP/IP, and TCP/IP,
installed
as protocols. Extra protocols like IPX/SPX and NetBEUI will cause this
problem.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

Next, look at the browser (no, I'm not talking about Internet Explorer)
situation. When you combine Windows 98 and XP on the network, this is a
problem.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

Additional info: I once had mapped a couple of drives on the W98 computer in
WXP, back when the original mainboard was in the box. I didn't like the
setup because the W98 isn't always switched on and that caused problems with
explorer trying to find the "missing" drives. So I removed the mapped drives
in My Computer after the mainboard was replaced. Curiously, one (only one)
of the mapped drive names keeps showing up in "My Network Places". I delete
it, it comes back. I share drive D on the W98 so the drive shows as W98-D in
Windows explorer, but that is also the name that I gave the mapped drive. So
there may be no issue with the mapping, it may be just the shared drive
jumping to the head of the que. Is this any help?

 

[Chuck]

Additional info: I once had mapped a couple of drives on the W98 computer in
WXP, back when the original mainboard was in the box. I didn't like the
setup because the W98 isn't always switched on and that caused problems with
explorer trying to find the "missing" drives. So I removed the mapped drives
in My Computer after the mainboard was replaced. Curiously, one (only one)
of the mapped drive names keeps showing up in "My Network Places". I delete
it, it comes back. I share drive D on the W98 so the drive shows as W98-D in
Windows explorer, but that is also the name that I gave the mapped drive. So
there may be no issue with the mapping, it may be just the shared drive
jumping to the head of the que. Is this any help?

Which computer is this persistent share showing up on? Which part of Network
Neighborhood?

Please provide "browstat status" and "ipconfig /all" from the Windows XP
computer, and "ipconfig /all" from the Windows 98 computer. Read this article,
and linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

 

[BP]

Which computer is this persistent share showing up on? Which part of
Network
Neighborhood?

It shows on the XP-SP2 machine. In "My Network Places" along with "Entire
Network".
It also shows on the XP-SP2 machine in My Network Places > Entire Network >
Microsoft Windows Network > 624OHR (Workgroup) > FRED (Computer Name-W98) >
CELLAR-D (Folder Share Name).

The XP machine is BRUCE in the 624OHR workgroup.

Please provide "browstat status" and "ipconfig /all" from the Windows XP
computer, and "ipconfig /all" from the Windows 98 computer. Read this
article,
and linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

Thanks Chuck for bearing with me on this. The hardest part is knowing how to
ask the question(s).
I will compile a more intelligent post with the info you requested. I've
already got the ipconfig data but will need to download, install, and run
browstat. I also want to read more on your site to try and educate myself
and not sound so lame. Give me a few days and I will post back.

 

[BP]

Which computer is this persistent share showing up on? Which part of
Network
Neighborhood?

Please provide "browstat status" and "ipconfig /all" from the Windows XP
computer, and "ipconfig /all" from the Windows 98 computer. Read this
article,
and linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

Chuck, here is the info from both computers

Browstat Status Data:

Status for domain 624OHR on transport
\Device\NetBT_Tcpip_{4AA75384-C1AF-46A5-B9EE-BE9E43855529}
Browsing is active on domain.
Master name cannot be determined from GetAdapterStatus. Using \\BRUCE
Master browser is running build 2600
1 backup servers retrieved from master BRUCE
\\BRUCE
There are 2 servers in domain 624OHR on transport
\Device\NetBT_Tcpip_{4AA75384-C1AF-46A5-B9EE-BE9E43855529}
There are 1 domains in domain 624OHR on transport
\Device\NetBT_Tcpip_{4AA75384-C1AF-46A5-B9EE-BE9E43855529}


Status for domain 624OHR on transport
\Device\NetBT_Tcpip_{B69BE971-07EC-4DAF-8B20-3F137520E309}
Browsing is active on domain.
Master browser name is: BRUCE
Master browser is running build 2600
1 backup servers retrieved from master BRUCE
\\BRUCE
There are 2 servers in domain 624OHR on transport
\Device\NetBT_Tcpip_{B69BE971-07EC-4DAF-8B20-3F137520E309}
There are 1 domains in domain 624OHR on transport
\Device\NetBT_Tcpip_{B69BE971-07EC-4DAF-8B20-3F137520E309}

*****
Browstat Listwfw Data:

Usage: BROWSTAT LISTWFW <Domain>
List WFW servers that are actually running browser.

Type "BROWSTAT" to list all switches.

*****
(Windows XP Home w/SP2)
Windows IP Configuration

Windows IP Configuration Host Name . . . . . . . . . . . . : bruce
Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . .
.. : Unknown IP Routing Enabled. . . . . . . . : Yes WINS Proxy
Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . :
hsd1.ma.comcast.net.Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : Description . . . . . . . . . .
.. : Linksys LNE100TX(v5) Fast Ethernet Adapter Physical Address. . .
.. . . . . . : 00-0C-41-E5-D5-78 Dhcp Enabled. . . . . . . . . . . :
No IP Address. . . . . . . . . . . . : 192.168.0.1 Subnet Mask
.. . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . .
.. : Ethernet adapter Broadband: Connection-specific DNS Suffix . :
hsd1.ma.comcast.net. Description . . . . . . . . . . . : 3Com
EtherLink XL 10/100 PCI For Complete PC Management NIC (3C905C-TX)
Physical Address. . . . . . . . . : 00-01-03-34-24-5F Dhcp Enabled. .
.. . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 65.96.154.232 Subnet Mask . . . .
.. . . . . . . : 255.255.248.0 Default Gateway . . . . . . . . . :
65.96.152.1 DHCP Server . . . . . . . . . . . : 68.87.71.11
DNS Servers . . . . . . . . . . . : 68.87.71.226
68.87.73.242 Lease Obtained. . . . . . . . . . : Friday, December 02,
2005 6:55:03 AM Lease Expires . . . . . . . . . . : Monday, December
05, 2005 6:49:36 AM
*****
(And if it matters)
PPP Adapter 110.net on BRUCE:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 216.41.121.119
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 216.41.121.119
DNS Servers . . . . . . . . . . . : 216.41.101.17
NetBIOS over Tcpip ..........: Disabled

*****
(Windows 98SE)
Windows 98 IP Configuration Host Name . . . . . . . . . : FRED.mshome.net
DNS Servers . . . . . . . . : 192.168.0.1 Node Type . . . . . . . . . :
Mixed NetBIOS Scope ID. . . . . . : IP Routing Enabled. . . . . : No WINS
Proxy Enabled. . . . . : No NetBIOS Resolution Uses DNS : No0 Ethernet
adapter : Description . . . . . . . . : PPP Adapter. Physical Address. . . .
.. . : 44-45-53-54-00-00 DHCP Enabled. . . . . . . . : Yes IP Address. . . .
.. . . . . : 0.0.0.0 Subnet Mask . . . . . . . . : 0.0.0.0 Default Gateway .
.. . . . . : DHCP Server . . . . . . . . : 255.255.255.255 Primary WINS
Server . . . . : Secondary WINS Server . . . : Lease Obtained. . . . . . .
: Lease Expires . . . . . . . : 1 Ethernet adapter : Description . . . . .
.. . . : Linksys LNE100TX(v5) Fast Ethernet Adapter NDIS5 Driver Physical
Address. . . . . . : 00-0C-41-E5-D5-E7 DHCP Enabled. . . . . . . . : Yes IP
Address. . . . . . . . . : 192.168.0.95 Subnet Mask . . . . . . . . :
255.255.255.0 Default Gateway . . . . . . : 192.168.0.1 DHCP Server . . . .
.. . . . : 192.168.0.1 Primary WINS Server . . . . : Secondary WINS Server .
.. . : Lease Obtained. . . . . . . : 12 02 05 8:18:06 AM Lease Expires . . .
.. . . . : 12 09 05 8:18:06 AM

*****
These are my network setting for (Bruce)
BRUCE (XP-Home), Network Connections, Local Area Connection, Properties

General Tab:
Client for MS Networks
File & Printer Sharing for MS Networks
TCP/IP
Both boxes checked

TCP/IP Properties:
(Un-selected Obtain IP address automativally. Was selected
pre-repair install.)
Use the following IP: 192.168.0.1 Mask: 255.255.255.0
(Obtain DNS un-selected - default)
Use the following DNS: Blank.

TCP/IP Protocols Advanced Settings
IP Settings Tab: IP Address : "As Above" . Autmatic metric
checked.
DNS Tab: No server addresses. "Append Primary" selected. "Append
parent" checked. Register this connection checked.
WINS Tab: "Enable LMHosts" checked. "Enable NetBIOS" selected.
Options Tab: "TCP/IP filtering" only. Properties: "Permit all" on
all 3.

Back in LAC, Properties window
AUTHENTICATION Tab:
"Enable IEEE802..." checked. "Authenticate as computer..." is
checked.

ADVANCED Tab: Windows Firewall > Settings
General Tab: On.
Exceptions Tab: "File & Print Sharing" is checked. "WinMX
Application" is checked. "Display a..." is checked.
Advanced Tab: "Local Area Connection" checked. "110.net" checked.
"Broadband Connection" checked.

Back in the Network Connection Window > Advanced Menu > Advanced Settings
LAC Bindings: "File & Print Sharing" and "Client for MS Networks"
plus TCP/IP for both.
Broadband Bindings: "Client for MS Networks" plus TCP/IP only.
Provider order: "MWN" listed first. "MS Terminal"... next. Then
"Web Client Net..."

Back in the Network Connection Window > Advanced Menu > Network
Identification > Change
Computer name: bruce
Workgroup: 624OHR
More: "Primary DNS Suffix" blank. NetBIOS Computer name: BRUCE.

******
These are my network setting for (Fred)
FRED (W98SE), Control Panel > Network

Configuration:
Client for MS Networks
Dial up Adapter
Linksys Adapter
TCP/IP Dial Up
TCP/IP Linksys
File and Print Sharing

Windows Logon

File & Print Sharing:
Browse Master : Automatic
LM Announce: No

Client for MS Networks:
Only "Quick Logon" is selected.

TCP/IP Linksys:
IP Address: "Obtain IP address automatically" checked.
WINS Config: "Use DHCP for WINS Resolution" selected. Only.
GATEWAY: Blank.
DNS CONFIG: "Disable DNS" selected.
BINDINGS: "Client for MS Networks" & "File & Printer..." checked.
ADVANCED: "Allow Binding to ATM" : No. "Set this protocol...."
checked.
NETBIOS: "NetBIOS over TCP/IP" checked and gray.

Back in the Network Window
IDENTIFICATION Tab:
Computer Name: FRED
Workgroup: 624OHR
Computer Description: CELLAR

ACCESS CONTROL Tab:
"Share level access control" is selected.

******

 

[BP]

Which computer is this persistent share showing up on? Which part of
Network
Neighborhood?

Please provide "browstat status" and "ipconfig /all" from the Windows XP
computer, and "ipconfig /all" from the Windows 98 computer. Read this
article,
and linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

CDiagnosis V1.33
Start diagnosis for BRUCE

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
IPC$ Remote IPC
print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers
HOLDING D:\DOWNLOADS\HOLDING
HUMOR F:\HUMOR
KAREN E:\KAREN
KRISTIN E:\KRISTIN
MP3 F:\MP3
NICOLE E:\NICOLE
PICTURES F:\PICTURES
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

WAV FILES F:\WAV FILES
X _BACKUPS F:\X _BACKUPS
LaserJet LPT1: Spooled LaserJet
Office-MP780 USB001 Spooled Canon MP780 Series Printer
Printer OLEtoADI Spooled Phantom AutoCAD OLE/ADI Printer
The command completed successfully.


Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\BRUCE The Computer
\\FRED Cellar
The command completed successfully.


Full Targets BRUCE 192.168.0.1 FRED 192.168.0.95 127.0.0.1

Target BRUCE

"BRUCE ping BRUCE"



Pinging bruce [65.96.154.232] with 32 bytes of data:



Reply from 65.96.154.232: bytes=32 time<1ms TTL=128

Reply from 65.96.154.232: bytes=32 time<1ms TTL=128

Reply from 65.96.154.232: bytes=32 time<1ms TTL=128

Reply from 65.96.154.232: bytes=32 time<1ms TTL=128



Ping statistics for 65.96.154.232:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"BRUCE net view BRUCE"

Shared resources at BRUCE

The Computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
HOLDING Disk
HUMOR Disk
KAREN Disk
KRISTIN Disk
LaserJet Print LaserJet
MP3 Disk
NICOLE Disk
Office-MP780 Print Canon MP780 Series Printer
PICTURES Disk
Printer Print Phantom AutoCAD OLE/ADI Printer
SharedDocs Disk
WAV FILES Disk
X _BACKUPS Disk
The command completed successfully.


Target 192.168.0.1

"BRUCE ping 192.168.0.1"



Pinging 192.168.0.1 with 32 bytes of data:



Reply from 192.168.0.1: bytes=32 time<1ms TTL=128

Reply from 192.168.0.1: bytes=32 time<1ms TTL=128

Reply from 192.168.0.1: bytes=32 time<1ms TTL=128

Reply from 192.168.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"BRUCE net view 192.168.0.1"

Shared resources at 192.168.0.1

The Computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
HOLDING Disk
HUMOR Disk
KAREN Disk
KRISTIN Disk
LaserJet Print LaserJet
MP3 Disk
NICOLE Disk
Office-MP780 Print Canon MP780 Series Printer
PICTURES Disk
Printer Print Phantom AutoCAD OLE/ADI Printer
SharedDocs Disk
WAV FILES Disk
X _BACKUPS Disk
The command completed successfully.


Target FRED

"BRUCE ping FRED"



Pinging FRED.hsd1.ma.comcast.net [66.30.124.98] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 66.30.124.98:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"BRUCE net view FRED"


Target 192.168.0.95

"BRUCE ping 192.168.0.95"



Pinging 192.168.0.95 with 32 bytes of data:



Reply from 192.168.0.95: bytes=32 time<1ms TTL=128

Reply from 192.168.0.95: bytes=32 time<1ms TTL=128

Reply from 192.168.0.95: bytes=32 time<1ms TTL=128

Reply from 192.168.0.95: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.0.95:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"BRUCE net view 192.168.0.95"


Target 127.0.0.1

"BRUCE ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"BRUCE net view 127.0.0.1"

Shared resources at 127.0.0.1

The Computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
HOLDING Disk
HUMOR Disk
KAREN Disk
KRISTIN Disk
LaserJet Print LaserJet
MP3 Disk
NICOLE Disk
Office-MP780 Print Canon MP780 Series Printer
PICTURES Disk
Printer Print Phantom AutoCAD OLE/ADI Printer
SharedDocs Disk
WAV FILES Disk
X _BACKUPS Disk
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32

Target www.yahoo.com

"BRUCE ping www.yahoo.com"



Pinging www.yahoo.akadns.net [68.142.226.34] with 32 bytes of data:



Reply from 68.142.226.34: bytes=32 time=23ms TTL=49

Reply from 68.142.226.34: bytes=32 time=23ms TTL=49

Reply from 68.142.226.34: bytes=32 time=22ms TTL=49

Reply from 68.142.226.34: bytes=32 time=22ms TTL=49



Ping statistics for 68.142.226.34:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 22ms, Maximum = 23ms, Average = 22ms


Target 66.94.230.32

"BRUCE ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=84ms TTL=46

Reply from 66.94.230.32: bytes=32 time=95ms TTL=46

Reply from 66.94.230.32: bytes=32 time=94ms TTL=46

Reply from 66.94.230.32: bytes=32 time=87ms TTL=46



Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 84ms, Maximum = 95ms, Average = 90ms


End diagnosis for BRUCE

 

[BP]

Which computer is this persistent share showing up on? Which part of
Network
Neighborhood?

Please provide "browstat status" and "ipconfig /all" from the Windows XP
computer, and "ipconfig /all" from the Windows 98 computer. Read this
article,
and linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

Browstat ListWFW using correct syntax

Calling NetServerEnum to enumerate WFW servers.
1 WFW servers returned. 1 total.
The following are running the browser:

\\FRED W95 04.00 (W,S,PQ,WFW,PBR,BBR,W95) Cellar

 

[Chuck]

<SNIP CDiag run for Bruce>

Very interesting, that. Look at pinging Bruce and Fred.

"BRUCE ping BRUCE"

Pinging bruce [65.96.154.232] with 32 bytes of data:

Reply from 65.96.154.232: bytes=32 time<1ms TTL=128

"BRUCE ping FRED"

Pinging FRED.hsd1.ma.comcast.net [66.30.124.98] with 32 bytes of data:

Request timed out.

Now look at your CDiag setup (presumably based upon ipconfig logs).
BRUCE 192.168.0.1 FRED 192.168.0.95

Have Bruce and Fred always been connected as server - client?

How about pinging each computer from Fred (I assume Fred is the Windows 98
computer?)? What ip addresses, and what results, do you get?

 

[BP]

I have a simple 2 computer home network set up with a crossover cable.
The
serving machine runs XP-SP2 and the client runs W98SE. The XP server
had
an
on-board Gigabit LAN controller (Asus P4C800-E) that was connected to
the
cable modem and a Linksys NIC to connect to the LAN. At one time
everything
worked perfectly, very fast, and no burps, beeps, or delays. Then my
server's mainboard died. A new (Intel) mainboard was installed and a
repair
install of XP was performed. The new board does not have built in
Gigabit
LAN, so a 3-Com NIC was added and connects to the modem. The same
Linksys
NIC connectsto the LAN. After the system was back up and running there
were
a *lot* of bugs in the works. One was that the network connection
could
not
be re-established. After much research I was able to find and delete
phantom
devices from the system, including the phantom Gigabit LAN controller
and
gain access to the network connection. But only by changing the
setting
under TCP/IP properties from "Obtain IP address automatically" and
manually assign address 192.168.0.1 (and the 255 subnet mask). By
default
the "Use the following DNS server address" option is selected, but I
left
this blank. Now the network works, but it is very slow to find the W98
computer in both Network Neighborhood and in Windows Explorer. The
hourglass
shows for 30 to 60 seconds before the files on W98 show up. Same with
the
shared printer connected to the W98. Sometimes it won't even show at
all
(grayed out). But, going the other way (from the W98 computer)
everything
is
just like before: no delay, very fast. Shared printers on the XP
machine
work great. ICS works great. And, once the XP does find the W98,
transferring files, data, and print jobs goes normally, no delays. It
is
only *finding* the W98 computer on the network that goes slow.
I have lived with this setup like this for several months now. It
works,
but
it's just annoying as all hell. Every now and then I see a post or
webpage
that seems to relate to my problem and I try the fix suggested, make
the
setting changes, edit the registry, hang garlic from the monitor, but
no
solution. I've tried a *lot* of things, all the usual suspects,
so please bear with me if you offer stuff I've done before. This also
means
that a lot of original settings, files, and the printer's driver have
been
changed, reinstalled, or deleted. I know the ultimate solution is to
clean
install XP, but I wonder if anyone knows a less painful fix. Please
let
me
know if you need any more info, I'm attempting to keep this long story
short.

First, make sure that you have only NetBIOS Over TCP/IP, and TCP/IP,
installed
as protocols. Extra protocols like IPX/SPX and NetBEUI will cause
this
problem.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

Next, look at the browser (no, I'm not talking about Internet
Explorer)
situation. When you combine Windows 98 and XP on the network, this is
a
problem.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from
experience.
My email is AT DOT
actual address pchuck mvps org.

Additional info: I once had mapped a couple of drives on the W98
computer
in
WXP, back when the original mainboard was in the box. I didn't like the
setup because the W98 isn't always switched on and that caused problems
with
explorer trying to find the "missing" drives. So I removed the mapped
drives
in My Computer after the mainboard was replaced. Curiously, one (only
one)
of the mapped drive names keeps showing up in "My Network Places". I
delete
it, it comes back. I share drive D on the W98 so the drive shows as
W98-D
in
Windows explorer, but that is also the name that I gave the mapped
drive.
So
there may be no issue with the mapping, it may be just the shared drive
jumping to the head of the que. Is this any help?

Which computer is this persistent share showing up on? Which part of
Network
Neighborhood?

Please provide "browstat status" and "ipconfig /all" from the Windows XP
computer, and "ipconfig /all" from the Windows 98 computer. Read this
article,
and linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

<SNIP CDiag run for Bruce>

Very interesting, that. Look at pinging Bruce and Fred.

"BRUCE ping BRUCE"

Pinging bruce [65.96.154.232] with 32 bytes of data:

Reply from 65.96.154.232: bytes=32 time<1ms TTL=128

"BRUCE ping FRED"

Pinging FRED.hsd1.ma.comcast.net [66.30.124.98] with 32 bytes of data:

Request timed out.

Now look at your CDiag setup (presumably based upon ipconfig logs).
BRUCE 192.168.0.1 FRED 192.168.0.95

Have Bruce and Fred always been connected as server - client?

How about pinging each computer from Fred (I assume Fred is the Windows 98
computer?)? What ip addresses, and what results, do you get?

SNIP

"Have Bruce and Fred always been connected as server - client?"
That would be yes, and no. Yes, only these two computers have ever been
networked together. But remember, BRUCE (WXP) had the motherboard failure
and repair install of XP, so maybe it is a "new" computer.

"(I assume Fred is the Windows 98 computer?)"
Yes.

"How about pinging each computer from Fred"
Fred's cool. Fred pings all 4 ways.
Pings Fred @fred.mshome.net 192.168.0.95
Pings 192.168.0.95
Pings Bruce @bruce.mshome.net 192.168.0.1
Pings 192.168.0.1

But BRUCE only pings 3 ways:
Pings Bruce @65.96.154.232
Pings 192.168.0.1
Does not ping Fred. It tries the address that is used for the broadband
connection on the 3Com card. (The LAN is on the Linksys card.)
Pings 192.168.0.95

BUT
If I disable the 3Com (Broadband) connection, then Bruce can ping Fred @
192.168.0.95
And if I ping 65.96.154.232 I get "Destination host unreachable"

I then re-engage the 3Com card and I can ping 65.96.154.232.

Thanks Chuck.

 

[BP]

I have a simple 2 computer home network set up with a crossover
cable.
The
serving machine runs XP-SP2 and the client runs W98SE. The XP server
had
an
on-board Gigabit LAN controller (Asus P4C800-E) that was connected to
the
cable modem and a Linksys NIC to connect to the LAN. At one time
everything
worked perfectly, very fast, and no burps, beeps, or delays. Then my
server's mainboard died. A new (Intel) mainboard was installed and a
repair
install of XP was performed. The new board does not have built in
Gigabit
LAN, so a 3-Com NIC was added and connects to the modem. The same
Linksys
NIC connectsto the LAN. After the system was back up and running
there
were
a *lot* of bugs in the works. One was that the network connection
could
not
be re-established. After much research I was able to find and delete
phantom
devices from the system, including the phantom Gigabit LAN controller
and
gain access to the network connection. But only by changing the
setting
under TCP/IP properties from "Obtain IP address automatically" and
manually assign address 192.168.0.1 (and the 255 subnet mask). By
default
the "Use the following DNS server address" option is selected, but I
left
this blank. Now the network works, but it is very slow to find the
W98
computer in both Network Neighborhood and in Windows Explorer. The
hourglass
shows for 30 to 60 seconds before the files on W98 show up. Same with
the
shared printer connected to the W98. Sometimes it won't even show at
all
(grayed out). But, going the other way (from the W98 computer)
everything
is
just like before: no delay, very fast. Shared printers on the XP
machine
work great. ICS works great. And, once the XP does find the W98,
transferring files, data, and print jobs goes normally, no delays. It
is
only *finding* the W98 computer on the network that goes slow.
I have lived with this setup like this for several months now. It
works,
but
it's just annoying as all hell. Every now and then I see a post or
webpage
that seems to relate to my problem and I try the fix suggested, make
the
setting changes, edit the registry, hang garlic from the monitor, but
no
solution. I've tried a *lot* of things, all the usual suspects,
so please bear with me if you offer stuff I've done before. This also
means
that a lot of original settings, files, and the printer's driver have
been
changed, reinstalled, or deleted. I know the ultimate solution is to
clean
install XP, but I wonder if anyone knows a less painful fix. Please
let
me
know if you need any more info, I'm attempting to keep this long
story
short.

First, make sure that you have only NetBIOS Over TCP/IP, and TCP/IP,
installed
as protocols. Extra protocols like IPX/SPX and NetBEUI will cause
this
problem.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

Next, look at the browser (no, I'm not talking about Internet
Explorer)
situation. When you combine Windows 98 and XP on the network, this
is a
problem.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from
experience.
My email is AT DOT
actual address pchuck mvps org.

Additional info: I once had mapped a couple of drives on the W98
computer
in
WXP, back when the original mainboard was in the box. I didn't like the
setup because the W98 isn't always switched on and that caused problems
with
explorer trying to find the "missing" drives. So I removed the mapped
drives
in My Computer after the mainboard was replaced. Curiously, one (only
one)
of the mapped drive names keeps showing up in "My Network Places". I
delete
it, it comes back. I share drive D on the W98 so the drive shows as
W98-D
in
Windows explorer, but that is also the name that I gave the mapped
drive.
So
there may be no issue with the mapping, it may be just the shared drive
jumping to the head of the que. Is this any help?

Which computer is this persistent share showing up on? Which part of
Network
Neighborhood?

Please provide "browstat status" and "ipconfig /all" from the Windows
XP
computer, and "ipconfig /all" from the Windows 98 computer. Read this
article,
and linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

<SNIP CDiag run for Bruce>

Very interesting, that. Look at pinging Bruce and Fred.

"BRUCE ping BRUCE"

Pinging bruce [65.96.154.232] with 32 bytes of data:

Reply from 65.96.154.232: bytes=32 time<1ms TTL=128

"BRUCE ping FRED"

Pinging FRED.hsd1.ma.comcast.net [66.30.124.98] with 32 bytes of data:

Request timed out.

Now look at your CDiag setup (presumably based upon ipconfig logs).
BRUCE 192.168.0.1 FRED 192.168.0.95

Have Bruce and Fred always been connected as server - client?

How about pinging each computer from Fred (I assume Fred is the Windows
98
computer?)? What ip addresses, and what results, do you get?

SNIP

"Have Bruce and Fred always been connected as server - client?"
That would be yes, and no. Yes, only these two computers have ever been
networked together. But remember, BRUCE (WXP) had the motherboard failure
and repair install of XP, so maybe it is a "new" computer.

"(I assume Fred is the Windows 98 computer?)"
Yes.

"How about pinging each computer from Fred"
Fred's cool. Fred pings all 4 ways.
Pings Fred @fred.mshome.net 192.168.0.95
Pings 192.168.0.95
Pings Bruce @bruce.mshome.net 192.168.0.1
Pings 192.168.0.1

But BRUCE only pings 3 ways:
Pings Bruce @65.96.154.232
Pings 192.168.0.1
Does not ping Fred. It tries the address that is used for the broadband
connection on the 3Com card. (The LAN is on the Linksys card.)
Pings 192.168.0.95

BUT
If I disable the 3Com (Broadband) connection, then Bruce can ping Fred @
192.168.0.95
And if I ping 65.96.154.232 I get "Destination host unreachable"

I then re-engage the 3Com card and I can ping 65.96.154.232.

Thanks Chuck.

Follow up:
I'm guessing that my problem has something to do with name resolution (?). I
have no clue how Windows handles name resolution. How/where do you make
changes in these settings?

I'm looking at the pages on your site regarding repair of LSP/Winsock and
resetting TCP/IP. I'm thinking of cutting to the chase and reinstalling the
network cards on the XP computer.
Is it safe to assume that all the name resolution data will be "wiped clean"
when I uninstall the network cards from Device Manager?
Will it be necessay to do anything on the W98 computer?

 

[Chuck]

I have a simple 2 computer home network set up with a crossover
cable.
The
serving machine runs XP-SP2 and the client runs W98SE. The XP server
had
an
on-board Gigabit LAN controller (Asus P4C800-E) that was connected to
the
cable modem and a Linksys NIC to connect to the LAN. At one time
everything
worked perfectly, very fast, and no burps, beeps, or delays. Then my
server's mainboard died. A new (Intel) mainboard was installed and a
repair
install of XP was performed. The new board does not have built in
Gigabit
LAN, so a 3-Com NIC was added and connects to the modem. The same
Linksys
NIC connectsto the LAN. After the system was back up and running
there
were
a *lot* of bugs in the works. One was that the network connection
could
not
be re-established. After much research I was able to find and delete
phantom
devices from the system, including the phantom Gigabit LAN controller
and
gain access to the network connection. But only by changing the
setting
under TCP/IP properties from "Obtain IP address automatically" and
manually assign address 192.168.0.1 (and the 255 subnet mask). By
default
the "Use the following DNS server address" option is selected, but I
left
this blank. Now the network works, but it is very slow to find the
W98
computer in both Network Neighborhood and in Windows Explorer. The
hourglass
shows for 30 to 60 seconds before the files on W98 show up. Same with
the
shared printer connected to the W98. Sometimes it won't even show at
all
(grayed out). But, going the other way (from the W98 computer)
everything
is
just like before: no delay, very fast. Shared printers on the XP
machine
work great. ICS works great. And, once the XP does find the W98,
transferring files, data, and print jobs goes normally, no delays. It
is
only *finding* the W98 computer on the network that goes slow.
I have lived with this setup like this for several months now. It
works,
but
it's just annoying as all hell. Every now and then I see a post or
webpage
that seems to relate to my problem and I try the fix suggested, make
the
setting changes, edit the registry, hang garlic from the monitor, but
no
solution. I've tried a *lot* of things, all the usual suspects,
so please bear with me if you offer stuff I've done before. This also
means
that a lot of original settings, files, and the printer's driver have
been
changed, reinstalled, or deleted. I know the ultimate solution is to
clean
install XP, but I wonder if anyone knows a less painful fix. Please
let
me
know if you need any more info, I'm attempting to keep this long
story
short.

First, make sure that you have only NetBIOS Over TCP/IP, and TCP/IP,
installed
as protocols. Extra protocols like IPX/SPX and NetBEUI will cause
this
problem.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

Next, look at the browser (no, I'm not talking about Internet
Explorer)
situation. When you combine Windows 98 and XP on the network, this
is a
problem.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from
experience.
My email is AT DOT
actual address pchuck mvps org.

Additional info: I once had mapped a couple of drives on the W98
computer
in
WXP, back when the original mainboard was in the box. I didn't like the
setup because the W98 isn't always switched on and that caused problems
with
explorer trying to find the "missing" drives. So I removed the mapped
drives
in My Computer after the mainboard was replaced. Curiously, one (only
one)
of the mapped drive names keeps showing up in "My Network Places". I
delete
it, it comes back. I share drive D on the W98 so the drive shows as
W98-D
in
Windows explorer, but that is also the name that I gave the mapped
drive.
So
there may be no issue with the mapping, it may be just the shared drive
jumping to the head of the que. Is this any help?

Which computer is this persistent share showing up on? Which part of
Network
Neighborhood?

Please provide "browstat status" and "ipconfig /all" from the Windows
XP
computer, and "ipconfig /all" from the Windows 98 computer. Read this
article,
and linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

<SNIP CDiag run for Bruce>

Very interesting, that. Look at pinging Bruce and Fred.

"BRUCE ping BRUCE"

Pinging bruce [65.96.154.232] with 32 bytes of data:

Reply from 65.96.154.232: bytes=32 time<1ms TTL=128

"BRUCE ping FRED"

Pinging FRED.hsd1.ma.comcast.net [66.30.124.98] with 32 bytes of data:

Request timed out.

Now look at your CDiag setup (presumably based upon ipconfig logs).
BRUCE 192.168.0.1 FRED 192.168.0.95

Have Bruce and Fred always been connected as server - client?

How about pinging each computer from Fred (I assume Fred is the Windows
98
computer?)? What ip addresses, and what results, do you get?

SNIP

"Have Bruce and Fred always been connected as server - client?"
That would be yes, and no. Yes, only these two computers have ever been
networked together. But remember, BRUCE (WXP) had the motherboard failure
and repair install of XP, so maybe it is a "new" computer.

"(I assume Fred is the Windows 98 computer?)"
Yes.

"How about pinging each computer from Fred"
Fred's cool. Fred pings all 4 ways.
Pings Fred @fred.mshome.net 192.168.0.95
Pings 192.168.0.95
Pings Bruce @bruce.mshome.net 192.168.0.1
Pings 192.168.0.1

But BRUCE only pings 3 ways:
Pings Bruce @65.96.154.232
Pings 192.168.0.1
Does not ping Fred. It tries the address that is used for the broadband
connection on the 3Com card. (The LAN is on the Linksys card.)
Pings 192.168.0.95

BUT
If I disable the 3Com (Broadband) connection, then Bruce can ping Fred @
192.168.0.95
And if I ping 65.96.154.232 I get "Destination host unreachable"

I then re-engage the 3Com card and I can ping 65.96.154.232.

Thanks Chuck.

Follow up:
I'm guessing that my problem has something to do with name resolution (?). I
have no clue how Windows handles name resolution. How/where do you make
changes in these settings?

I'm looking at the pages on your site regarding repair of LSP/Winsock and
resetting TCP/IP. I'm thinking of cutting to the chase and reinstalling the
network cards on the XP computer.
Is it safe to assume that all the name resolution data will be "wiped clean"
when I uninstall the network cards from Device Manager?
Will it be necessay to do anything on the W98 computer?

Bruce is Node Type Unknown, Fred is Node Type Mixed. See my article, which
discusses node type, and name resolution.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

You could start by re installing the network hardware, but IMHO there are more
problems with LSP / Winsock, then with TCP/IP, finally with the physical
devices, when most folks get help here. That's why my diagnosis / prognosis
goes in that order. LSP / Winsock pre-Vista is used to attach a lot of third
party software, and gets corrupted a lot. If there's a problem with LSP /
Winsock, re installing hardware won't resolve it.

What I'm most curious about is the name resolution that Bruce is getting. Bruce
is getting a name resolution reply for itself from 65.96.154.232, and can ping
itself on that address. Bruce gets name resolution for Fred from 66.30.124.98,
but can't ping that. What is 66.30.124.98? When did you have 2 computers on
separate subnets like that?

I wouldn't bet that the problem is in the physical network devices (if so, why
can Fred ping Bruce), so re installing the physical devices first won't likely
have any effect.

My recommendation is that you investigate in this order:
1) Misconfigured or overlooked firewall.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html
2) LSP / Winsock / TCP/IP.
3) Physical device / drivers.

 

[BP]

I have a simple 2 computer home network set up with a crossover
cable.
The
serving machine runs XP-SP2 and the client runs W98SE. The XP
server
had
an
on-board Gigabit LAN controller (Asus P4C800-E) that was connected
to
the
cable modem and a Linksys NIC to connect to the LAN. At one time
everything
worked perfectly, very fast, and no burps, beeps, or delays. Then
my
server's mainboard died. A new (Intel) mainboard was installed and
a
repair
install of XP was performed. The new board does not have built in
Gigabit
LAN, so a 3-Com NIC was added and connects to the modem. The same
Linksys
NIC connectsto the LAN. After the system was back up and running
there
were
a *lot* of bugs in the works. One was that the network connection
could
not
be re-established. After much research I was able to find and
delete
phantom
devices from the system, including the phantom Gigabit LAN
controller
and
gain access to the network connection. But only by changing the
setting
under TCP/IP properties from "Obtain IP address automatically" and
manually assign address 192.168.0.1 (and the 255 subnet mask). By
default
the "Use the following DNS server address" option is selected, but
I
left
this blank. Now the network works, but it is very slow to find the
W98
computer in both Network Neighborhood and in Windows Explorer. The
hourglass
shows for 30 to 60 seconds before the files on W98 show up. Same
with
the
shared printer connected to the W98. Sometimes it won't even show
at
all
(grayed out). But, going the other way (from the W98 computer)
everything
is
just like before: no delay, very fast. Shared printers on the XP
machine
work great. ICS works great. And, once the XP does find the W98,
transferring files, data, and print jobs goes normally, no delays.
It
is
only *finding* the W98 computer on the network that goes slow.
I have lived with this setup like this for several months now. It
works,
but
it's just annoying as all hell. Every now and then I see a post or
webpage
that seems to relate to my problem and I try the fix suggested,
make
the
setting changes, edit the registry, hang garlic from the monitor,
but
no
solution. I've tried a *lot* of things, all the usual suspects,
so please bear with me if you offer stuff I've done before. This
also
means
that a lot of original settings, files, and the printer's driver
have
been
changed, reinstalled, or deleted. I know the ultimate solution is
to
clean
install XP, but I wonder if anyone knows a less painful fix. Please
let
me
know if you need any more info, I'm attempting to keep this long
story
short.

First, make sure that you have only NetBIOS Over TCP/IP, and
TCP/IP,
installed
as protocols. Extra protocols like IPX/SPX and NetBEUI will cause
this
problem.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

Next, look at the browser (no, I'm not talking about Internet
Explorer)
situation. When you combine Windows 98 and XP on the network, this
is a
problem.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from
experience.
My email is AT DOT
actual address pchuck mvps org.

Additional info: I once had mapped a couple of drives on the W98
computer
in
WXP, back when the original mainboard was in the box. I didn't like
the
setup because the W98 isn't always switched on and that caused
problems
with
explorer trying to find the "missing" drives. So I removed the mapped
drives
in My Computer after the mainboard was replaced. Curiously, one (only
one)
of the mapped drive names keeps showing up in "My Network Places". I
delete
it, it comes back. I share drive D on the W98 so the drive shows as
W98-D
in
Windows explorer, but that is also the name that I gave the mapped
drive.
So
there may be no issue with the mapping, it may be just the shared
drive
jumping to the head of the que. Is this any help?

Which computer is this persistent share showing up on? Which part of
Network
Neighborhood?

Please provide "browstat status" and "ipconfig /all" from the Windows
XP
computer, and "ipconfig /all" from the Windows 98 computer. Read
this
article,
and linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

<SNIP CDiag run for Bruce>

Very interesting, that. Look at pinging Bruce and Fred.

"BRUCE ping BRUCE"

Pinging bruce [65.96.154.232] with 32 bytes of data:

Reply from 65.96.154.232: bytes=32 time<1ms TTL=128

"BRUCE ping FRED"

Pinging FRED.hsd1.ma.comcast.net [66.30.124.98] with 32 bytes of data:

Request timed out.

Now look at your CDiag setup (presumably based upon ipconfig logs).
BRUCE 192.168.0.1 FRED 192.168.0.95

Have Bruce and Fred always been connected as server - client?

How about pinging each computer from Fred (I assume Fred is the Windows
98
computer?)? What ip addresses, and what results, do you get?

SNIP
"Have Bruce and Fred always been connected as server - client?"
That would be yes, and no. Yes, only these two computers have ever been
networked together. But remember, BRUCE (WXP) had the motherboard
failure
and repair install of XP, so maybe it is a "new" computer.

"(I assume Fred is the Windows 98 computer?)"
Yes.

"How about pinging each computer from Fred"
Fred's cool. Fred pings all 4 ways.
Pings Fred @fred.mshome.net 192.168.0.95
Pings 192.168.0.95
Pings Bruce @bruce.mshome.net 192.168.0.1
Pings 192.168.0.1

But BRUCE only pings 3 ways:
Pings Bruce @65.96.154.232
Pings 192.168.0.1
Does not ping Fred. It tries the address that is used for the broadband
connection on the 3Com card. (The LAN is on the Linksys card.)
Pings 192.168.0.95

BUT
If I disable the 3Com (Broadband) connection, then Bruce can ping Fred @
192.168.0.95
And if I ping 65.96.154.232 I get "Destination host unreachable"

I then re-engage the 3Com card and I can ping 65.96.154.232.

Thanks Chuck.

Follow up:
I'm guessing that my problem has something to do with name resolution (?).
I
have no clue how Windows handles name resolution. How/where do you make
changes in these settings?

I'm looking at the pages on your site regarding repair of LSP/Winsock and
resetting TCP/IP. I'm thinking of cutting to the chase and reinstalling
the
network cards on the XP computer.
Is it safe to assume that all the name resolution data will be "wiped
clean"
when I uninstall the network cards from Device Manager?
Will it be necessay to do anything on the W98 computer?

Bruce is Node Type Unknown, Fred is Node Type Mixed. See my article,
which
discusses node type, and name resolution.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

You could start by re installing the network hardware, but IMHO there are
more
problems with LSP / Winsock, then with TCP/IP, finally with the physical
devices, when most folks get help here. That's why my diagnosis /
prognosis
goes in that order. LSP / Winsock pre-Vista is used to attach a lot of
third
party software, and gets corrupted a lot. If there's a problem with LSP /
Winsock, re installing hardware won't resolve it.

What I'm most curious about is the name resolution that Bruce is getting.
Bruce
is getting a name resolution reply for itself from 65.96.154.232, and can
ping
itself on that address. Bruce gets name resolution for Fred from
66.30.124.98,
but can't ping that. What is 66.30.124.98? When did you have 2 computers
on
separate subnets like that?

I wouldn't bet that the problem is in the physical network devices (if so,
why
can Fred ping Bruce), so re installing the physical devices first won't
likely
have any effect.

My recommendation is that you investigate in this order:
1) Misconfigured or overlooked firewall.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html
2) LSP / Winsock / TCP/IP.
3) Physical device / drivers.

Sounds like a "fun" weekend project. I'll post back with results.

"What is 66.30.124.98?"
That is what I've been asking myself for months. I have no idea where the
address comes from, or why (particularly when the ip address is fixed). Do
you think this could be the result some type of trojan/spyware hijack? I run
AVG and Spybot.

"When did you have 2 computers on separate subnets like that?"
Never!

Regarding fixing LSP/Winsock: I was going to use the "fifth possibility"
netsh winsock... first, rather than installing the feeeware solutions,
unless you think the freeware is a superior fix. Is it?

Thanks

 

[Chuck]

I have a simple 2 computer home network set up with a crossover
cable.
The
serving machine runs XP-SP2 and the client runs W98SE. The XP
server
had
an
on-board Gigabit LAN controller (Asus P4C800-E) that was connected
to
the
cable modem and a Linksys NIC to connect to the LAN. At one time
everything
worked perfectly, very fast, and no burps, beeps, or delays. Then
my
server's mainboard died. A new (Intel) mainboard was installed and
a
repair
install of XP was performed. The new board does not have built in
Gigabit
LAN, so a 3-Com NIC was added and connects to the modem. The same
Linksys
NIC connectsto the LAN. After the system was back up and running
there
were
a *lot* of bugs in the works. One was that the network connection
could
not
be re-established. After much research I was able to find and
delete
phantom
devices from the system, including the phantom Gigabit LAN
controller
and
gain access to the network connection. But only by changing the
setting
under TCP/IP properties from "Obtain IP address automatically" and
manually assign address 192.168.0.1 (and the 255 subnet mask). By
default
the "Use the following DNS server address" option is selected, but
I
left
this blank. Now the network works, but it is very slow to find the
W98
computer in both Network Neighborhood and in Windows Explorer. The
hourglass
shows for 30 to 60 seconds before the files on W98 show up. Same
with
the
shared printer connected to the W98. Sometimes it won't even show
at
all
(grayed out). But, going the other way (from the W98 computer)
everything
is
just like before: no delay, very fast. Shared printers on the XP
machine
work great. ICS works great. And, once the XP does find the W98,
transferring files, data, and print jobs goes normally, no delays.
It
is
only *finding* the W98 computer on the network that goes slow.
I have lived with this setup like this for several months now. It
works,
but
it's just annoying as all hell. Every now and then I see a post or
webpage
that seems to relate to my problem and I try the fix suggested,
make
the
setting changes, edit the registry, hang garlic from the monitor,
but
no
solution. I've tried a *lot* of things, all the usual suspects,
so please bear with me if you offer stuff I've done before. This
also
means
that a lot of original settings, files, and the printer's driver
have
been
changed, reinstalled, or deleted. I know the ultimate solution is
to
clean
install XP, but I wonder if anyone knows a less painful fix. Please
let
me
know if you need any more info, I'm attempting to keep this long
story
short.

First, make sure that you have only NetBIOS Over TCP/IP, and
TCP/IP,
installed
as protocols. Extra protocols like IPX/SPX and NetBEUI will cause
this
problem.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

Next, look at the browser (no, I'm not talking about Internet
Explorer)
situation. When you combine Windows 98 and XP on the network, this
is a
problem.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from
experience.
My email is AT DOT
actual address pchuck mvps org.

Additional info: I once had mapped a couple of drives on the W98
computer
in
WXP, back when the original mainboard was in the box. I didn't like
the
setup because the W98 isn't always switched on and that caused
problems
with
explorer trying to find the "missing" drives. So I removed the mapped
drives
in My Computer after the mainboard was replaced. Curiously, one (only
one)
of the mapped drive names keeps showing up in "My Network Places". I
delete
it, it comes back. I share drive D on the W98 so the drive shows as
W98-D
in
Windows explorer, but that is also the name that I gave the mapped
drive.
So
there may be no issue with the mapping, it may be just the shared
drive
jumping to the head of the que. Is this any help?

Which computer is this persistent share showing up on? Which part of
Network
Neighborhood?

Please provide "browstat status" and "ipconfig /all" from the Windows
XP
computer, and "ipconfig /all" from the Windows 98 computer. Read
this
article,
and linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

<SNIP CDiag run for Bruce>

Very interesting, that. Look at pinging Bruce and Fred.

"BRUCE ping BRUCE"

Pinging bruce [65.96.154.232] with 32 bytes of data:

Reply from 65.96.154.232: bytes=32 time<1ms TTL=128

"BRUCE ping FRED"

Pinging FRED.hsd1.ma.comcast.net [66.30.124.98] with 32 bytes of data:

Request timed out.

Now look at your CDiag setup (presumably based upon ipconfig logs).
BRUCE 192.168.0.1 FRED 192.168.0.95

Have Bruce and Fred always been connected as server - client?

How about pinging each computer from Fred (I assume Fred is the Windows
98
computer?)? What ip addresses, and what results, do you get?

SNIP
"Have Bruce and Fred always been connected as server - client?"
That would be yes, and no. Yes, only these two computers have ever been
networked together. But remember, BRUCE (WXP) had the motherboard
failure
and repair install of XP, so maybe it is a "new" computer.

"(I assume Fred is the Windows 98 computer?)"
Yes.

"How about pinging each computer from Fred"
Fred's cool. Fred pings all 4 ways.
Pings Fred @fred.mshome.net 192.168.0.95
Pings 192.168.0.95
Pings Bruce @bruce.mshome.net 192.168.0.1
Pings 192.168.0.1

But BRUCE only pings 3 ways:
Pings Bruce @65.96.154.232
Pings 192.168.0.1
Does not ping Fred. It tries the address that is used for the broadband
connection on the 3Com card. (The LAN is on the Linksys card.)
Pings 192.168.0.95

BUT
If I disable the 3Com (Broadband) connection, then Bruce can ping Fred @
192.168.0.95
And if I ping 65.96.154.232 I get "Destination host unreachable"

I then re-engage the 3Com card and I can ping 65.96.154.232.

Thanks Chuck.

Follow up:
I'm guessing that my problem has something to do with name resolution (?).
I
have no clue how Windows handles name resolution. How/where do you make
changes in these settings?

I'm looking at the pages on your site regarding repair of LSP/Winsock and
resetting TCP/IP. I'm thinking of cutting to the chase and reinstalling
the
network cards on the XP computer.
Is it safe to assume that all the name resolution data will be "wiped
clean"
when I uninstall the network cards from Device Manager?
Will it be necessay to do anything on the W98 computer?

Bruce is Node Type Unknown, Fred is Node Type Mixed. See my article,
which
discusses node type, and name resolution.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

You could start by re installing the network hardware, but IMHO there are
more
problems with LSP / Winsock, then with TCP/IP, finally with the physical
devices, when most folks get help here. That's why my diagnosis /
prognosis
goes in that order. LSP / Winsock pre-Vista is used to attach a lot of
third
party software, and gets corrupted a lot. If there's a problem with LSP /
Winsock, re installing hardware won't resolve it.

What I'm most curious about is the name resolution that Bruce is getting.
Bruce
is getting a name resolution reply for itself from 65.96.154.232, and can
ping
itself on that address. Bruce gets name resolution for Fred from
66.30.124.98,
but can't ping that. What is 66.30.124.98? When did you have 2 computers
on
separate subnets like that?

I wouldn't bet that the problem is in the physical network devices (if so,
why
can Fred ping Bruce), so re installing the physical devices first won't
likely
have any effect.

My recommendation is that you investigate in this order:
1) Misconfigured or overlooked firewall.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html
2) LSP / Winsock / TCP/IP.
3) Physical device / drivers.

Sounds like a "fun" weekend project. I'll post back with results.

"What is 66.30.124.98?"
That is what I've been asking myself for months. I have no idea where the
address comes from, or why (particularly when the ip address is fixed). Do
you think this could be the result some type of trojan/spyware hijack? I run
AVG and Spybot.

"When did you have 2 computers on separate subnets like that?"
Never!

Regarding fixing LSP/Winsock: I was going to use the "fifth possibility"
netsh winsock... first, rather than installing the feeeware solutions,
unless you think the freeware is a superior fix. Is it?

LSP / Winsock corruptions are so unpredictable, and not one of the 6 solutions
presented in that article have proven to be 100% effective. You may have to try
one at a time. Don't give up with the first, if it doesn't work.

Your address resolution anomaly is weird, but it doesn't scream spyware
infection. Just the same, if you don't get results after you try all 6 LSP
fixes (and please do that first), let's see if HijackThis gives us any clues.
<http://nitecruzr.blogspot.com/2005/05/interpreting-hijackthis-logs-with.html>
http://nitecruzr.blogspot.com/2005/05/interpreting-hijackthis-logs-with.html

 

[BP]

On Tue, 29 Nov 2005 07:18:30 -0500, "BP"
<*email_address_deleted*>
wrote:

I have a simple 2 computer home network set up with a crossover
cable.
The
serving machine runs XP-SP2 and the client runs W98SE. The XP
server
had
an
on-board Gigabit LAN controller (Asus P4C800-E) that was
connected
to
the
cable modem and a Linksys NIC to connect to the LAN. At one time
everything
worked perfectly, very fast, and no burps, beeps, or delays. Then
my
server's mainboard died. A new (Intel) mainboard was installed
and
a
repair
install of XP was performed. The new board does not have built in
Gigabit
LAN, so a 3-Com NIC was added and connects to the modem. The same
Linksys
NIC connectsto the LAN. After the system was back up and running
there
were
a *lot* of bugs in the works. One was that the network connection
could
not
be re-established. After much research I was able to find and
delete
phantom
devices from the system, including the phantom Gigabit LAN
controller
and
gain access to the network connection. But only by changing the
setting
under TCP/IP properties from "Obtain IP address automatically"
and
manually assign address 192.168.0.1 (and the 255 subnet mask). By
default
the "Use the following DNS server address" option is selected,
but
I
left
this blank. Now the network works, but it is very slow to find
the
W98
computer in both Network Neighborhood and in Windows Explorer.
The
hourglass
shows for 30 to 60 seconds before the files on W98 show up. Same
with
the
shared printer connected to the W98. Sometimes it won't even show
at
all
(grayed out). But, going the other way (from the W98 computer)
everything
is
just like before: no delay, very fast. Shared printers on the XP
machine
work great. ICS works great. And, once the XP does find the W98,
transferring files, data, and print jobs goes normally, no
delays.
It
is
only *finding* the W98 computer on the network that goes slow.
I have lived with this setup like this for several months now. It
works,
but
it's just annoying as all hell. Every now and then I see a post
or
webpage
that seems to relate to my problem and I try the fix suggested,
make
the
setting changes, edit the registry, hang garlic from the monitor,
but
no
solution. I've tried a *lot* of things, all the usual suspects,
so please bear with me if you offer stuff I've done before. This
also
means
that a lot of original settings, files, and the printer's driver
have
been
changed, reinstalled, or deleted. I know the ultimate solution is
to
clean
install XP, but I wonder if anyone knows a less painful fix.
Please
let
me
know if you need any more info, I'm attempting to keep this long
story
short.

First, make sure that you have only NetBIOS Over TCP/IP, and
TCP/IP,
installed
as protocols. Extra protocols like IPX/SPX and NetBEUI will
cause
this
problem.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

Next, look at the browser (no, I'm not talking about Internet
Explorer)
situation. When you combine Windows 98 and XP on the network,
this
is a
problem.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from
experience.
My email is AT DOT
actual address pchuck mvps org.

Additional info: I once had mapped a couple of drives on the W98
computer
in
WXP, back when the original mainboard was in the box. I didn't like
the
setup because the W98 isn't always switched on and that caused
problems
with
explorer trying to find the "missing" drives. So I removed the
mapped
drives
in My Computer after the mainboard was replaced. Curiously, one
(only
one)
of the mapped drive names keeps showing up in "My Network Places".
I
delete
it, it comes back. I share drive D on the W98 so the drive shows as
W98-D
in
Windows explorer, but that is also the name that I gave the mapped
drive.
So
there may be no issue with the mapping, it may be just the shared
drive
jumping to the head of the que. Is this any help?

Which computer is this persistent share showing up on? Which part
of
Network
Neighborhood?

Please provide "browstat status" and "ipconfig /all" from the
Windows
XP
computer, and "ipconfig /all" from the Windows 98 computer. Read
this
article,
and linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

<SNIP CDiag run for Bruce>

Very interesting, that. Look at pinging Bruce and Fred.

"BRUCE ping BRUCE"

Pinging bruce [65.96.154.232] with 32 bytes of data:

Reply from 65.96.154.232: bytes=32 time<1ms TTL=128

"BRUCE ping FRED"

Pinging FRED.hsd1.ma.comcast.net [66.30.124.98] with 32 bytes of
data:

Request timed out.

Now look at your CDiag setup (presumably based upon ipconfig logs).
BRUCE 192.168.0.1 FRED 192.168.0.95

Have Bruce and Fred always been connected as server - client?

How about pinging each computer from Fred (I assume Fred is the
Windows
98
computer?)? What ip addresses, and what results, do you get?

SNIP
"Have Bruce and Fred always been connected as server - client?"
That would be yes, and no. Yes, only these two computers have ever
been
networked together. But remember, BRUCE (WXP) had the motherboard
failure
and repair install of XP, so maybe it is a "new" computer.

"(I assume Fred is the Windows 98 computer?)"
Yes.

"How about pinging each computer from Fred"
Fred's cool. Fred pings all 4 ways.
Pings Fred @fred.mshome.net 192.168.0.95
Pings 192.168.0.95
Pings Bruce @bruce.mshome.net 192.168.0.1
Pings 192.168.0.1

But BRUCE only pings 3 ways:
Pings Bruce @65.96.154.232
Pings 192.168.0.1
Does not ping Fred. It tries the address that is used for the
broadband
connection on the 3Com card. (The LAN is on the Linksys card.)
Pings 192.168.0.95

BUT
If I disable the 3Com (Broadband) connection, then Bruce can ping Fred
@
192.168.0.95
And if I ping 65.96.154.232 I get "Destination host unreachable"

I then re-engage the 3Com card and I can ping 65.96.154.232.

Thanks Chuck.

Follow up:
I'm guessing that my problem has something to do with name resolution
(?).
I
have no clue how Windows handles name resolution. How/where do you make
changes in these settings?

I'm looking at the pages on your site regarding repair of LSP/Winsock
and
resetting TCP/IP. I'm thinking of cutting to the chase and reinstalling
the
network cards on the XP computer.
Is it safe to assume that all the name resolution data will be "wiped
clean"
when I uninstall the network cards from Device Manager?
Will it be necessay to do anything on the W98 computer?

Bruce is Node Type Unknown, Fred is Node Type Mixed. See my article,
which
discusses node type, and name resolution.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

You could start by re installing the network hardware, but IMHO there
are
more
problems with LSP / Winsock, then with TCP/IP, finally with the physical
devices, when most folks get help here. That's why my diagnosis /
prognosis
goes in that order. LSP / Winsock pre-Vista is used to attach a lot of
third
party software, and gets corrupted a lot. If there's a problem with LSP
/
Winsock, re installing hardware won't resolve it.

What I'm most curious about is the name resolution that Bruce is
getting.
Bruce
is getting a name resolution reply for itself from 65.96.154.232, and
can
ping
itself on that address. Bruce gets name resolution for Fred from
66.30.124.98,
but can't ping that. What is 66.30.124.98? When did you have 2
computers
on
separate subnets like that?

I wouldn't bet that the problem is in the physical network devices (if
so,
why
can Fred ping Bruce), so re installing the physical devices first won't
likely
have any effect.

My recommendation is that you investigate in this order:
1) Misconfigured or overlooked firewall.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html
2) LSP / Winsock / TCP/IP.
3) Physical device / drivers.

Sounds like a "fun" weekend project. I'll post back with results.

"What is 66.30.124.98?"
That is what I've been asking myself for months. I have no idea where the
address comes from, or why (particularly when the ip address is fixed). Do
you think this could be the result some type of trojan/spyware hijack? I
run
AVG and Spybot.

"When did you have 2 computers on separate subnets like that?"
Never!

Regarding fixing LSP/Winsock: I was going to use the "fifth possibility"
netsh winsock... first, rather than installing the feeeware solutions,
unless you think the freeware is a superior fix. Is it?

LSP / Winsock corruptions are so unpredictable, and not one of the 6
solutions
presented in that article have proven to be 100% effective. You may have
to try
one at a time. Don't give up with the first, if it doesn't work.

Your address resolution anomaly is weird, but it doesn't scream spyware
infection. Just the same, if you don't get results after you try all 6
LSP
fixes (and please do that first), let's see if HijackThis gives us any
clues.
<http://nitecruzr.blogspot.com/2005/05/interpreting-hijackthis-logs-with.html>
http://nitecruzr.blogspot.com/2005/05/interpreting-hijackthis-logs-with.html

OK. LSP Fix found nothing to change or remove. WinSock2 Fix is no longer
supported by the host site and is for Build 4 OS's only.
None of the six fixes worked They changed my TCP/IP settings to defaults
(Automatic IP) and I go "No Connectivity" on the Linksys LAN NIC (only-
Broadband on the 3Com is always fine.). Hitting "Repair" does nothing:.
Resetting TCP/IP back to my configuration (fixed IP address) solves the
connectiovity problem.

Weird: After running the TCP fixes and getting connectivity back, Bruce
can't see Bruce or Fred in Network Places. I go down to FRED and check its
connection and (good ol' Fred) nothing is wrong: finds Bruce, open folders
instantaneously. I go back up to BRUCE and voila, BRUCE can now see itself
and FRED in network places. Once that has been done the problem condition
goes back to it's original (slow) state.

And now a phantom Fred printer (drivers deleted and reinstalled with a new
name on Bruce) has shown up. I deleted it again in "Printers" but it remains
in Network Places.

Next opportunity I will reinstall the hardware and with them the protocols.
My plan is to remove the devices in windows, physically remove the hardware
from the computer, reboot, and search the registry for stragglers. I've got
a sneaking suspicion that the Linksys NIC exists twice in some key and has
laid claim to the IP address. We'll see.....