Tried everything, what's next?

[Charles Pyeatte]

I hope someone can offer a solution. I’ve spent days working through
the Problem Solver and not solving my problem.

I have two computers in a peer-to-peer network connected by a crossover
cable. They are named FRED and WILMA. The network (STUDYNET) worked fine
when I first set it up. I’m not sure what undid it, but I suspect it
happened when I realized that Wilma was causing Fred to dial the
Internet every time Wilma dialed. ICS had accidentally been enabled. I
went into the settings page and disabled it.

IPCONFIG reports as follows:

Host name WILMA
Primary Dns Suffix
Node type Mixed
Ip Routing Enabled No
WINS proxy Enabled No

Ethernet adapter local area connection:

Physical address 00-0B-6A-6D-04
DHCP Enabled No
IP Address 192.168.0.98
Subnet mask 255.255.255.0
Default Gateway 192.168.0.98

Host name FRED
Primary Dns suffix
Node type Mixed
IP routing enabled No
WINS proxy enabled No

Ethernet adapter local area connection:

Physical address 00-0B-6A-EE-4A-E6
DHCP enabled No
IP address 192.168.0.99
Subnet mask 255.255.255.0
Default gateway 192.168.0.99

When I look at Workgroup Computers, Fred can see icons for Fred and
Wilma, but when I click on the Wilma icon, I get the message:
\\wilma is not accessible. You might not have permission to use this
network resource. Contact the administrator of this serve to find out if
you have access permission.
The network path was not found.

Wilma can only see Wilma in workgroup computers.
When I try ping tests from wither computer, all work until I try to ping
the other computer, then it fails: Request timed out.

I have run the setup wizard after deleting all protocols and the network
adapter. The assigned IP address was as follows: Wilma: 169.254.183.111
and Fred: 169.254.107.156, both with the subnet mask of 255.255.0.0. In
this configuration, there was “Limited or no connectivity.” When I
entered the manual IP addresses, they both show that they are connected
but still can’t communicate to each other. These same IP addresses
occur if I set both computers to automatic.

I have tried setting Net BIOS over TCP/IP with no change in results,
whether I click on that specifically or on the more general tab. The
TCP/IP Helper Service is running. The Browser is running.

In Event Viewer, on both computers, there are repeated errors showing
naming “USERENV” as the affected file.

I have turned the firewall off and on; made sure that file sharing was
checked, all with no change in the connectivity.

I tried to do a repair installation, but it did not work properly, my
computer got stuck in an endless loop trying to boot, and I had to
reinstall my hard drive from a backup.

This is how I’ve spent half my vacation!

I have connected each end of the crossover cable to my laptop and can
see either Fred or Wilma on the other end. (I couldn’t go any farther
because I needed to set up a password and account for my laptop.)

At times, I have run the Winsock repair tool and tried “Repair” in the
network box or typed the nestsh in ip reset command, although I haven’t
done either since re-installing my hard drive.

Can any of you offer me a solution, please?

 

[Chuck]

I hope someone can offer a solution. I’ve spent days working through
the Problem Solver and not solving my problem.

I have two computers in a peer-to-peer network connected by a crossover
cable. They are named FRED and WILMA. The network (STUDYNET) worked fine
when I first set it up. I’m not sure what undid it, but I suspect it
happened when I realized that Wilma was causing Fred to dial the
Internet every time Wilma dialed. ICS had accidentally been enabled. I
went into the settings page and disabled it.

IPCONFIG reports as follows:

Host name WILMA
Primary Dns Suffix
Node type Mixed
Ip Routing Enabled No
WINS proxy Enabled No

Ethernet adapter local area connection:

Physical address 00-0B-6A-6D-04
DHCP Enabled No
IP Address 192.168.0.98
Subnet mask 255.255.255.0
Default Gateway 192.168.0.98

Host name FRED
Primary Dns suffix
Node type Mixed
IP routing enabled No
WINS proxy enabled No

Ethernet adapter local area connection:

Physical address 00-0B-6A-EE-4A-E6
DHCP enabled No
IP address 192.168.0.99
Subnet mask 255.255.255.0
Default gateway 192.168.0.99

When I look at Workgroup Computers, Fred can see icons for Fred and
Wilma, but when I click on the Wilma icon, I get the message:
\\wilma is not accessible. You might not have permission to use this
network resource. Contact the administrator of this serve to find out if
you have access permission.
The network path was not found.

Wilma can only see Wilma in workgroup computers.
When I try ping tests from wither computer, all work until I try to ping
the other computer, then it fails: Request timed out.

I have run the setup wizard after deleting all protocols and the network
adapter. The assigned IP address was as follows: Wilma: 169.254.183.111
and Fred: 169.254.107.156, both with the subnet mask of 255.255.0.0. In
this configuration, there was “Limited or no connectivity.” When I
entered the manual IP addresses, they both show that they are connected
but still can’t communicate to each other. These same IP addresses
occur if I set both computers to automatic.

I have tried setting Net BIOS over TCP/IP with no change in results,
whether I click on that specifically or on the more general tab. The
TCP/IP Helper Service is running. The Browser is running.

In Event Viewer, on both computers, there are repeated errors showing
naming “USERENV” as the affected file.

I have turned the firewall off and on; made sure that file sharing was
checked, all with no change in the connectivity.

I tried to do a repair installation, but it did not work properly, my
computer got stuck in an endless loop trying to boot, and I had to
reinstall my hard drive from a backup.

This is how I’ve spent half my vacation!

I have connected each end of the crossover cable to my laptop and can
see either Fred or Wilma on the other end. (I couldn’t go any farther
because I needed to set up a password and account for my laptop.)

At times, I have run the Winsock repair tool and tried “Repair” in the
network box or typed the nestsh in ip reset command, although I haven’t
done either since re-installing my hard drive.

Can any of you offer me a solution, please?

Charles,

You've spent a frustrating half vacation, I agree. My sympathies - it doesn't
get any easier as you get more experienced - the problems just get more
complicated. ;-)

Being as I don't see a lot of symptoms identified, I can only suggest that you
analyse the problem on a layer by layer basis - and from both computers. Please
read both of these articles, and decide which one best fits your current
situation.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>

Generally, it would be best if you left ICS enabled, and turned off "Allow the
other computer to control the Internet connection". How did you disable ICS?
Stopping the WF (ICF?) / ICS service would be the wrong way, and could cause
your problem.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>

If the problem is, by any chance, an LSP / Winsock problem, there is no such
thing as "the Winsock repair tool". There are 5 possibilities there - and
absolutely none of the 5 is self sufficient in itself.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>

Please provide complete and unedited "browstat status" and "ipconfig /all" from
each computer, as a start to diagnosing the problem. Read this article, and
linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

 

[Guest]

Thank you so much for your suggestions. I have assumed that the problem was
software related, but maybe not. My NICs are on my motherboards. However, the
crossover cable illuminates at its plug ends. When I connected my laptop, on
the plug in the laptop lit up. I looked at both desktop computers, and the
plugs don't light up. Would this indicate a failure? The cable is old and
has been moved around a lot. I read in this newsgroup a recommendation that
using a switch and Cat 5 cables is better than a crossover. Would you
suggest that?

In the meantime, I'll read up as you recommended. And thanks, Chuck. It
offers much relief to know there's someone I can ask about this.

 

[Chuck]

Charles,

You've spent a frustrating half vacation, I agree. My sympathies - it doesn't
get any easier as you get more experienced - the problems just get more
complicated. ;-)

Being as I don't see a lot of symptoms identified, I can only suggest that you
analyse the problem on a layer by layer basis - and from both computers. Please
read both of these articles, and decide which one best fits your current
situation.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>

Generally, it would be best if you left ICS enabled, and turned off "Allow the
other computer to control the Internet connection". How did you disable ICS?
Stopping the WF (ICF?) / ICS service would be the wrong way, and could cause
your problem.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>

If the problem is, by any chance, an LSP / Winsock problem, there is no such
thing as "the Winsock repair tool". There are 5 possibilities there - and
absolutely none of the 5 is self sufficient in itself.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>

Please provide complete and unedited "browstat status" and "ipconfig /all" from
each computer, as a start to diagnosing the problem. Read this article, and
linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

[/QUOTE]

Thank you so much for your suggestions. I have assumed that the problem was
software related, but maybe not. My NICs are on my motherboards. However, the
crossover cable illuminates at its plug ends. When I connected my laptop, on
the plug in the laptop lit up. I looked at both desktop computers, and the
plugs don't light up. Would this indicate a failure? The cable is old and
has been moved around a lot. I read in this newsgroup a recommendation that
using a switch and Cat 5 cables is better than a crossover. Would you
suggest that?

In the meantime, I'll read up as you recommended. And thanks, Chuck. It
offers much relief to know there's someone I can ask about this.

Charlie,

With just 2 computers, using a crossover cable will give identical performance,
and is simpler. If the network cards on both computers have diagnostic lights,
you'll get the same diagnostic ability too. For future expansion though, using
a switch isn't a bad idea.

If it's an old cable, buying a new one is a good idea, and it never hurts to
have a spare. Are you using the same cable with the laptop? What do you
connect the laptop to? If the laptop connects successfully to anything, then
there's a good baseline test. Substitute one computer, at a time, for the
laptop.

And welcome to Usenet. Lots of experts here.
<http://nitecruzr.blogspot.com/2005/05/getting-help-on-usenet-and-believing.html>
http://nitecruzr.blogspot.com/2005/05/getting-help-on-usenet-and-believing.html

 

[Guest]

My crude test was to disconnect the cable from one computer and plug it into
the laptop with the other end still attached to one computer. In each
instance, I was able to see an icon for the desktop at the cable's end.
However, since the laptop runs in WIN98SE, I couldn't actually access the
desktop without a hassle of setting up user accounts and passwords. My only
observation was the the cable lit up at the laptop end but not at the
desktop end.

Since others can read this message, I wanted to mention that your
suggestions about systematically examining the problem are VERY important. I
knew I was flailing away madly when I reached out for help.

Some additional data, if you care to review it:
1. Each (desktop) computer (FRED and WILMA) can ping itself by name or IP
address. Neither can ping the other computer.
2. Browstat reports that FRED is the MBR and WILMA waits to hear from him.
3. Sometimes I can see icons for both comps in the workgroup window on FRED
and sometimes the workgroup is inacessible. In WILMA, I can only see that
comp's icon in the workgroup. FRED's shares show, WILMA's don't.
4. The main symptom is the fact that the comps no longer connect to each
other for either printers or files, as they used to do. I will look deeper
into whether it is a software issue caused by my shutting down ICS. I am
running XP Home and don't think I used the Windows Firewall to shut off ICS,
but I don't recall exactly how I did it. Is is OK just to start up ICS again?

Again, thanks for your time. If I'm bugging you too often, just wait awhile
before replying and I'll understand.

 

[Chuck]

My crude test was to disconnect the cable from one computer and plug it into
the laptop with the other end still attached to one computer. In each
instance, I was able to see an icon for the desktop at the cable's end.
However, since the laptop runs in WIN98SE, I couldn't actually access the
desktop without a hassle of setting up user accounts and passwords. My only
observation was the the cable lit up at the laptop end but not at the
desktop end.

Since others can read this message, I wanted to mention that your
suggestions about systematically examining the problem are VERY important. I
knew I was flailing away madly when I reached out for help.

Some additional data, if you care to review it:
1. Each (desktop) computer (FRED and WILMA) can ping itself by name or IP
address. Neither can ping the other computer.
2. Browstat reports that FRED is the MBR and WILMA waits to hear from him.
3. Sometimes I can see icons for both comps in the workgroup window on FRED
and sometimes the workgroup is inacessible. In WILMA, I can only see that
comp's icon in the workgroup. FRED's shares show, WILMA's don't.
4. The main symptom is the fact that the comps no longer connect to each
other for either printers or files, as they used to do. I will look deeper
into whether it is a software issue caused by my shutting down ICS. I am
running XP Home and don't think I used the Windows Firewall to shut off ICS,
but I don't recall exactly how I did it. Is is OK just to start up ICS again?

Again, thanks for your time. If I'm bugging you too often, just wait awhile
before replying and I'll understand.

Charlie,

You need ICS, to provide connectivity for Wilma. You can shutdown WF (SP2), if
desired, and you shut it down the same for XP Home as for XP Pro, thru Security
Center. But please disconnect Fred from the Internet before you do that! Don't
ever connect an unprotected computer to the Internet, even for a few seconds!
From the BBC Video Jacques' Hack Attack (and my article
<http://nitecruzr.blogspot.com/2005/05/security-by-obscurity.html>):
The first worm hit that unprotected computer almost immediately after it was
connected to the internet.
In typical British melodrama:
How long would it be before we were hit by something nasty on the net? Hours,
minutes? As it turned out - eight seconds!

 

[Guest]

Chuck,
I took two of your suggestions so far: got a new crossover cable and reset
the network to ICS. The current symptoms are: neither FRED nor WILMA can see
each other or connect to each other, although each seems able to ping itself
OK. I don’t suspect any problem with the NICs (built into our identical
combo boards), but I have the latest driver ready. The system runs Windows
XP Home SP2. Both have an up-to-date copy of Norton System Works 2003
includingn the antivirus, although I disabled worm browser on both.

As I hadn’t offered the tests you usually like to see, I’ll do that now.

I tried to run CDiag on both computers. In both attempts, the program ran
amok and generated almost 200 DOS screens and about 30 .txt screens. I got a
system error 6118. Word wrap was off. Also, in looking at system events,
both comps show repeated errors concerning DHCP and some for DCOM.

Windows IP Configuration for FRED

Host Name . . . . . . . . . . . . : FRED
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0B-6A-EE-4A-E6
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Browstat status FRED

Status for domain STUDYNET on transport
\Device\NetBT_Tcpip_{E4CB6CDF-4BBC-4FF2-8253-4B3C78CE4109}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

(I tried to start the browser on FRED but it shut itself off immediately.


CDiagnosis V1.33
Start diagnosis for FRED

Enumerate Shares
Share name Resource Remark
-------------------------------------------------------------------------------
IPC$ Remote IPC

The command completed successfully.
Adhoc Browser View
Share name Resource Remark
-------------------------------------------------------------------------------
IPC$ Remote IPC

The command completed successfully.
Ping Targets www.yahoo.com 66.94.230.32
"FRED ping www.yahoo.com"
End diagnosis for FRED
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 Target 66.94.230.32

Pinging www.yahoo.akadns.net [66.94.230.49] with 32 bytes of data:
Reply from 66.94.230.49: bytes=32 time=192ms TTL=52
Reply from 66.94.230.49: bytes=32 time=174ms TTL=52 Reply from
66.94.230.49: bytes=32 time=214ms TTL=52
Reply from 66.94.230.49: bytes=32 time=181ms TTL=52
Ping statistics for 66.94.230.49:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 174ms, Maximum = 214ms, Average = 190ms
Target 66.94.230.32

Enumerate Shares
"FRED ping 66.94.230.32"
Target 127.0.0.1
Enumerate Shares
"FRED ping www.yahoo.com"
Adhoc Browser View
Share name Resource
Remark

-------------------------------------------------------------------------------
IPC$ Remote IPC

The command completed successfully.
"FRED net view 127.0.0.1"
"FRED net view 127.0.0.1"
"FRED ping www.yahoo.com"
Full Targets 127.0.0.1
Target 127.0.0.1
"FRED 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
"FRED net view 127.0.0.1"
There are no entries in the list.
Ping Targets www.yahoo.com 66.94.230.32

Target www.yahoo.com

"FRED ping www.yahoo.com"
Pinging www.yahoo.akadns.net [66.94.230.33] with 32 bytes of data:
Reply from 66.94.230.33: bytes=32 time=207ms TTL=52
Reply from 66.94.230.33: bytes=32 time=177ms TTL=52
Reply from 66.94.230.33: bytes=32 time=183ms TTL=52
Reply from 66.94.230.33: bytes=32 time=178ms TTL=52
Ping statistics for 66.94.230.33:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 177ms, Maximum = 207ms, Average = 186ms

Target 66.94.230.32
"FRED ping 66.94.230.32"
Pinging 66.94.230.32 with 32 bytes of data:
Reply from 66.94.230.32: bytes=32 time=203ms TTL=52
Reply from 66.94.230.32: bytes=32 time=174ms TTL=52
Reply from 66.94.230.32: bytes=32 time=181ms TTL=52
Reply from 66.94.230.32: bytes=32 time=187ms TTL=52
Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 174ms, Maximum = 203ms, Average = 186ms


Windows IP Configuration WILMA

Host Name . . . . . . . . . . . . : WILMA
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection :
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-0B-6A-EF-6D-04
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.183.111
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :


I didn’t get a copy of WILMA’s browstat, but it did show that browser was
not active. I can see some possible problems here, but I’ve learned my
lesson about not jumping in.
As before, I do appreciate your time and attention.

 

[Guest]

Chuck,
I took two of your suggestions so far: got a new crossover cable and reset
the network to ICS. The current symptoms are: neither FRED nor WILMA can see
each other or connect to each other, although each seems able to ping itself
OK. I don’t suspect any problem with the NICs (built into our identical
combo boards), but I have the latest driver ready. The system runs Windows
XP Home SP2. Both have an up-to-date copy of Norton System Works 2003
includingn the antivirus, although I disabled worm browser on both.

As I hadn’t offered the tests you usually like to see, I’ll do that now.

I tried to run CDiag on both computers. In both attempts, the program ran
amok and generated almost 200 DOS screens and about 30 .txt screens. I got a
system error 6118. Word wrap was off. Also, in looking at system events,
both comps show repeated errors concerning DHCP and some for DCOM.

Windows IP Configuration for FRED

Host Name . . . . . . . . . . . . : FRED
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0B-6A-EE-4A-E6
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Browstat status FRED

Status for domain STUDYNET on transport
\Device\NetBT_Tcpip_{E4CB6CDF-4BBC-4FF2-8253-4B3C78CE4109}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

(I tried to start the browser on FRED but it shut itself off immediately.


CDiagnosis V1.33
Start diagnosis for FRED

Enumerate Shares
Share name Resource Remark
-------------------------------------------------------------------------------
IPC$ Remote IPC

The command completed successfully.
Adhoc Browser View
Share name Resource Remark
-------------------------------------------------------------------------------
IPC$ Remote IPC

The command completed successfully.
Ping Targets www.yahoo.com 66.94.230.32
"FRED ping www.yahoo.com"
End diagnosis for FRED
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 Target 66.94.230.32

Pinging www.yahoo.akadns.net [66.94.230.49] with 32 bytes of data:
Reply from 66.94.230.49: bytes=32 time=192ms TTL=52
Reply from 66.94.230.49: bytes=32 time=174ms TTL=52 Reply from
66.94.230.49: bytes=32 time=214ms TTL=52
Reply from 66.94.230.49: bytes=32 time=181ms TTL=52
Ping statistics for 66.94.230.49:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 174ms, Maximum = 214ms, Average = 190ms
Target 66.94.230.32

Enumerate Shares
"FRED ping 66.94.230.32"
Target 127.0.0.1
Enumerate Shares
"FRED ping www.yahoo.com"
Adhoc Browser View
Share name Resource
Remark

-------------------------------------------------------------------------------
IPC$ Remote IPC

The command completed successfully.
"FRED net view 127.0.0.1"
"FRED net view 127.0.0.1"
"FRED ping www.yahoo.com"
Full Targets 127.0.0.1
Target 127.0.0.1
"FRED 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
"FRED net view 127.0.0.1"
There are no entries in the list.
Ping Targets www.yahoo.com 66.94.230.32

Target www.yahoo.com

"FRED ping www.yahoo.com"
Pinging www.yahoo.akadns.net [66.94.230.33] with 32 bytes of data:
Reply from 66.94.230.33: bytes=32 time=207ms TTL=52
Reply from 66.94.230.33: bytes=32 time=177ms TTL=52
Reply from 66.94.230.33: bytes=32 time=183ms TTL=52
Reply from 66.94.230.33: bytes=32 time=178ms TTL=52
Ping statistics for 66.94.230.33:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 177ms, Maximum = 207ms, Average = 186ms

Target 66.94.230.32
"FRED ping 66.94.230.32"
Pinging 66.94.230.32 with 32 bytes of data:
Reply from 66.94.230.32: bytes=32 time=203ms TTL=52
Reply from 66.94.230.32: bytes=32 time=174ms TTL=52
Reply from 66.94.230.32: bytes=32 time=181ms TTL=52
Reply from 66.94.230.32: bytes=32 time=187ms TTL=52
Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 174ms, Maximum = 203ms, Average = 186ms


Windows IP Configuration WILMA

Host Name . . . . . . . . . . . . : WILMA
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection :
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-0B-6A-EF-6D-04
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.183.111
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :


I didn’t get a copy of WILMA’s browstat, but it did show that browser was
not active. I can see some possible problems here, but I’ve learned my
lesson about not jumping in.
As before, I do appreciate your time and attention.

Charlie,

You need ICS, to provide connectivity for Wilma. You can shutdown WF (SP2), if
desired, and you shut it down the same for XP Home as for XP Pro, thru Security
Center. But please disconnect Fred from the Internet before you do that! Don't
ever connect an unprotected computer to the Internet, even for a few seconds!
From the BBC Video Jacques' Hack Attack (and my article
<http://nitecruzr.blogspot.com/2005/05/security-by-obscurity.html>):
The first worm hit that unprotected computer almost immediately after it was
connected to the internet.
In typical British melodrama:
How long would it be before we were hit by something nasty on the net? Hours,
minutes? As it turned out - eight seconds!



Let me try this again, this time bottom posting. I was able to get a better output from the diagnostics thie second time:

Windows IP Configuration



Host Name . . . . . . . . . . . . : FRED

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Mixed

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter

Physical Address. . . . . . . . . : 00-0B-6A-EE-4A-E6

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 169.254.183.100

Subnet Mask . . . . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . . . . :



Status for domain STUDYNET on transport
\Device\NetBT_Tcpip_{E4CB6CDF-4BBC-4FF2-8253-4B3C78CE4109}
Browsing is active on domain.
Master browser name is: FRED
Master browser is running build 2600
1 backup servers retrieved from master FRED
\\FRED
There are 2 servers in domain STUDYNET on transport
\Device\NetBT_Tcpip_{E4CB6CDF-4BBC-4FF2-8253-4B3C78CE4109}
There are 1 domains in domain STUDYNET on transport
\Device\NetBT_Tcpip_{E4CB6CDF-4BBC-4FF2-8253-4B3C78CE4109}




Windows IP Configuration



Host Name . . . . . . . . . . . . : WILMA

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Mixed

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection :



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter

Physical Address. . . . . . . . . : 00-0B-6A-EF-6D-04

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Autoconfiguration IP Address. . . : 169.254.183.111

Subnet Mask . . . . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . . . . :



Status for domain STUDYNET on transport
\Device\NetBT_Tcpip_{D69482A1-0864-43A8-969F-70B137A4D350}
Browsing is active on domain.
Master browser name is: WILMA
Master browser is running build 2600
1 backup servers retrieved from master WILMA
\\WILMA
There are 1 servers in domain STUDYNET on transport
\Device\NetBT_Tcpip_{D69482A1-0864-43A8-969F-70B137A4D350}
There are 1 domains in domain STUDYNET on transport
\Device\NetBT_Tcpip_{D69482A1-0864-43A8-969F-70B137A4D350}


The new cable is installed and I don't get different results.