New IT forum Follow us on Twitter
22 May 2012, 09:18:43 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: TonidoPlug2 - Now in stock!
 
   Home   SHOP Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Cannot connect to network  (Read 482 times)
bigoten
Newbie
*
Posts: 3


« on: 11 November 2011, 01:26:57 pm »

Hi,
first of all I am not very technical with PCs, so I appreciate all the detailed help that I can get  Smiley

I just received home the SheevaPlug that I bought this week. It is an eSata Multi Boot with a 16Gb SD card, Ubuntu 09.04.
I managed to connect and start the plug via USB using my laptop running Ubuntu 11.10. So this part works fine.

The problem is that I cannot connect with the network. I am using the ethernet cable that was shipped with the plug to connect it directly to the router. But for some reason the plug does not seem to realize it (ping www.google.com does not respond, for example). The leds on the plug are blue and red, which I suspect is not how it should be.

I tried to find threads in this forum over this problem. I found one which did not help me:
http://www.newit.co.uk/forum/index.php?topic=2076.0

Another site explained how to solve this problem: http://shankserver.org/2010/08/getting-sheevaplug-onto-the-network/. This did not work for me because when I run "dhclient" I end up with the error "No DHCPOFFERS received".

I also read the thread for beginners on this forum (http://www.newit.co.uk/forum/index.php/topic,44.0.html), hoping that it would teach me how to do it. Unfortunately it did not work.
Can someone please show me step-by-step how this is done?

Thank you in advance,
bigoten

Logged
NewIT_James
Administrator
Sr. Member
*****
Posts: 394


« Reply #1 on: 11 November 2011, 01:42:17 pm »

Hi bigoten,

Assuming you do have a dhcp server on your network try,

Code:
dhclient eth0

Logged

NewITJames
bigoten
Newbie
*
Posts: 3


« Reply #2 on: 11 November 2011, 01:53:32 pm »

Hi James,
thank you for replying so quickly.

Executing "dhclient eth0" gave me this:

Code:
root@ubuntu:~# dhclient eth0
There is already a pid file /var/run/dhclient.pid with pid 1692
killed old client process, removed PID file
Internet 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/eth0/f0:ad:4e:00:a6:b6
Sending on   LPF/eth0/f0:ad:4e:00:a6:b6
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
Logged
NewIT_James
Administrator
Sr. Member
*****
Posts: 394


« Reply #3 on: 11 November 2011, 01:59:57 pm »


Do you have another ethernet cable to try just to rule out a dodgy cable?

Do the the Network device on your network use fixed ip addresses?

If you are using Fixed ip addresses here is a post to help you configure the plug.

http://www.newit.co.uk/forum/index.php/topic,45.0.html
Logged

NewITJames
bigoten
Newbie
*
Posts: 3


« Reply #4 on: 11 November 2011, 02:08:02 pm »

Quote
Do you have another ethernet cable to try just to rule out a dodgy cable?
Well, I think you just found the problem. Now the terminal output is:

Code:
root@ubuntu:~# dhclient eth0
There is already a pid file /var/run/dhclient.pid with pid 1751
killed old client process, removed PID file
Internet 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/eth0/f0:ad:4e:00:a6:b6
Sending on   LPF/eth0/f0:ad:4e:00:a6:b6
Sending on   Socket/fallback
DHCPREQUEST of 192.168.1.10 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.10 from 192.168.1.1
bound to 192.168.1.10 -- renewal in 41369 seconds.

And I can ping.
Thank you for your help. It is unfortunate that the shipped ethernet cable is faulty, but it's not the end of the world.
 Smiley
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.16 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!