URGENT: dns resolving through gateway

I have a Linux pc running Ubuntu Hoary in my network.

I have problem to access internet from it.

This pc has static ip 192.168.0.3 and should connet to internet through a WinXp gateway at 192.168.0.4.

The Ubuntu box and the Gteway can ping each other. So i guess there's no network problem.
Moreover if i set up a working proxy in the Gateway a can access internet through it.

So i guess is a dns configuratin problem.

I post some config file might be useful:

--------/etc/netork/interfaces----------------
# The loopback network interface
auto lo
iface lo inet loopback

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
script grep
map eth0

# The primary network interface
iface eth0 inet static
address 192.168.0.3
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.4
# dns-* options are implemented by the resolvconf package, if installed
#dns-nameservers 192.168.0.4

auto eth0
------------------------------------------------------------

----------/etc/resolv.conf------------------------------
#these are tiscali dns server
nameserver 213.205.32.70
nameserver 213.205.36.70
-----------------------------------------------------------

i'd guess it was windows's fault, you would just get your machines gateway to be the windwos box and off you go.

and please do NOT meark threads as Urgent. it is NOT urgent for me, or any other member of this site who donates their time to help others.

I dont give a shit if it is not ugent for you.
It is for me.

If you dont have time bothering to reply, dont waste my time posting and go get some autosatifitation elseway.

And anyway i dont give a shit about your opinion on WinXp too. So dont waste my time posting just because you dont have anything else better to do.

If you have something more useful to say just say it or skip and please yourself.

Cheeeeeeeeeeeeers

After some work i got that ican't actually ping anythin outside the local network.
Even if i ping an ip directly, without any need for dns resolving.

I guess that that means that i haven't got a dns problem, but a proper routing problem on the gateway.

What's amazing is that the gateway allows the traffic from others boxes in the network to access internet. I even tried to shut down the zonealarm firewall but no effect whatsoever.
What the hell??

Be careful how to talk to moderators. I am just doing my job, and if you wish to remain a valid member of this site, you will be polite in future. Abuse will not be tolerated.

this may be out of the question but why dont you just buy a $40 linksys router from bestbuy and use that as your internet gateway like the other 90% of the world. i dont understand why people mess around with windows connection sharing when routers are cheap, fast, and secure.

to try and answer your question, is the linux box configured exactly like the other computers on your network? ip class, subnet, gateway, and dns settings? have you tried turning one of the other computers off and using that computer's ip address on the linux box? Norton internet security can filter traffic by IP, id imagine zone alarm can do the same. Try assigning an ip address from one of your working computers to your linux box, if that allows the linux box to see the internet then theres a configuration issue with your firewall. If that still doesnt work then its more than likely an issue with the network settings on your linux machine. once you isolate the issue to either your firewall or linux box, then we can troubleshoot further.

Edit- I had some ideas I was about to post. After reading the way this guy talks to the moderators and all the rest of us who volunteer our knowledge to this site I've decided he's barely worth posting this.

linksys routers secure??????????huh, they must have changed the default admin, admin user/passwd combo. not trying to be a smartass either, sorry.

Originally posted by Darin Edit- I had some ideas I was about to post. After reading the way this guy talks to the moderators and all the rest of us who volunteer our knowledge to this site I've decided he's barely worth posting this.

I agree. This poster's communication style has not been respectful to the wonderful contributors to this forum. But please don't let that hold you back from responding with your troubleshooting suggestions. Remember, your suggestion will hopefully be found by others in a similar predicament and they'll be able to benefit from your guidance.

I say this because I am grappling with a similar problem. I am running Mandrake 9.2 as a web / mail server behind a cheap-ass Netgear router. Have been using it for several years now. Unfortunately, I tried to renovate my network and now I'm not able to access the internet FROM the linux box. Oddly, I am able to connect TO the linux box from the outside internet and from other computers on the LAN. I changed around a bunch of stuff on the router, but nothing on the linux box. So, I do not suspect the problem is originating in how the Mandrake box is configured, but I now need to reconfigure it to be able to make outbound connections. It responds fine to web and mail inbound connections. It can also send email. What it can't do is ping, nslookup, or connect to the news-server. Any ideas? Here is the relevant info--

cat /etc/resolv.conf
nameserver 24.93.43.121
nameserver 24.93.44.119
nameserver 192.168.1.1
domain austin.rr.com

Destinaton 	Gateway 	Netmask 	Interface
192.168.1.0 	0.0.0.0 	255.255.255.0 	eth0
127.0.0.0 	0.0.0.0 	255.0.0.0 	lo
Default Route 	192.168.1.1 	0.0.0.0 	eth0

That 192.168.1.0 thing looks weird to me. The real router is at 192.168.1.1 Also wondering if that netmask should be 255.255.255.0 for the default router.

Any thoughts on this topic much appreciated.

di11rod

di11rod the 192.168.1.0 destitation is a network not a host - in other words it says any ip addresses starting with 192.168.1. can be found by using device eth0. The default route is also correct as it will match any destination on any subnet which has already been specified.

Try just changing your resolv.conf file to contain:
nameserver 192.168.1.1

SuperSadSmile, can you confirm that your routing table is set up correctly by posting:
route -n