Hi Yall,
This is a copy of a thread I've got on the Ubuntu forum. I haven't had any replies so I thought I would try the Network forum instead. In hindsight it looks more likely to be a network issue than a Ubuntu specific one. Anyway.... Here goes.

Hi Folks,
This may be a network issue or it may be something particular to Ubuntu. Any help would be gratefully received.
I've got two PC's both running Ubuntu 6.06. The second PC connects to the internet through the first one i.e. I don't have a router (yet). Firestarter is istalled on the first PC and is set up to allow the second PC through and onto the internet (I'm typing this message from the second PC). I can go and get my Email on the second PC and browse the web OK. However when I try to get updates from the internet via the update manager I get the following errors.

W: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/...untu7_i386.deb
Could not connect to 192.168.0.1:80 (192.168.0.1). - connect (111 Connection refused).

the IP address of the first PC is 192.168.0.1 and the IP address of the second PC is 192.168.0.10.

In firefox's connection settings, if I select manual proxy configuration and then use 192.168.0.1 and port 80 (for all protocols) I get the following error:-

The proxy server is refusing connections
Firefox is configured to use a proxy server that is refusing connections.

But if instead I select Auto detect proxy settings for this network, I am allowed though. If after selecting auto detect I then go to the about:config page, it looks like I'm connected to 192.168.0.1 port 80.

If I try to ping 192.168.0.1 I get the following:-

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

--- 192.168.0.1 ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6009ms



If I go route at a console I get:-

192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
default nathansroom 0.0.0.0 UG 0 0 0 eth0

So I guess this is a proxy problem but I'm fully stuck. I'd be grateful for any help.

Cheers,

Mick.

You might try to disable the firewall prior to connecting to updates to rule that out as a possible blockage. Is the connection using UDP and do you have that filtered out?

Hi usaf_sp,
Thanks for the reply. I think there's something a bit deeper going on here. I've tried stopping the firewall (firestarter) and then checking for updates. I still get the same error message. Also, I've forwarded all the ports I can think are necessary to the second machines IP address (192.168.0.10) and this has made no difference. Another weird thing is that the update manager must be able to connect one way or another because it flashes up a balloon saying there are updates available. It just that when I say Okay go and get them that it fails. It seems to use one method for connecting to the internet in order to check for updates but a different method in order to actually get them. Does anyone know what port the update manager uses when getting updates??
As before, any help is gratefully accepted.

Cheers,

Mick.