I have redhat 7 running which I would like to have connected to the internet. The station is connected to a local network using the 192.168.0.xxx range of adresses with a subnet mask 255.255.255.0

The modem has its own ip: 192.168.0.1

The linux station has the ip 192.168.0.200
with the mask 255.255.255.0
and the default gateway 192.168.0.1

Configured hosts:
127.0.0.1 localhost.localdomain

Primary DNS: 192.168.0.10 (this is the network server which also serves as a DNS address)

I can ping all computers on the network, I can ping the modem but when I try to surf the net nothing works. Is it just something I need to configure in Mozilla??

First of all, lets see if we can straight things out. A device that has an IP address is either a host ( your system ) or a router, the thing you are calling Modem. Modems modulate and demodulate, they don't route and have IP addresses.

I would bet you have a dual purpose machine, modem/router. This is common these days. The modem part just adapts to the media you have, ADSL or Cable.

You should be able to point your web browser at it, type the IP addess in the location bar, press enter, and get to it. Try the gateway address. Most are password protected, and all too many people never change the default factory password. Great for people wanting to use your service for free, or hack your network.

The ISP side of your router will have a IP address assigned by your ISP, most, but not all ISP's use DHCP to assign an address. The rest require you to configure in the ISP side IP address.

An address on 192.168.xxx.xxx is a private address, and gets translated in your router. Don't worry about that, it will work unless the router is broken.

It sounds like you assigned the IP address to your linux system. Is that correct? If yes, you need to look at the router config to see what range of addresses it is configured for, and make sure you are part of the same sub-net. If you are not, then the router will not route your packetts. The masks look good, that is a standard class C mask.

The primary DNS IP address doesn't look right to me. Most routers will aquire the DNS addresses from the ISP, and pass them to the systems using the router using DHCP. If you assigned the IP, you need to find out the correct DNS address from the ISP, or your router. Mine displays the DNS addresses. Once again, look at your router config to wee what you can find out your self. Ask your ISP if you can not see the info in your router.

Valid addresses for the internet will not be private IP addresses such as 192.168.xxx.xxx. Your side is a private network and an address of 192.168.xxx.xxx there is O.K.

You will have a resolv.conf file some where on your system, usually in /etc directory, or it may be a sim link to the real resolv.conf file. Have a look at it and see what addresses are in it. As an example only, here is mine.

/sbin/ifconfig in mine shows:

Note the IP address, I'm running DHCP, my router assigns the address. The third field is the sub-net. In my case it is 1, yours is 0. That is OK as long as it matches your router config.

Have a look at things, and post pack what you can discover. It helps if you post as much info as you can gather, such as your /etc/resolv.conf file, /etc/hosts file and the output of /sbin/ifonfig.

Hope this helps.

The modem acts as a gateway and has been assigned an ip address. All computers on the network are connected to a hub and use the modem's ip (192.168.0.1) as the default gateway. We have a DNS on the network which we use ip: 192.168.0.10
The internet provider's DNS ip is 216.252.64.75

Simply putting this information in the network config utility simply doesn't work.
Here is my resolv.conf file:

nameserver 192.168.0.10
nameserver 216.252.64.75 (which i can't even ping but i still put it there)

ifconfig
eth0 Link encap:Ethernet HWaddr 00:40:33:5A:69:F1
inet addr:192.168.0.200 Bcast:192.168.0.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:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:966 (966.0 b)
Interrupt:9 Base address:0xe800

I think the problem has to do with the nameserver 192.168.0.10. It is the first nameserver your work station would go to to resolve a name to IP address. The only way I can see for you to work this out would be to find out what your name server does if it can not resolve a name. What other servers does it go to? Or does it just return a host not found message to the requestor? Most private servers are set up to resolve internal ( comapny wide ) names, and not resolve the public side. You will probably have to talk to who ever configured the private DNS server.

It would be interesting if you could remove the 192.168.0.10 address and try your work station, with just the ISP's name server. I wouldn't get too excited about not being able to ping it. You can configure a device not to respond to pings. This is often done on busy servers to cut down on unnecessary traffic.

Point of interest, I can ping 216.252.64.75 , 'm connected to the public internet. So the server does respond to a ping. That would lead me to believe your station is not getting routed to the internet.

I think it is time to also look into the router configuration; as stated above.

216.252.64.75 has dns1.enter-net.com as fully qualified dns name. And indeed, the DNS server is running on that host. You should be able to ping this IP from your home network. If not, the router is the problem. Can you post the output of