• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 227
  • Last Modified:

Connecting Windows clients to a Linux Server for Internet Access

I have set up RH9 as a network server.  I am able to ping a computer in the LAN, but the client can't access the Internet.  How do I configure linux and the client for the client to access the Internet? The Linux server does have Internet access.
0
bzinke2
Asked:
bzinke2
  • 3
  • 2
1 Solution
 
paullamhkgCommented:
1st ensure your RH have the internet access. and your RH have a fixed IP

than set your RH as a default gateway in your win client, should do, eg.

if your RH IP is 192.168.0.1

put this ip into your win client gateway setting will do.
0
 
bzinke2Author Commented:
I have tried that.  I get a DSL connection when I boot and it is dynamic.  The IP of my server is 10.0.0.1.  The DHCP table is working on my server as evidenced by pinging the client.  The client has 10.0.0.3.  When I configure the client for Internet connection, I put 10.0.0.3 in the IP address configuration window.  The subnet is 255.0.0.0 and the default gateway is  10.0.0.1.  Is this correct?
0
 
paullamhkgCommented:
yes, the client setting correct, but how abt the DNS, is the linux box also the DNS server? if not, try to use the DNS of your ISP.

come to the 1st question, can your linux box got the internet access? try ping some out side web site from your linux box, what's result you got?
0
 
bzinke2Author Commented:
I am using the DNS of my ISP.  I do not have the Linux box set up as a DNS.  The Linux has Internet. I am using it now to communicate with Expert Exchange.  I have set up my Linux as a router too.  The LAN communicates with Linux on eth1 and I have Internet connected through SBC on eth0.  Do I assign IP address 10.0.0.1 (the linux box) to the IP for the router or should the router have another IP such as 10.0.0.4?
0
 
paullamhkgCommented:
Oh that's is difference story, you set the router in your linux box and have 2 NIC right, 1 network for your external connection the other is for internal LAN, and you are routing between 2 NIC right, so the gateway IP should be the one for internal connection eth1.

 
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now