problem setting up ubuntu server 8.04

Kadafi · 1 Jul 2008 at 10:52

when i try to update the system im met with this error (its a lot longer as there is an error for each repo)

Err http://gb.archive.ubuntu.com hardy Release.9p9.gpg
Could not resolve .gb.archive.ubuntu.com.

Reading package lists... Done

W: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/...dy/Release.gpg
Could not resolve .gb.archive.ubuntu.com.

W: Some index files failed to download, they have been ignored, or old ones used instead.
W:You may want to run apt-get update to correct these problems

any ideas? it could be something to do with the DNS but im a bit of a noob at linux so im not sure what im doing.

Kadafi · 1 Jul 2008 at 14:55

yeah definitely something wrong, did a ping of google, nothing!

ifconfig /all didnt do anything, ifconfig came up with a load of details on network connection etc.

Kadafi · 1 Jul 2008 at 15:43

im connecting via ethernet to an smc router.

ifconfig reads

eth0
Link encap:Ethernet HWaddr 00:1d:7d:93:32:e9
inet addr:192.168.2.136 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::21d:7dff:fe93:32e9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:703 errors:0 dropped:0 overruns:0 frame:0
TX packets:786 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:52184 (50.9 KB) TX bytes:101218 (98.8 KB)
Interrupt:18 Base address:0xce00

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:1605 errors:0 dropped:0 overruns:0 frame:0
TX packets:1605 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7301 (7.1 KB) TX bytes:7301 (7.1 KB)

PING 192.168.2.137 (192.168.2.137) 56(84) bytes of data.

---192.168.2.137 ping statistics---
17packets transmitted, 0 received, 100% packet loss, time 15999ms

guess thats a no then, although i am connecting to the server using openssh...

Kadafi · 1 Jul 2008 at 17:51

Septh said:
You can connect fine cuz you can see the server but it can't see you, 192.168.2.137, what machine is that? the one your sshing from? or your router?

192.168.2.136 is the server
192.168.2.137 is my pc

Kadafi · 1 Jul 2008 at 18:53

static ip

Kadafi · 1 Jul 2008 at 19:13

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.2.136
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255
gateway 192.168.2.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 192.168.2.135 192.168.2.134 192.168.2.133
dns-search home

Kadafi · 1 Jul 2008 at 19:51

i havent changed the broadcast ip, its what was there from when i installed.

there is no error after

sudo /etc/init.d/networking restart

Kadafi · 1 Jul 2008 at 20:22

no i cant use a Static DHCP server, my router doesnt support it.

Kadafi · 2 Jul 2008 at 11:25

yup that solves it, but now i cant connect via ssh because the ip address changes.

Kadafi · 2 Jul 2008 at 13:38

ive just tried that and im greeted with this error

Unable to open connection to server1.home:
Name or service not known

Kadafi · 2 Jul 2008 at 15:26

bump

anyone?

Kadafi · 2 Jul 2008 at 17:00

it comes out server1.home

i tried just server1 in the ssh terminal but same error.