I Have Ubuntu 9.10 Server installed and for some reason after updating our server with the ubuntu update manager, we can no longer connect to the network via remote desktop, let alone not even able to ping. We are actually able to connect to the internet itself just fine so I dont understand why this isn't working.

Thanks in advance!

Alex

Please post the output of the following commands (executed as root):

root@ucareserver:/home/ucareadmin# ifconfig
eth0 Link encap:Ethernet HWaddr f4:ce:46:80:06:4e
inet addr:135.59.98.16 Bcast:135.59.98.255 Mask:255.255.255.0
inet6 addr: fe80::f6ce:46ff:fe80:64e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:473692 errors:0 dropped:0 overruns:0 frame:0
TX packets:10344 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:39691508 (39.6 MB) TX bytes:1729603 (1.7 MB)
Memory:fbe60000-fbe80000

eth1 Link encap:Ethernet HWaddr f4:ce:46:80:06:4f
inet addr:135.59.98.16 Bcast:135.59.98.255 Mask:255.255.255.0
UP 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)
Memory:fbee0000-fbf00000

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

root@ucareserver:/home/ucareadmin# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
135.59.98.0 * 255.255.255.0 U 0 0 0 eth1
135.59.98.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth1
default vrrp-135-59-98- 0.0.0.0 UG 100 0 0 eth0
default vrrp-135-59-98- 0.0.0.0 UG 100 0 0 eth1


Edit: I also noticed for some reason i can't even ping my gateway address anymore (135.59.98.3)

Found the problem....

The issue wast hat the eth1 device was also configured with the same ip. took the eth1 interface down and it worked.