second NIC disabled on-board NIC

  • Thread starter Thread starter hawat.thufir
  • Start date Start date
H

hawat.thufir

I have two computers, named arrakis and caladan. on arrakis
I recently installed a new internal NIC, which seems to
interfere with the onboard NIC. why is the new
NIC doing that, please?

on arrakis, the "Local Area Connection Properties"
has the following info:

"Client for Microsoft Networks"
"File and Printer Sharing for Microsoft Networks"
"Internet Protocol (TCP/IP)"

which are all selected. clicking "configure" gives the following,
from the general tab:

"D-Link DFE 538TX 10/100 Adapter
Device type: Network adapters
Manufacturer: D-Link Corporation
Location: Location 1 (PCI bus 0, device 9, function 0)

Device status:

This device is working properly.

If you are haveing problems with this device, click Troubleshooter
to start the troubleshooter."

I'm not having a problem with the D-Link NIC, but the onboard NIC.
the onboard NIC for Arrakis isn't showing anywhere.


I want the internet connection to come into Arrakis, and then
connect arrakis and caladan with a crossover ethernet cable.
however, arrakis is only showing a single NIC, as far
as I can tell. the internet connection is wi-fi through
an asus 802.11b/g adapter.

links:
<http://support.microsoft.com/default.aspx?scid=kb;en-us;169289>
<http://support.microsoft.com/default.aspx?scid=kb;en-us;301281>
<http://support.microsoft.com/default.aspx?scid=kb;en-us;307311>
<http://www.ecsusa.com/downloads/manual_k7s.html> arrakis mother board
<http://usa.asus.com/prog/spec.asp?m=WL-330g&langs=09> wi-fi adapter
<http://www.dlink.ca/product.php?PID=124> new NIC on arrakis


thanks,

Thufir
 
I have two computers, named arrakis and caladan. on arrakis
I recently installed a new internal NIC, which seems to
interfere with the onboard NIC. why is the new
NIC doing that, please?
Click to expand...

Is the operating system installed with a standard HAL or an ACPI HAL? Is the
onboard NIC enabled in bios? Did you verify the motherboard's shared
resource table for add on adapters? Did you verify if the NIC was disabled
in Device Manager (ie: hidden device?).
 
Peter said:
Is the operating system installed with a standard HAL or an ACPI HAL? Is the
onboard NIC enabled in bios? Did you verify the motherboard's shared
resource table for add on adapters? Did you verify if the NIC was disabled
in Device Manager (ie: hidden device?).
Click to expand...



arrakis uses a k7som+ motherboard, see link below. Device manager
gives:

Network adapters
D-Link DFE-538TX 10/100 Adapter

Other devices
ethernet controller
Universal Serial Bus (USB) Controller
Video Controller (VGA compatible)

it's only showing the new NIC, as far as I can tell.

beyond, that I'm unable to answer those questions without more
research. can those questions be rephrased, please?


links:
<http://www.ecsusa.com/downloads/manual_k7s.html>
<http://usa.asus.com/prog/spec.asp?m=WL-330g&langs=09>
<http://www.dlink.ca/product.php?PID=124>


some command line stuff, from caladan:


C:\>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : CALADAN
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100
PCI
For Complete PC Management NIC (3C905C-TX)
Physical Address. . . . . . . . . : 00-50-DA-68-8C-B2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.120
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : Tuesday, June 21, 2005
2:06:4
0 PM
Lease Expires . . . . . . . . . . : Tuesday, June 28, 2005
2:06:4
0 PM

C:\>

C:\>
C:\>route print
=========================================================================
==
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 50 da 68 8c b2 ...... 3Com EtherLink PCI
=========================================================================
==
=========================================================================
==
Active Routes:
Network Destination Netmask Gateway Interface
Metr
ic
0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.120
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.2.0 255.255.255.0 192.168.2.120 192.168.2.120
1
192.168.2.120 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.2.255 255.255.255.255 192.168.2.120 192.168.2.120
1
224.0.0.0 224.0.0.0 192.168.2.120 192.168.2.120
1
255.255.255.255 255.255.255.255 192.168.2.120 192.168.2.120
1
Default Gateway: 192.168.2.1
=========================================================================
==
Persistent Routes:
None




from arrakis, this I had to type in:


c:\ ipconfig /all

Windows 2000 IP Configuration
Host Name: arrakis
Primary DNS suffix:
Node Type: Broadcast
IP Routing enabled: No
WINS Proxy enabled: No

Ethernet adapter Local Area Connection:
Media State: Cable Disconnected
Description: D-Link DFE-538TX 10/100 Adapter
Physical Address: 00-0D-88-37-FA-22

C:\ route print

interface list
0x1 MS TCP Loopback interface
0x1000003 00 0d 88 37 fa 22 D-Link DFE-538TX 10/100 Adapter


Active Routes:

Network Destination Netmask Gateway Interface Metric
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
255.255.255.255 255.255.255.255 255.255.255.255 255.255.255.255 1

Persistent Routes:
None

C:\

background, if you like:


experiments with ping:

using an ethernet crossover cable I conducted some simple
experiments with ping between two computers, arrakis and caladan.
For now, I just want to be able to re-produce a succesful ping.

arrakis is the "problem" computer, it has two NIC's the onboard
and the d-link. neither NIC is fully co-operating.
I've had some success with the d-link NIC, no success with the
onboard NIC.

caladan is the backup computer, older but simpler.
caladan is also running win2k.
caladan has access to the internet, but just one NIC. with
just one ethernet port, caladan can either connect to the
internet with a wi-fi 802.11b/g network adapter or connect
to arrakis with the crossover cable, but not both simultaneously.

the 802.11b/g network adapter only seems to work in caladan,
it was working in caladan, but after resetting the network
adapter, no more. the wi-fi adapter works very nicely.

by booting both computers simultaneously, as I recall,
I was able to ping. on arrakis, "ping caladan" gave
good results, and on caladan "ping arrakis" also gave good
results, no lost packets. the crossover cable was plugged
into the d-link NIC for arrakis.

this establishes that the cross-over cable is ok, and that
the d-link NIC for arrakis are working ok.

I then tried mixing up a few things, like switching back
to the regular ethernet cable, and connecting arrakis
and caladan via a hub, I also tried the crossover cable in
the d-link NIC of arrakis.

after trying some different combinations I'm now unable
to reproduce any sort of ping at all. for the moment,
I just want to reproduce that ping. I should've kept
a log of what I was doing, I guess!


thanks,

Thufir
 
Peter said:
Is the operating system installed with a standard HAL or an ACPI HAL? Is the
onboard NIC enabled in bios? Did you verify the motherboard's shared
resource table for add on adapters? Did you verify if the NIC was disabled
in Device Manager (ie: hidden device?).
Click to expand...

It's ACPI HAL, as shown by:
From the Device Manager:
Click to expand...
Arrakis
Computer
Advanced Configuration and Power Interface (ACPI) PC

opening the ACPI branch gives the following tabs:

general
Advanced Configuration and Power Interface (ACPI) PC

Device type: Computer
Manufacturer: (Standard computers)
Location: Unknown

Device status

This device is working properly.

If you are having problems with this device, click Troubleshooter
to start the troubleshooter.


Driver
Advanced Configuration and Power Interface (ACPI) PC


Driver Provider: Microsoft
Driver Date: 11/14/1999
Driver Version: 5.0.2183.1
Digital Signer: Microsoft Windows 2000 Publisher

To view details about the driver files loaded for this device,
click Driver Details. To uninstall the driver for this
device, click Uninstall. To update the driver files for this
device, click Update Driver.

(I'm trying to get the answers to the other questions,
any help with that, please)?

thanks,

Thufir


links:

<http://support.microsoft.com/default.aspx?scid=kb;EN-US;237556#XSLTH3120121122120121120120>
 
Why do you believe that the onboard NIC, if disabled in BIOS and not
installed in the OS, is interfering with the NIC you want to use? If both
are PnP, enabled, drivers installed, and connected to the same hub, even the
worst-case scenario (barring unlikey MAC or IP collision) won't result in
much going wrong other than a few obvious error messages. What symptoms do
you have?
 
j9 said:
Why do you believe that the onboard NIC, if disabled in BIOS and not
installed in the OS, is interfering with the NIC you want to use? If both
are PnP, enabled, drivers installed, and connected to the same hub, even the
worst-case scenario (barring unlikey MAC or IP collision) won't result in
much going wrong other than a few obvious error messages. What symptoms do
you have?
Click to expand...


both NIC's are, or should be, PnP. I don't know that there's a
BIOS issue here, the cause of this is a mystery. The problems
with the onboard NIC started immediately after installing
the D-Link NIC, so there's a correlation, however.

arrakis and caladan can ping if the connection is from
the D-Link NIC. they can't ping if the connection
is from the onboard NIC of arrakis.


D-Link => caladan SUCCESS
onboard => caladan FAILURE


arrakis:

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-1999 Microsoft Corp.

C:\>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : arrakis
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : D-Link DFE-538TX 10/100
Adapter
Physical Address. . . . . . . . . : 00-0D-88-37-FA-22
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration IP Address. . . : 192.168.10.123
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

C:\>ping 192.168.10.125

Pinging 192.168.10.125 with 32 bytes of data:

Reply from 192.168.10.125: bytes=32 time<10ms TTL=128
Reply from 192.168.10.125: bytes=32 time<10ms TTL=128
Reply from 192.168.10.125: bytes=32 time<10ms TTL=128
Reply from 192.168.10.125: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.10.125:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>


caladan:


Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\Administrator>cd ..

C:\Documents and Settings>cd ..

C:\>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : CALADAN
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100
PCI
For Complete PC Management NIC (3C905C-TX)
Physical Address. . . . . . . . . : 00-50-DA-68-8C-B2
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.125
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

C:\>ping 192.168.10.123

Pinging 192.168.10.123 with 32 bytes of data:

Reply from 192.168.10.123: bytes=32 time<10ms TTL=128
Reply from 192.168.10.123: bytes=32 time<10ms TTL=128
Reply from 192.168.10.123: bytes=32 time<10ms TTL=128
Reply from 192.168.10.123: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.10.123:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>



thanks,

Thufir
 
Back
Top