Simple home network stops working ?

Chuck you going to beleive this, I got it fixed. Here is where I went.
Run through MVP Hans-Georg Michna's network troubleshooter he

http://www.michna.com/kb/wxnet.htm

I check the one that said "The LAN adapter IP address is: 0.0.0.0 (i.e. no
valid IP address). [ip=3]
This is what it said
After setting the restore point, to remove this dependency, do this:

a.. Click: Start
b.. Click: Run...
c.. Type: regedit
d.. Click: OK
e.. Navigate to the following keys in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\DHCP
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\NetBT
f.. For each of these, on the right side, double-click: DependOnService
g.. Delete any lines containing either SYMTDI or NISDRV.
h.. Click: OK
i.. Close the Registry Editor.
j.. Reboot.
Chuck I sure thank you far all your help, you have been great. Anything I
can do far you just ask. Thanks again


"Chuck" wrote in message
...
On Tue, 7 Dec 2004 15:37:03 -0800, "seniorshot"
wrote:



Hi Chuck Again

Latest instalment......

I managed to update the driver on the laptop to latest dated 15/7/2004

On desktop I removed the LAN PCI card and re-installed the motherboard
integrated Lan card and updated the SIS900 driver for this adaptor from
the
SIS site - dated 12/6/2004.

Unfortunately the problem remains.
I ran the Cdiag.cmd program and it gave the same results as previously
(The
desktop had a new IPaddress 169.254.14.252( I suppose due to change of
Adaptor)

Chuck ..You must be running out of ideas now ??

regards
Roger

Hi Roger,

I have to admit we're running out of options.

To recap, you have two computers - a desktop and a laptop, connected by
cross-over cable, using APIPA addresses, which are properly assigned to
each.
Neither can successfully ping each other by ip address. They have other
connectivity problems, which are higher level. All problems are
symmetrical,
and consistent.

You've tested the network adapters, and replaced the network cable
(cross-over).
You've updated the drivers for the network adapters.

You've un installed the Norton Personal Firewall, using the intensive
(non-wizard based) Symantec un install procedure. You have Windows
Firewall (XP
SP2) enabled on both computers, with the File and Printer Sharing
exception
checked.

I presume that you updated CDiag to reflect the new ip address on
Rowanlea, on
both computers?

Details to check:
1) Is the Norton firewall part of Norton Internet Security or do you have
Norton Antivirus also? I have had one other person tell me that removal
of
Norton Antivirus was necessary in her case, when she had a problem similar
to
yours.
2) Disable the Windows Firewall. Ensure that the Windows Firewall
(Control
Panel - Administrative Tools - Services) service is Running / Started,
with
Startup type Automatic. With SP2, the WF service must be running for
network
connectivity.
3) Isolate the problem. Take Compaq to a friends LAN, and see if it will
connect. Get a friend to bring a laptop to Rowanlea, and try to connect.

There are other things we can check when file sharing does not work. But
first,
you have to get basic connectivity, with successful pinging by ip address,
working.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

On Tue, 7 Dec 2004 15:37:03 -0800, "seniorshot"
wrote:



Hi Chuck Again

Latest instalment......

I managed to update the driver on the laptop to latest dated 15/7/2004

On desktop I removed the LAN PCI card and re-installed the motherboard
integrated Lan card and updated the SIS900 driver for this adaptor from the
SIS site - dated 12/6/2004.

Unfortunately the problem remains.
I ran the Cdiag.cmd program and it gave the same results as previously (The
desktop had a new IPaddress 169.254.14.252( I suppose due to change of
Adaptor)

Chuck ..You must be running out of ideas now ??

regards
Roger

Hi Roger,

I have to admit we're running out of options.

To recap, you have two computers - a desktop and a laptop, connected by
cross-over cable, using APIPA addresses, which are properly assigned to each.
Neither can successfully ping each other by ip address. They have other
connectivity problems, which are higher level. All problems are symmetrical,
and consistent.

You've tested the network adapters, and replaced the network cable (cross-over).
You've updated the drivers for the network adapters.

You've un installed the Norton Personal Firewall, using the intensive
(non-wizard based) Symantec un install procedure. You have Windows Firewall (XP
SP2) enabled on both computers, with the File and Printer Sharing exception
checked.

I presume that you updated CDiag to reflect the new ip address on Rowanlea, on
both computers?

Details to check:
1) Is the Norton firewall part of Norton Internet Security or do you have
Norton Antivirus also? I have had one other person tell me that removal of
Norton Antivirus was necessary in her case, when she had a problem similar to
yours.
2) Disable the Windows Firewall. Ensure that the Windows Firewall (Control
Panel - Administrative Tools - Services) service is Running / Started, with
Startup type Automatic. With SP2, the WF service must be running for network
connectivity.
3) Isolate the problem. Take Compaq to a friends LAN, and see if it will
connect. Get a friend to bring a laptop to Rowanlea, and try to connect.

There are other things we can check when file sharing does not work. But first,
you have to get basic connectivity, with successful pinging by ip address,
working.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

"Chuck" wrote in message
...
On Tue, 7 Dec 2004 15:37:03 -0800, "seniorshot"
wrote:



Hi Chuck Again

Latest instalment......

I managed to update the driver on the laptop to latest dated 15/7/2004

On desktop I removed the LAN PCI card and re-installed the motherboard
integrated Lan card and updated the SIS900 driver for this adaptor from
the
SIS site - dated 12/6/2004.

Unfortunately the problem remains.
I ran the Cdiag.cmd program and it gave the same results as previously
(The
desktop had a new IPaddress 169.254.14.252( I suppose due to change of
Adaptor)

Chuck ..You must be running out of ideas now ??

regards
Roger

Hi Roger,

I have to admit we're running out of options.

To recap, you have two computers - a desktop and a laptop, connected by
cross-over cable, using APIPA addresses, which are properly assigned to
each.
Neither can successfully ping each other by ip address. They have other
connectivity problems, which are higher level. All problems are
symmetrical,
and consistent.

You've tested the network adapters, and replaced the network cable
(cross-over).
You've updated the drivers for the network adapters.

You've un installed the Norton Personal Firewall, using the intensive
(non-wizard based) Symantec un install procedure. You have Windows
Firewall (XP
SP2) enabled on both computers, with the File and Printer Sharing
exception
checked.

I presume that you updated CDiag to reflect the new ip address on
Rowanlea, on
both computers?

Details to check:
1) Is the Norton firewall part of Norton Internet Security or do you have
Norton Antivirus also? I have had one other person tell me that removal
of
Norton Antivirus was necessary in her case, when she had a problem similar
to
yours.
2) Disable the Windows Firewall. Ensure that the Windows Firewall
(Control
Panel - Administrative Tools - Services) service is Running / Started,
with
Startup type Automatic. With SP2, the WF service must be running for
network
connectivity.
3) Isolate the problem. Take Compaq to a friends LAN, and see if it will
connect. Get a friend to bring a laptop to Rowanlea, and try to connect.

There are other things we can check when file sharing does not work. But
first,
you have to get basic connectivity, with successful pinging by ip address,
working.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

Forgive me for coming in late. Just want to check some things.

As Chuck said, disable the Windows Firewall, at least for now. By that I
mean in the firewall control panel, not the service. It could be blocking
pings.

Network adapters typically have at least two lights on them. One for link
beat, meaning the cable is connected, and another for traffic. Do you have
any lights lit?

Until you have connectivity problems solved, use numeric ip addresses only
(eg 169.254.x.x)

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Check MS knowledge base for "reinstalling tcp/ip",

"Chuck" wrote in message
...
On Tue, 7 Dec 2004 15:37:03 -0800, "seniorshot"
wrote:



Hi Chuck Again

Latest instalment......

I managed to update the driver on the laptop to latest dated 15/7/2004

On desktop I removed the LAN PCI card and re-installed the motherboard
integrated Lan card and updated the SIS900 driver for this adaptor from
the
SIS site - dated 12/6/2004.

Unfortunately the problem remains.
I ran the Cdiag.cmd program and it gave the same results as previously
(The
desktop had a new IPaddress 169.254.14.252( I suppose due to change of
Adaptor)

Chuck ..You must be running out of ideas now ??

regards
Roger

Hi Roger,

I have to admit we're running out of options.

To recap, you have two computers - a desktop and a laptop, connected by
cross-over cable, using APIPA addresses, which are properly assigned to
each.
Neither can successfully ping each other by ip address. They have other
connectivity problems, which are higher level. All problems are
symmetrical,
and consistent.

You've tested the network adapters, and replaced the network cable
(cross-over).
You've updated the drivers for the network adapters.

You've un installed the Norton Personal Firewall, using the intensive
(non-wizard based) Symantec un install procedure. You have Windows
Firewall (XP
SP2) enabled on both computers, with the File and Printer Sharing
exception
checked.

I presume that you updated CDiag to reflect the new ip address on
Rowanlea, on
both computers?

Details to check:
1) Is the Norton firewall part of Norton Internet Security or do you have
Norton Antivirus also? I have had one other person tell me that removal
of
Norton Antivirus was necessary in her case, when she had a problem similar
to
yours.
2) Disable the Windows Firewall. Ensure that the Windows Firewall
(Control
Panel - Administrative Tools - Services) service is Running / Started,
with
Startup type Automatic. With SP2, the WF service must be running for
network
connectivity.
3) Isolate the problem. Take Compaq to a friends LAN, and see if it will
connect. Get a friend to bring a laptop to Rowanlea, and try to connect.

There are other things we can check when file sharing does not work. But
first,
you have to get basic connectivity, with successful pinging by ip address,
working.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

On Tue, 7 Dec 2004 15:37:03 -0800, "seniorshot"
wrote:



Hi Chuck Again

Latest instalment......

I managed to update the driver on the laptop to latest dated 15/7/2004

On desktop I removed the LAN PCI card and re-installed the motherboard
integrated Lan card and updated the SIS900 driver for this adaptor from the
SIS site - dated 12/6/2004.

Unfortunately the problem remains.
I ran the Cdiag.cmd program and it gave the same results as previously (The
desktop had a new IPaddress 169.254.14.252( I suppose due to change of
Adaptor)

Chuck ..You must be running out of ideas now ??

regards
Roger

Roger,

One more thing occurs to me. This could be LSP / Winsock or TCP/IP corruption
too. You'll have to do each on both computers, though.

1) Check LSP / Winsock corruption on both computers.
http://support.microsoft.com/?id=318584
http://support.microsoft.com/?id=811259

If XP SP2, Start - Run - "cmd". Type "netsh winsock reset catalog" into the
command window.

Give LSP-Fix http://www.cexx.org/lspfix.htm, WinsockFix
http://www.tacktech.com/display.cfm?ttid=257, or WinsockXPFix
http://www.spychecker.com/program/winsockxpfix.html a shot.

2) Reset TCP/IP on both computers.
http://support.microsoft.com/?id=299357

Start - Run - "cmd". Type "netsh int ip reset c:\netsh.txt" into the command
window.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

Hi Chuck

SUCCESS SUCCESS SUCCESS

The problem was Norton Anti Virus 2003 on the laptop !

I have Norton AntiVirus on both machines but it's part of Norton SystemWorks
2003 on the Desktop, whereas its the stand alone version on the Laptop.
I was reluctant to uninstall because of the age of the products and the
number of updates that I've received. But when needs must !!!!- I'd tried
just about everything else.

I just uninstalled the NAV from the Laptop and this seemed to clear the
problem. I've now re-installed it, and the network appears to be running OK.

Chuck you're a star. Many thanks for all your help and suggestions - I could
not have solved this myself.

I'm considering Broadband and a wireless network for my 2 computers but the
problems which might occur are putting me off taking this step. !!!!!

Once again many thanks
regards
Roger

On Wed, 8 Dec 2004 12:15:03 -0800, "seniorshot"
wrote:

Hi Chuck

SUCCESS SUCCESS SUCCESS

The problem was Norton Anti Virus 2003 on the laptop !

I have Norton AntiVirus on both machines but it's part of Norton SystemWorks
2003 on the Desktop, whereas its the stand alone version on the Laptop.
I was reluctant to uninstall because of the age of the products and the
number of updates that I've received. But when needs must !!!!- I'd tried
just about everything else.

I just uninstalled the NAV from the Laptop and this seemed to clear the
problem. I've now re-installed it, and the network appears to be running OK.

Chuck you're a star. Many thanks for all your help and suggestions - I could
not have solved this myself.

I'm considering Broadband and a wireless network for my 2 computers but the
problems which might occur are putting me off taking this step. !!!!!

Once again many thanks
regards
Roger


Roger,

Well that's good news indeed! Thanks for the feedback. And please don't let
this experience put you off updating - broadband and wireless are excellent
things to have.

But, if you get broadband, PLEASE get a NAT router for convenience and
protection. Stay away from USB modems, which require you to connect one
computer as a host as you have right now.

And if you use a wireless LAN, remember to protect yourself especially.
Remember with a wireless LAN, your neighbors may be far outside your front door.

Here's a story about somebody's very stupid wireless neighbor. Don't expect all
wireless neighbors to be this stupid.
http://www.canoe.ca/NewsStand/LondonFreePress/News/2003/11/22/264890.html.

The point is, you need to protect a wireless LAN with more precautions than just
the NAT firewall.

Change the router management password, and disable remote (WAN) management.

Enable WEP / WPA. Use non-trivial (non-guessable) values for each. (No "My dog
has fleas").

Enable MAC filtering.

Change the subnet of your LAN - don't use the default.

Disable DHCP, and assign an address to each computer manually.

Install a software firewall on every computer connected to a wireless LAN. Put
manually assigned ip addresses in the Local (highly trusted) Zone. Open the
following ports for file sharing, only in the Local Zone: TCP 139, 445; UDP 137,
138, 445.

Don't disable SSID broadcast - some configurations require the SSID broadcast.
But change the SSID itself - to something that doesn't identify you, or the
equipment.

Enable the router activity log. Examine it regularly. Know what each
connection listed represents - you? a neighbor?.

Use non-trivial accounts and passwords on every computer connected to a wireless
LAN. Disable or delete Guest userid, if possible (XP Home is a bad choice
here). Rename Administrator, to a non-trivial value, and give it a non-trivial
password. Never use the Administrator renamed account for day to day
activities, only when intentionally doing administrative tasks.

Stay educated - know what the threats are. Newsgroups alt.internet.wireless and
microsoft.public.windows.networking,wireless are good places to start.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.