USB to Ethernet Switchover

[BillyTheKid1974@googlemail.com]

I have just changed my connection to my cable modem from USB to
Ethernet. I have managed to get the connection working OK but I have
found that certain web sites which were accessible whilst connected
via USB are no longer accessible whilst connected via Ethernet. Can
anyone outh there shed any light on why this would be tha case ?

[Tom Stiller]

In article <1189783444.275441.279960@y42g2000hsy.googlegroups.com>,
BillyTheKid1974@googlemail.com wrote:

> I have just changed my connection to my cable modem from USB to
> Ethernet. I have managed to get the connection working OK but I have
> found that certain web sites which were accessible whilst connected
> via USB are no longer accessible whilst connected via Ethernet. Can
> anyone outh there shed any light on why this would be tha case ?

Presumably you had to modify the active network interface and, possibly,
Network Port Configurations. Check to be sure that the TCP/IP
parameters of the Ethernet adapter are correct, paying special attention
to the settings for DNS.

--
Tom Stiller

PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3 7BDA 71ED 6496 99C0 C7CF

[Bit Twister]

On Fri, 14 Sep 2007 08:24:04 -0700, BillyTheKid1974@googlemail.com wrote:
> I have just changed my connection to my cable modem from USB to
> Ethernet. I have managed to get the connection working OK but I have
> found that certain web sites which were accessible whilst connected
> via USB are no longer accessible whilst connected via Ethernet. Can
> anyone outh there shed any light on why this would be tha case ?

Type of connection eth/usb should not matter except ethernet should be
faster. Maybe different rules in your firewall. I assume you have the
same DNS values in ethernet as usb.

I had a wierd one where I could not connect to mozilla.com. It would
time out but was not having problems with any other sites. Change
from Verizon internal DNS to public DNS servers fixed the problem.

After me and the HelpDesk played around we could not figure out what
was wrong.

So, he pushed a new DHCP lease, I power booted everything, again,
and it worked. I wound up on a new segment using the same old DNS
servers and mozilla.com started working.