Results 1 to 10 of 18
Hi,
I just got Debian with XFCE installed on my ipaq desktop.
I have it plugged directly into my wireless routed, so it has a ethernet hook up wired. I ...
- 11-02-2011 #1
Connection failed: unable to get IP address
Hi,
I just got Debian with XFCE installed on my ipaq desktop.
I have it plugged directly into my wireless routed, so it has a ethernet hook up wired. I went to the network manager and tried to connect to the internet.
It just keeps giving me "connection failed: unable to get IP address" and I can't seem to find out why.
Any ideas? I googled it and couldn't find much, will try again.
- 11-02-2011 #2Guest
- Join Date
- Feb 2005
- Posts
- 314
Post outputs
Code:ifconfig -a
Code:cat /etc/network/interfaces
- 11-02-2011 #3Linux Guru
- Join Date
- May 2011
- Posts
- 1,813
and
Also, on your router, have you confirmed that it is configured to be a DHCP server? That is what gives clients (like your Debian box) an IP address, assuming it asks for one.Code:route -n
Did you plug your CAT-5 cable into the right port on the router?
Do you see link lights (on the router and on the NIC on the ipaq)?
- 11-02-2011 #4
Hi,
I don't know how to put in that code, it gave me an error. Will try again.
Here is some stats I got using netstat command:
Ip:
58 total packets received
0 forwarded
0 incoming packets discarded
58 incoming packets delivered
58 request sent out
Icmp:
10 TCMP messages received
0 input ICMP message failed
ICMP input histogram:
destination unreachable: 10
10 icmp messages sent
0 icmp messages failed
icmp output histogram:
destination unreachable: 10
icmpMsg:
Intype3:10
outtype3: 10
tcp:
3 active connections openings
3 passive connections openings
0 failed connection attempts
0 connection resets received
0 connections established
30 segments received
30 segments send out
0 segments retransmitted
0 bad segments received
0 resets sent
udp:
8 packets received
10 packets to unknown port received
0 packet receive errors
18 packets sent
udplite:
tcpext:
3 tcp sockets finished time wait in fast timer
0 packet headers predicted
9 acknowledgements not containing data payload received
3 predicted acknowledgements
ipext:
in0ctets: 3956
out0ctets: 3956
I have my charter modem plugged into my netgear wireless router. It supports 4 computers to be hooked up through cables, so I plugged it in directly to the netgear modem. It now has all 4 sockets filled up.
The router shows the computer button lit up for this computer, and the cable is lit up in the back of the computer in the plug in.
I will go over the netgear router set up again online and see if I can find anything dealing with dhcp. I couldn't find anything on it last time.
Oh, and help with the code you two posted would be appreciated
I only know the sudo commands pretty much 
EDIT:
ON the first router page it says dhcp. And then in the router setup it says under internet port dhcpclient. And it has dhcp turned on. other then that it doesnt say anything else about dhcp
on the online info sheet it says this router is auto set up as a dhcp serverLast edited by jreidsma; 11-02-2011 at 07:54 PM.
- 11-02-2011 #5Linux Guru
- Join Date
- May 2011
- Posts
- 1,813
I guess you need to run the commands via sudo, or su to root first, e.g.:
orCode:sudo ifconfig -a
What is the model number of your netgear router? We can look it up online and follow along with you.Code:su - ifconfig -a
- 11-02-2011 #6
My router is a netgear wnr2000v2
I am reinstalling debian right now, it is giving me this error message:
Network autoconfiguration failed
you network is probably not using the dhcp protocol. Alternatively, the dhcp server may be slow or some network hardware is not working properly.
My router is fully updated and is working fine though.
I will run the code once debian finishes installing again.
- 11-02-2011 #7
Here's what I got from running the command ifconfig
eth0 Link encap:Ethernet HWaddr 00:d0:b7:e5:81:7c
inet addr:192.168.1.8 Bcast:192.168.1.255 Mask:255.255.255.0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
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:38 errors:0 dropped:0 overruns:0 frame:0
TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2636 (2.5 KiB) TX bytes:2636 (2.5 KiB)
- 11-03-2011 #8Linux Guru
- Join Date
- May 2011
- Posts
- 1,813
ok, so you're not getting an ip address, that much is clear.
Try to acquire one:
orCode:sudo dhclient eth0
then run the ifconfig command againCode:su - dhclient eth0
- 11-03-2011 #9
- 11-03-2011 #10Linux Guru
- Join Date
- May 2011
- Posts
- 1,813
oh, snap...
yes, there it is. so what does route -n say? (sudo route -n, su -;route -n, etc.)
EDIT: and do 'cat /etc/resolv.conf' for that matterLast edited by atreyu; 11-03-2011 at 03:50 PM. Reason: dns


Reply With Quote

