Replaced MB - now unable to connect to 2nd computer (advanced)

[BP]

Hello. My mainboard fried and I had a local repair shop replace it with a
new replacement board. The old board was an ASUS P4C800-E Deluxe with
onboard LAN (Intel Pro/1000 Adapter) and IEEE1394. I used this LAN
connection and a Linksys LNE100TX card to create a small local network (2
computers). The broadband modem was plugged into the Intel Adapter and the
second (W98) computer was plugged into the Linksys Adapter with a crossover
cable. Both computers were configured and the network ran well for several
months.
The new board is an Intel D865PERL w/o on board LAN or IEEE 1394. The repair
shop added a second NIC card, a 3Com along with my old Linksys. Both cards
are working and drivers installed. The broadband modem is plugged into the
3Com card and I have an internet access. The crossover cable is plugged into
the Linksys card but I do not have connectivity. I re-checked the network
configurations on both computers and they are correct (according to Carey
Holtzman's excellent site). Nothing has changed on the second computer.

The systray icon has an alert symbol and reads: "Status: limited or no
connectivity ..... network did not assign a network address to the computer"
Clicking "repair" results in: "Renewing your IP address; then: "Windows
could no finish repairing the problem because the following action cannot be
completed: Renewing your IP address".

On the "Local Area Connection" I saw a message: Invalid IP Address ;
Automatic Private Address = 169.254.226.3

I attempted to establish a static IP address (192.168.0.1) for the Linksys
(to try and ping the computers - they don't ping) and I got a message that
read: "this address is currently being used by another network adapter.
Using the same address on two adapters could cause problems." I checked in
the registry and found that the old Intel Pro/1000 connection is still
installed in several keys, including the Network keys in HKLM current
version.

The "Error Log" Lists errors:
DHCP - "Your computer has lost the lease to its IP address 24.218.46.20 on
the Network Card with network address 00010334245F." ;
" IPNATHLP - The Network Address Translator (NAT) was unable to request an
operation of the kernel-mode translation module. This may indicate
misconfiguration, insufficient resources, or an internal error. The data is
the error code." ;
" IPNATHLP- The DHCP allocator has disabled itself on IP address
169.254.226.3, since the IP address is outside the 192.168.0.0/255.255.255.0
scope from which addresses are being allocated to DHCP clients. To enable
the DHCP allocator on this IP address, please change the scope to include
the IP address, or change the IP address to fall within the scope."
" IPNATHLP- The DNS proxy agent was unable to read the local list of
name-resolution servers from the registry. The data is the error code.
" IPNATHLP- The Network Address Translator (NAT) was unable to request an
operation of the kernel-mode translation module. This may indicate
misconfiguration, insufficient resources, or an internal error. The data is
the error code."
" IPNATHLP- The DNS proxy agent encountered an error while obtaining the
local list of name-resolution servers. Some DNS or WINS servers may be
inaccessible to clients on the local network. The data is the error code."

I've also run the Network wizard again. No luck.

I have a feeling the problem is due to the old Intel Pro/1000 connection
still being installed in the registry, but I'm looking for any advice or
confirmation before I start deleting keys. Any help would be greatly
appreciated.

 

[Ron Lowe]

Hello. My mainboard fried and I had a local repair shop replace it with a
new replacement board. The old board was an ASUS P4C800-E Deluxe with
onboard LAN (Intel Pro/1000 Adapter) and IEEE1394. I used this LAN
connection and a Linksys LNE100TX card to create a small local network (2
computers). The broadband modem was plugged into the Intel Adapter and the
second (W98) computer was plugged into the Linksys Adapter with a
crossover cable. Both computers were configured and the network ran well
for several months.
The new board is an Intel D865PERL w/o on board LAN or IEEE 1394. The
repair shop added a second NIC card, a 3Com along with my old Linksys.
Both cards are working and drivers installed. The broadband modem is
plugged into the 3Com card and I have an internet access. The crossover
cable is plugged into the Linksys card but I do not have connectivity. I
re-checked the network configurations on both computers and they are
correct (according to Carey Holtzman's excellent site). Nothing has
changed on the second computer.

The systray icon has an alert symbol and reads: "Status: limited or no
connectivity ..... network did not assign a network address to the
computer" Clicking "repair" results in: "Renewing your IP address; then:
"Windows could no finish repairing the problem because the following
action cannot be completed: Renewing your IP address".

On the "Local Area Connection" I saw a message: Invalid IP Address ;
Automatic Private Address = 169.254.226.3

I attempted to establish a static IP address (192.168.0.1) for the Linksys
(to try and ping the computers - they don't ping) and I got a message that
read: "this address is currently being used by another network adapter.
Using the same address on two adapters could cause problems." I checked in
the registry and found that the old Intel Pro/1000 connection is still
installed in several keys, including the Network keys in HKLM current
version.

The "Error Log" Lists errors:
DHCP - "Your computer has lost the lease to its IP address 24.218.46.20 on
the Network Card with network address 00010334245F." ;
" IPNATHLP - The Network Address Translator (NAT) was unable to request an
operation of the kernel-mode translation module. This may indicate
misconfiguration, insufficient resources, or an internal error. The data
is the error code." ;
" IPNATHLP- The DHCP allocator has disabled itself on IP address
169.254.226.3, since the IP address is outside the
192.168.0.0/255.255.255.0 scope from which addresses are being allocated
to DHCP clients. To enable the DHCP allocator on this IP address, please
change the scope to include the IP address, or change the IP address to
fall within the scope."
" IPNATHLP- The DNS proxy agent was unable to read the local list of
name-resolution servers from the registry. The data is the error code.
" IPNATHLP- The Network Address Translator (NAT) was unable to request an
operation of the kernel-mode translation module. This may indicate
misconfiguration, insufficient resources, or an internal error. The data
is the error code."
" IPNATHLP- The DNS proxy agent encountered an error while obtaining the
local list of name-resolution servers. Some DNS or WINS servers may be
inaccessible to clients on the local network. The data is the error code."

I've also run the Network wizard again. No luck.

I have a feeling the problem is due to the old Intel Pro/1000 connection
still being installed in the registry, but I'm looking for any advice or
confirmation before I start deleting keys. Any help would be greatly
appreciated.

Yes, I agree that the ghost of the Intel adapter is the problem.
It has IP address 192.168.0.1 bound to it, and we need to get it to
relinquish that address to allow us to set up ICS on the new adapter.

Have a read of this:

Device Manager Does Not Display Devices That Are Not
Connected to the Windows XP-Based Computer
http://support.microsoft.com/default.aspx?scid=kb;en-us;315539

You might like to use this article to force Device Manager to show the
nonpresent devices.
The nonpresent ghosts should now reveal themselves.
You should then delete the nonpresent network adapter from device manager.

After doing this, disable and then re-enable ICS.
( use the wizard to set it up if you like, or just do it manually. )

 

[BP]

Yes, I agree that the ghost of the Intel adapter is the problem.
It has IP address 192.168.0.1 bound to it, and we need to get it to
relinquish that address to allow us to set up ICS on the new adapter.

Have a read of this:

Device Manager Does Not Display Devices That Are Not
Connected to the Windows XP-Based Computer
http://support.microsoft.com/default.aspx?scid=kb;en-us;315539

You might like to use this article to force Device Manager to show the
nonpresent devices.
The nonpresent ghosts should now reveal themselves.
You should then delete the nonpresent network adapter from device manager.

After doing this, disable and then re-enable ICS.
( use the wizard to set it up if you like, or just do it manually. )

Hey Thanks Ron. I'll check that out. Some more info: I set static addresses
to both computers (192.168.0.1 & 2) and they connect and can share files and
printers but I can't get ICS to work even though the W98 machine says the
gateway is open. The 20 second startup lag I never mentioned disappears too
(no surprise). I assume that "obtain IP addresses automatically" must be set
to get ICS to work?
I'll try and kill the ghosts. If the device manager trick doesn't work, what
do think about editing the registry? After setting a restore point, of
course.

 

[Ron Lowe]

Hey Thanks Ron. I'll check that out. Some more info: I set static

addresses to both computers (192.168.0.1 & 2) and they connect and can
share files and printers but I can't get ICS to work even though the W98
machine says the gateway is open. The 20 second startup lag I never
mentioned disappears too (no surprise). I assume that "obtain IP addresses
automatically" must be set to get ICS to work?

ICS clients can be configured manually,
or using "obtain IP addresses automatically".
Either way works OK, but I'd use automatic allocation as a preference.

If setting up an ICS client manually, you need to set the following TCP/IP
parameters:

IP address: 192.168.0.x where x is in the range 2-254
Subnet Mask: 255.255.255.0
Default gateway: 192.168.0.1
DNS server: 192.168.0.1 or your ISP's DNS server.

When you set it to 'Obtain Automatically', it will pick up settings as above
from the DHCP allocator built into the ICS host. This allocator only works
if ICS has managed to configure the LAN adapter as 192.168.0.1. After
removing the ghost of the Intel adaptr, you ought to be able to do this.

The lag you mention is most likely caused by the client attempting to get an
IP address from the DHCP allocator, but since the DHCP allocator is not
running ( due to the card not getting the 192.168.0.1. address ) then the
client times out after a period of time. This lag will go away once the
host is on 192.168.0.1 and the DHCP allocator can start.

I'll try and kill the ghosts. If the device manager trick doesn't work,
what do think about editing the registry? After setting a restore point,
of course.

I've never ripped out a LAN adapter my manually editing the registry, so I
can't comment on this. I certainly would not reccomend this unless you knew
what you were doing! I have used the "show non present devices" setting
several times and it's always worked for me.

 

[BP]

ICS clients can be configured manually,
or using "obtain IP addresses automatically".
Either way works OK, but I'd use automatic allocation as a preference.

If setting up an ICS client manually, you need to set the following TCP/IP
parameters:

IP address: 192.168.0.x where x is in the range 2-254
Subnet Mask: 255.255.255.0
Default gateway: 192.168.0.1
DNS server: 192.168.0.1 or your ISP's DNS server.

When you set it to 'Obtain Automatically', it will pick up settings as
above from the DHCP allocator built into the ICS host. This allocator
only works if ICS has managed to configure the LAN adapter as 192.168.0.1.
After removing the ghost of the Intel adaptr, you ought to be able to do
this.

The lag you mention is most likely caused by the client attempting to get
an IP address from the DHCP allocator, but since the DHCP allocator is not
running ( due to the card not getting the 192.168.0.1. address ) then the
client times out after a period of time. This lag will go away once the
host is on 192.168.0.1 and the DHCP allocator can start.



I've never ripped out a LAN adapter my manually editing the registry, so I
can't comment on this. I certainly would not reccomend this unless you
knew what you were doing! I have used the "show non present devices"
setting several times and it's always worked for me.

--
Ron, if you wern't so ugly I'd kiss you! The "show non present devices"
setting worked like a charm. Nice trick. The Pro/1000 adapter is history
and everything up and running and set to automatic configuration, just
like before the smoke started!

And now I can see a whole bunch of phantom/dupicate devices from the old
motherboard. I'm going to go after them now.
Thanks again.