ipconfig & Cable Disconnected

[hawat.thufir]

C:\>ipconfig

Windows 2000 IP Configuration

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Cable
Disconnected

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.2.139
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1

C:\>



1.) why isn't this showing the 802.11b USB NIC, please?
2.) why does the ethernet NIC show as "Cable Disconnected," please?
3.) can the PC act as a router between the external USB NIC and the
internal ethernet NIC?
4.} does this involve routing the internal network IP to outside
network?

this is so that a telephone adapter can plug into the RJ-45 socket. a
telephone plugs into the telephone adapter. this should enable VOIP
through the 802.11b NIC, to its router, to the cable modem.




thanks,

Thufir

 

[Herb Martin]

C:\>ipconfig

Windows 2000 IP Configuration

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Cable
Disconnected

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.2.139
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1

C:\>



1.) why isn't this showing the 802.11b USB NIC, please?

Some NICs have a "media detect" option and effectively
disable themselves when nothing is plugged into them.

By failing completely, the prevent the operating system
from using a NIC that won't work anyway.

It's usually an option though in the NIC (hardware) properties.

2.) why does the ethernet NIC show as "Cable Disconnected," please?

Nothing plugged into the NIC probably.

3.) can the PC act as a router between the external USB NIC and the
internal ethernet NIC?

Sure. Even workstations (and XP) can do that
although it's usually only done with Servers (or
with ICS by using the NAT/Router feature.)

4.} does this involve routing the internal network IP to outside
network?

[The above question is malformed or unclear as to
your meaning. ]

Routing is about forwarding packet from one interface
to another interface (from one network to another.)

There are methods for also mapping traffic from one
destination address to another address but this is not
part of routing -- it is usually involved with those
special NAT routers.

this is so that a telephone adapter can plug into the RJ-45 socket. a
telephone plugs into the telephone adapter. this should enable VOIP
through the 802.11b NIC, to its router, to the cable modem.

Huh?

I doubt that you can (usefully) plug an RJ-11 phone cable
into your RJ-45 Ethernet. (It will fit, but it won't do
anything useful.)

If you have a device that is a "phone" but also operates as
an IP host then that wouldn't be a telephone in the normal
sense and it would likely use an RJ-45 plug.

(Then it is just another node on a network, I.e., an IP
network, not a "telephone" network.)

 

[hawat.thufir]

Herb Martin wrote:
[..]

Some NICs have a "media detect" option and effectively
disable themselves when nothing is plugged into them.

[..]

I'll have to look into this "media detect" option. The telephone
adapter <http://www.linksys.com/products/product.asp?prid=651&scid=38>
is plugged into the ethernet NIC, so that's not the cause for the
unplugged cable message.

Sure. Even workstations (and XP) can do that
although it's usually only done with Servers (or
with ICS by using the NAT/Router feature.)

[..]

This is what's needed to get the VOIP working.

I doubt that you can (usefully) plug an RJ-11 phone cable
into your RJ-45 Ethernet. (It will fit, but it won't do
anything useful.)

[..]

Heh, sorry if that wasn't clear. The telephone plugs into the RJ-45
socket on the telephone adapter. The telephone adapter has an RJ-11
ethernet socket, which connects to the ethernet NIC. it's for VOIP.

How do I find out why the ethernet NIC gives "unplugged cable" when
it's connected to something, the telephone adapter in this case?


thanks,

Thufir

 

[Phillip Windell]

1.) why isn't this showing the 802.11b USB NIC, please?

Because it is disabled due to "Cable Disconnected"

2.) why does the ethernet NIC show as "Cable Disconnected," please?

Usually a physical problem with the cabling (bad cable, incorrect wiring
pattern, nothing "live" on the opposite end of the cable, etc)

3.) can the PC act as a router between the external USB NIC and the
internal ethernet NIC?

Yes, but you may not need "routing",...you may need "NAT",...they are
related, but are not the same thing.

4.} does this involve routing the internal network IP to outside
network?

Don't know in this context....

this is so that a telephone adapter can plug into the RJ-45 socket. a
telephone plugs into the telephone adapter. this should enable VOIP
through the 802.11b NIC, to its router, to the cable modem.

Have no idea....

 

[JM]

quoting:

1.) why isn't this showing the 802.11b USB NIC, please?

The thing about wireless, The OS can't see the wireless layer. The OS can
only see the ethernet layer. That means every single wireless adapter you
throw at the OS, it'll never say it's "wireless", "802.11b", etc. Just a
generic "ethernet adapter". You see, every wireless adapter has an ethernet
layer inside, then the hardware inside the wireless adapter bridges the data
over the air.

2.) why does the ethernet NIC show as "Cable Disconnected," please?
3.) can the PC act as a router between the external USB NIC and the
internal ethernet NIC?
4.} does this involve routing the internal network IP to outside
network?

this is so that a telephone adapter can plug into the RJ-45 socket. a
telephone plugs into the telephone adapter. this should enable VOIP
through the 802.11b NIC, to its router, to the cable modem.

If I got you correctly, the phone is plugged into the ethernet adapter that
is showing "cable disconnected". I bet you have the wrong cable installed.
Try a crossover cable instead.

Since you already have wireless, to make your setup simpler, I would just
use a wireless adapter (like Linksys WET11) with the phone adapter. That
way there, the phone goes directly to the router (wirelessly) and it doesn't
have to interact with your computer.

 

[hawat.thufir]

quoting:

The thing about wireless, The OS can't see the wireless layer. The OS can
only see the ethernet layer. That means every single wireless adapter you
throw at the OS, it'll never say it's "wireless", "802.11b", etc. Just a
generic "ethernet adapter". You see, every wireless adapter has an ethernet
layer inside, then the hardware inside the wireless adapter bridges the data
over the air.

[..]

The description reads ": SMC EZ Connect Wireless USB," which is how
I'd describe it.

I know what you're saying, in that this adapter is ethernet, just of
wireless type. The OS is just seeing "ethernet" and not the "wireless"
part. The USB NIC is taking care of the "wireless" and just sending
plain old ethernet signal via the USB port.


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

C:\Documents and Settings\Administrator>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 2:

Media State . . . . . . . . . . . : Cable Disconnected
Description . . . . . . . . . . . : SiS 900 PCI Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-0A-E6-A0-24-27

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SMC EZ Connect Wireless
USB Adapter
(SMC2662W)
Physical Address. . . . . . . . . : 00-04-E2-A9-F8-BF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.139
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. . . . . . . . . . : Thursday, March 03, 2005
10:28:13 AM

Lease Expires . . . . . . . . . . : Thursday, March 10, 2005
9:18:51 AM

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

If I got you correctly, the phone is plugged into the ethernet adapter that
is showing "cable disconnected". I bet you have the wrong cable installed.
Try a crossover cable instead.

exactly what Linksys technical support says. That'd be the same effect
as phone-->PAP2-->hub-->internal ethernet NIC? It could also be
phone-->PAP2-->(crossover ethernet cable)-->internal ethernet, I
believe.

Since you already have wireless, to make your setup simpler, I would just
use a wireless adapter (like Linksys WET11) with the phone adapter. That
way there, the phone goes directly to the router (wirelessly) and it doesn't
have to interact with your computer.

technically that makes sense; politically, it doesn't. I share the
connection with my landlord. It's a bit sneaky, but I'd rather not ask
him for help on this. I don't think he'd mind, since wireless
internet's part of the rent, but VOIP might be pushing the boundaries.

once I get the crossover cable, or a hub, how do I "turn on" the
internal NIC, please?

I'm dissapointed by <http://www.digitalvoice.ca/> because they
explicitly told me I could just plug the PAP2 into the ethernet cable
*before* I picked up the PAP2, but that's off topic.


thanks,

-Thufir

 

[jason.mangiafico]

quoting:

The thing about wireless, The OS can't see the wireless layer. The OS can
only see the ethernet layer. That means every single wireless adapter you
throw at the OS, it'll never say it's "wireless", "802.11b", etc. Just a
generic "ethernet adapter". You see, every wireless adapter has an ethernet
layer inside, then the hardware inside the wireless adapter bridges the data
over the air.

[..]

The description reads ": SMC EZ Connect Wireless USB," which is how
I'd describe it.

I know what you're saying, in that this adapter is ethernet, just of
wireless type. The OS is just seeing "ethernet" and not the "wireless"
part. The USB NIC is taking care of the "wireless" and just sending
plain old ethernet signal via the USB port.

Correct.



[...]

If I got you correctly, the phone is plugged into the ethernet adapter that
is showing "cable disconnected". I bet you have the wrong cable installed.
Try a crossover cable instead.

exactly what Linksys technical support says. That'd be the same effect
as phone-->PAP2-->hub-->internal ethernet NIC? It could also be
phone-->PAP2-->(crossover ethernet cable)-->internal ethernet, I
believe.

Since you already have wireless, to make your setup simpler, I

would

just
use a wireless adapter (like Linksys WET11) with the phone adapter. That
way there, the phone goes directly to the router (wirelessly) and

it

doesn't
have to interact with your computer.

technically that makes sense; politically, it doesn't. I share the
connection with my landlord. It's a bit sneaky, but I'd rather not ask
him for help on this. I don't think he'd mind, since wireless
internet's part of the rent, but VOIP might be pushing the

boundaries.


You can install a router so that your landlord can't "see" more than
one IP address. This router has to be bridged via the wireless
connection you have now. You can even install a wireless router/access
point for yourself. This can be done either by a "repeater" device, or
a router with a wireless bridge connected to the WAN port. Then you
can have more than one computer and devices online at the same time.

once I get the crossover cable, or a hub, how do I "turn on" the
internal NIC, please?

The NIC should be already ON by default, but to check to make sure,
right click on "my network places", and then properties. Is any of
your NICs greyed out? If so, right click on it and then "enable".

I'm dissapointed by <http://www.digitalvoice.ca/> because they
explicitly told me I could just plug the PAP2 into the ethernet cable
*before* I picked up the PAP2, but that's off topic.

What probably going on here is that the cable provided with the unit
was meant to go directly into a router. But to go go into another NIC
on a computer would need to replace the cable with a crossover type.

 

[hawat.thufir]

What probably going on here is that the cable provided with the unit
was meant to go directly into a router. But to go go into another NIC
on a computer would need to replace the cable with a crossover type.

exactly. i thought i'd covered my bases *before* picking up the unit,
but, eh, never mind. the crossover cable fixed it


thanks,

Thufir