Substitute for dead RJ45 Ethernet connection

On Mon, 26 Feb 2018 17:00:11 -0800, cameo wrote:

On 2/26/2018 1:35 AM, Paul wrote:
cameo wrote:
On 2/25/2018 9:02 PM, Paul wrote:
cameo wrote:
On 2/25/2018 6:34 PM, Paul wrote:
cameo wrote:



*From Command Prompt

*** ipconfig

can tell you about whether an address has been acquired.

Here it is with the WiFi turned on. As you see, the WiFi connection at
the bottom does have the Gateway IP, but the new USB adapter Local
Area Connection 3 does not.

Correct, and not only that, Local Area Connection 3 does not have a
*valid* IP address for your LAN. As Paul suggested, it has an APIPA
address, (169.254.x.x), which will not work to connect to the rest of
the PCs on your LAN and will not work to connect to your router and will
not work to connect to the Internet. (See Plugable8)

So how does one end up with an APIA address? That happens when the
adapter is configured to use DHCP but no DHCP server responds to this
PC's request for a DHCP assignment. When the DHCP request times out,
Windows autoconfigures its network adapter using APIPA.

If the adapter returns the APIPA address, then it isn't making
contact with the DHCP server on the wired router. Or maybe for
some reason the DHCP server is using MAC filtering to deny
an address to the NIC ?

I doubt it if you look at this page of my router. It has two Notebook7
entries with different IPs. The 192.168.1.191 is the new USB3 adapter
and the 192.168.1.188 is the WiFi.

I may have missed the screenshot where the USB adapter had a valid IP,
but if it did then at that time your new adapter was working. It had a
valid LAN address and a valid gateway address. You would have been able
to use the new adapter to access the router, the Internet, and the rest
of the PCs on your LAN via the USB adapter.

Actually, the Gbe connection does not have an IP address. Just check the
ptreviously sent Plugable8.jpg image

Correct. At the time that that info was taken, Local Area Connection 3
had an APIPA address while Local Area Connection 2 is not connected.

The ping does not eork even on the same machines between wired and
wireless connections and same across the two machines (fom/to the GbE
connection.)

And it won't while this one PC is on an APIPA island. It, alone, has a
169.254.x.x IP address and nothing else on the LAN does, so it has no
one to talk to.

The relevant section is already on that Plugable8.jpg. What else do you
need?

Plugable8 shows that DHCP failed. You can try to work around that by
configuring a static IP, network mask, and gateway, but I get the
feeling that you'll need more details on how to do that. Paul and others
have given tips, I believe.

If your DNS wasn't working, you should still be able to open
a web browser and enter

* http://156.151.59.35

and it should be the same as doing

* http://www.sun.com***************** # The Sun/Oracle web site

Actually, without Internet connection I can't even get local IP page up
in my Chrome browser. It's kind'a counterintuitive to me why that should
be so.

If you don't have a valid IP address, (which you don't in Plugable8),
then nothing else will work. No access to anything.


--

Char Jackson

On Wed, 28 Feb 2018 18:59:36 -0800, cameo wrote:

Yes, the router is set to use DHCP within a certain range of IP
addresses. But because I use several IP cameras as well, I had to
reserve some stable IPs for them so I could use port forwarding to them
from outside calls.

You should make sure you reserved those camera IPs to addresses that
fall outside of the router's DHCP scope. Most SOHO NAT routers aren't
smart enough to check whether an address is already being used before
they hand it out to the PC that just made a DHCP request. The result
could well be an address conflict, which seriously affects both PCs.

Personally I don't see the rational of why I could
also not uses reserved IP for this GbE adapter. In any case I've tried
to use both reserved and unreserved IPs for it without any difference in
results.

No clue what that means. Are you saying you've been manually
(statically) configuring the IP address, network mask, and gateway
address on the new adapter? If so, always use an IP address that falls
outside of the DHCP scope and isn't being used anywhere else on the LAN.
Use the exact same network mask, usually 255.255.255.0, on every PC on
the LAN. Lastly, configure the exact same gateway address on each PC,
which I think in your case is 192.168.1.1

BTW this router's (D-Link DIR-825) DHCP allocates new IPs starting from
the highest available one in the pool that I set to 100 to 200 and
continues to lower available numbers,

So it doesn't sound as if the DHCP pool is exhausted. That's good to
know.

skipping the ones that are reserved for given MAC IDs.

Reserving IP addresses that lie within the DHCP scope is usually
considered to be a misconfiguration. That's certainly what I would call
it.


--

Char Jackson

cameo,

Snip of all the above....


This is getting to get very convoluted and way out-of-hand for
troubleshooting that needs to be done step-by-step to establish what works
and what doesn't.

The thread started with you stating that the onboard Ethernet port is not
working. Based on what findings and diagnostics?

You have made many changes and tried a number of things which may or may not
have helped a thing except add confusion. Take it back to the basics:

1. Pull that USB to Ethernet adapter and remove any driver and delete any
network connection found under Network (if it remains there).

2. The USB card you added sometime ago - pull for the testing.

3. Reboot the system and if you had deleted the drivers for the on-board
Ethernet port, reinstall them. If you don't know how, just open Device
Manger, right-click on the top most entry in the tree and select Scan for
hardware changes. Then it show show under Network Adapters in the tree. If
it has a red X, Enable it.

4. Right-click on that network adapter and select Update Driver Software and
it will either install the latest driver it has on your system or tell you
it has the latest driver. Since you can't access the internet yet it can't
look for a newer driver yet.

5. Make sure the cable you have going to your router is a known good one
and not an outdated cross-over cable. A cross-over cable can be used on
Ethernet equipment that can distinguish the cable pin out but I don't know
if your on-board port is capable. The cross-over cable would work with
newer equipment but *may* not work with your on-board port. So to say it
another way - go buy a new Ethernet cable so that possibility is taken out
of the equation.

6. Configure the on-board Ethernet port for DHCP. Be sure that if you have
disabled that port in any manner, turn it back on.

7. Plug in the new cable and connect it to the router and run the Diagnostic
by right-clicking on the network adapter and selecting Diagnose.

Lets stop there and see what the results are before going on. You are
getting to deep in the mud without first really establishing if you really
do have bad hardware, bad cable or a corrupted network driver.

Bob S.

On 2/28/2018 8:30 PM, Char Jackson wrote:
On Wed, 28 Feb 2018 18:59:36 -0800, cameo wrote:

Yes, the router is set to use DHCP within a certain range of IP
addresses. But because I use several IP cameras as well, I had to
reserve some stable IPs for them so I could use port forwarding to them
from outside calls.

You should make sure you reserved those camera IPs to addresses that
fall outside of the router's DHCP scope. Most SOHO NAT routers aren't
smart enough to check whether an address is already being used before
they hand it out to the PC that just made a DHCP request. The result
could well be an address conflict, which seriously affects both PCs.

I just tried it but it router refused it by saying that reservation must
be within the DHCP range.

Personally I don't see the rational of why I could
also not uses reserved IP for this GbE adapter. In any case I've tried
to use both reserved and unreserved IPs for it without any difference in
results.

No clue what that means. Are you saying you've been manually
(statically) configuring the IP address, network mask, and gateway
address on the new adapter?

What I meant was that reserving an IP address or letting the DHCP assign
the IP makes no difference.

If so, always use an IP address that falls
outside of the DHCP scope and isn't being used anywhere else on the LAN.
Use the exact same network mask, usually 255.255.255.0, on every PC on
the LAN. Lastly, configure the exact same gateway address on each PC,
which I think in your case is 192.168.1.1

I figure router does it automatically with DHCP. Am I wrong? Why is it I
never had any problem with my other devices before I tried to set up
this GbE adapter?

BTW this router's (D-Link DIR-825) DHCP allocates new IPs starting from
the highest available one in the pool that I set to 100 to 200 and
continues to lower available numbers,

So it doesn't sound as if the DHCP pool is exhausted. That's good to
know.

skipping the ones that are reserved for given MAC IDs.

Reserving IP addresses that lie within the DHCP scope is usually
considered to be a misconfiguration. That's certainly what I would call
it.

As I wrote before, the router only allows reservation of IP addresses
withing the DHCP scope. And I need the reservation for using port
forwarding to my Internet cams.

On 2/28/2018 7:23 PM, Char Jackson wrote:
On Mon, 26 Feb 2018 17:00:11 -0800, cameo wrote:

On 2/26/2018 1:35 AM, Paul wrote:
cameo wrote:
On 2/25/2018 9:02 PM, Paul wrote:
cameo wrote:
On 2/25/2018 6:34 PM, Paul wrote:
cameo wrote:



*From Command Prompt

*** ipconfig

can tell you about whether an address has been acquired.

Here it is with the WiFi turned on. As you see, the WiFi connection at
the bottom does have the Gateway IP, but the new USB adapter Local
Area Connection 3 does not.

Correct, and not only that, Local Area Connection 3 does not have a
*valid* IP address for your LAN. As Paul suggested, it has an APIPA
address, (169.254.x.x), which will not work to connect to the rest of
the PCs on your LAN and will not work to connect to your router and will
not work to connect to the Internet. (See Plugable8)

So how does one end up with an APIA address? That happens when the
adapter is configured to use DHCP but no DHCP server responds to this
PC's request for a DHCP assignment. When the DHCP request times out,
Windows autoconfigures its network adapter using APIPA.

Okay, so why is the WiFi connection not having that problem? I removed
all the devices and reservations and left only the WiFi and GbE
connections. That adapter still cannot connect to the Internet.
Should I manually set the gateway address for that adapter?

If the adapter returns the APIPA address, then it isn't making
contact with the DHCP server on the wired router. Or maybe for
some reason the DHCP server is using MAC filtering to deny
an address to the NIC ?

I doubt it if you look at this page of my router. It has two Notebook7
entries with different IPs. The 192.168.1.191 is the new USB3 adapter
and the 192.168.1.188 is the WiFi.

I may have missed the screenshot where the USB adapter had a valid IP,
but if it did then at that time your new adapter was working. It had a
valid LAN address and a valid gateway address. You would have been able
to use the new adapter to access the router, the Internet, and the rest
of the PCs on your LAN via the USB adapter.

Unfortunately it did not last long enough for me to make a screenshot
then. So you could not have seen it.

And it won't while this one PC is on an APIPA island. It, alone, has a
169.254.x.x IP address and nothing else on the LAN does, so it has no
one to talk to.

I have no clue how to make that APIPA address disappear.

The relevant section is already on that Plugable8.jpg. What else do you
need?

Plugable8 shows that DHCP failed. You can try to work around that by
configuring a static IP, network mask, and gateway, but I get the
feeling that you'll need more details on how to do that. Paul and others
have given tips, I believe.

I know how to set that up in the Internet Protocol Version4 (TCP/IPv4)
Properties sheet. Is that what you mean?

And this was supposed to be a simple Plug-and-Play setup ...

cameo wrote:


And this was supposed to be a simple Plug-and-Play setup ...

When the two radio buttons with the word "...automatically"
are selected here (the default case), it should be
a simple operation. But it assumes that the router you
plug into is properly configured. The router has to respond
properly, for the two Automatically radio buttons here, to
do the right things.

http://pedal.dcn.org/~help/images/wi...in8ipv4dyn.PNG

*******

When you connect two PCs directly to one another, with no
other network boxes in the picture, it's only natural for
that case to require manual configuration.

*******

You can "fake" the necessary responses - in other words, use
a separate PC to act as your router. Even if the PC has the one
port, it could be used to verify that a DHCP request from
your broken machine, actually works properly given a chance.

This is an example. I wouldn't say "Easy", but at least you
can see someone has thought about the problem.

http://www.instructables.com/id/Runn...-the-Easy-way/

If you could assign static addresses to a couple machines,
you could also use ping, or use some benchmarking software
to prove the ASIX product is robust. The software I wanted
to point you to, is no longer available, and also isn't
on Archive.org, so I can't really say any more about that one.
Dead end (pcausa ttcp).

Paul