Trouble connecting to ISP directly rather than through router

[isee]

Hello!

I've had my PC connected to my router since I installed Ubuntu. My router has the address and name password for my ISP. I'd like to plug my PC directly into my ISP line, but the network manager won't find the connection, and I don't know how to tell my PC my ISP's address and the name and password to logon with.

I set up my router, and I know how to make the connection in XP, but I don't know how to in Linux. I have very limited Terminal experience.

Thanks much!

[doas777]

well, have you tried shutting down both devices (just unplug the cable modem). then power the cable modem on, waiting a minute or two, and then booting the pc?

cable modems don't respond well when you unplug one device and plug another in, so somtimes a reboot is in order.

[isee]

No that didn't work. Thanks though.

When I boot everything up with my PC pluged into the ISP cable modem (bypassing my DLink), and I click on the NetworkManager Applet icon in my panel and select Auto eth0, the icon just spins, eventually telling me I am not connected. The cable modem detects my PC because the computer icon on its front panel goes off if I power my PC completely off and comes on again when I boot up.

Any help please?

[doas777]

No that didn't work. Thanks though.

When I boot everything up with my PC pluged into the ISP cable modem (bypassing my DLink), and I click on the NetworkManager Applet icon in my panel and select Auto eth0, the icon just spins, eventually telling me I am not connected. The cable modem detects my PC because the computer icon on its front panel goes off if I power my PC completely off and comes on again when I boot up.

Any help please?


well, to start off with, please post the output of these commands:


ifconfig
ping 4.2.2.1
cat /etc/resolv.conf
nslookup www.google.com
cat /etc/networking/interfaces
route

[isee]

Is this do be done while connected with my DLink or while connected to the cable modem?

[doas777]

Is this do be done while connected with my DLink or while connected to the cable modem?

well, your only having trouble when you connect directly to the modem, right?
so in that case, when you are connected directly.

[isee]

OK This may take a little while.

Thanks!

[doas777]

OK This may take a little while.

Thanks!

oh, with the ping command, it will keep running until you kill it with ctrl + C. sry shoudl have mentioned it or told you to use ping <ip> -c 2

[isee]

ifconfig
ping 4.2.2.1
cat /etc/resolv.conf
nslookup www.google.com (http://www.google.com/)
cat /etc/networking/interfaces
routeResults

ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:09:18:fc:d6
inet6 addr: fe80::211:9ff:fe18:fcd6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:468 (468.0 B)
Interrupt:18 Base address:0x6000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:36 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2592 (2.5 KB) TX bytes:2592 (2.5 KB)

ping 4.2.2.1
connect: Network is unreachable

cat /etc/resolv.conf
# Generated by NetworkManager

nslookup www.google.com (http://www.google.com)
;; connection timed out; no servers could be reached

cat /etc/networking/interfaces
cat: /etc/networking/interfaces: No such file or directory

route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

[doas777]

ok, so your problem is definitely DHCP then. we've ruled out routing and DNS.

try running this:


sudo dhclient


I'm no pro with dhcp (my network is mostly static, or otherwise problem-free), but there are a few regulars around here later in the day that can walk you through deeper dhcp troubleshooting.

[isee]

I do have the folders etc\network which contain a file called interfaces containing this:
auto lo
iface lo inet loopback

[isee]

sudo dhclientInternet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/pan0/0a:f1:67:fe:79:33
Sending on LPF/pan0/0a:f1:67:fe:79:33
Listening on LPF/eth0/00:11:09:18:fc:d6
Sending on LPF/eth0/00:11:09:18:fc:d6
Sending on Socket/fallback
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 6
DHCPREQUEST of 192.168.0.100 on eth0 to 255.255.255.255 port 67
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 6
DHCPREQUEST of 192.168.0.100 on eth0 to 255.255.255.255 port 67
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[doas777]

I do have the folders etc\network which contain a file called interfaces containing this:
auto lo
iface lo inet loopback
yeah, I sometimes get the service "networking" and the /etc/network folder confused. prolly dyslexia.

add this pair of lines to it:

auto eth0
iface eth0 inet dhcp and save. then restart networking with


sudo /etc/init.d/networking restart


your dhclient output indicates that it is broadcasting to find a server, but isn't getting a response from one.

[isee]

That didn't work either.

I used Nautilus to edit ect/network/interfaces to include those lines, then ran the networking restart command. It went through the same process as sudo dhclient, with the same results as posted above.

Then I had a scare when I rebooted and clicked on my NetworkManager icon in the panel and instead of being able to select Auto eth0, there was just greyed text saying "Device not Managed"

So I edited those lines out of /interfaces and rebooted and it's OK now.

[isee]

I figured it out!

Right click on the NetworkManager icon in panel ---> Edit Connections

Click DSL tab
+Add
Enter Username, Service, and Password.

I now have Auto eth0 and DSL connection 1 available, so I can switch between using my DLink or connecting directly.

Yay! =D>