Server is attached to router, client is attached to server via internal nic - how to gain internet access for client?

[PeeluckyDuckee]

Here's the situation:

I have a Linksys 4-port Router/Switch. The Server machine is hooked up to one of the ports on the router. The server has another internal nic attaching the client machine (W2K Pro). The server is running W2K Server AD Domain. The client only has one network card. DNS is running on the server.

Here's info on the wireless WiLinx nic on the server that's attached to the Linksys router:
IP address - 192.168.1.2
Net Mask - 255.255.255.0
DG - 192.168.1.1 <-- (IP of the Linksys Router)
DNS #1 - 205.200.16.65 (ISP's DNS)
DNS #2 - 205.200.16.69 (ISP's DNS)

Here's info on the other USB Linksys 10/100 nic on the server that's attached to the client machine:
IP address - 192.168.1.9
Net Mask - 255.255.255.0
DG - 192.168.1.2 <--(points to the WiLinx, is this correct?)
DNS - 192.168.1.2
DNS - 205.200.16.65 (ISP's DNS)

And here's the nic on the client machine:
IP address - 192.168.1.10
Net Mask - 255.255.255.0
DG - 192.168.1.9 <-- (points to the USB internal nic on the server, correct?)
DNS - 192.168.1.2

The client is using an internal private IP, no DHCP server is in use. When I try to ping 192.168.1.2 it fails, but 192.168.1.9 goes thru just fine. Do I need to set up some sort of a static route to 192.168.1.2? Cause the client can't seem to see that nic. Also, because of that, it may also be the reason the client machine cannot get onto the internet? Or do I need to setup a network router on the server using Routing and Remote Access?

Please lend a hand if you can, thx, appreciate it.

Plucky

 

[PeeluckyDuckee]

^

 

[lowtech1]

Server attach to Router.
Client workstation attach to Router.
DNS & Active Directory set on the Domain controler.
Client machine DNS can be set to the Domain controler, Router, or ISP provider DNS.

 

[lowtech1]

Server attach to Router.
Client workstation attach to Router.
DNS & Active Directory set on the Domain controler.
Client machine DNS can be set to the Domain controler, Router, or ISP provider DNS.

 

[PeeluckyDuckee]

I do not wish to attach the client workstation to the router directly. I want all clients to go thru the server first.

 

[Mota331]

I would suggest that you just setup a Proxy Server, from what I can tell that is what you are trying to do right. If you want to just download AnalogX's Proxy Program, it does everything for you.

 

[ivwshane]

Set router to static IP and the server to static IP(if you have already done some of these just ignore and go to the next step)
On the server, it's dns server should point to itself
the default gateway should be the router's static IP and yours isp's DNS server's IP should be in the forwarders box in the forward lookup zone.
If you aren't using DHCP then the clients should also be set to static and default gateway should be router.





Here's what I do with my setup;

static router IP
Server set to static IP running AD, DNS, and DHCP. Default gateway is router IP, my ISP's DNS server's IP's set in forward lookup zones under forwarders.
client's all go into router
clients have dynamic IP's

 

[PeeluckyDuckee]

OK, so on the server's DNS server I remove the "." root and configure DNS to use both the primary and secondary external ISP DNS servers as my forwarders? And set the client to use the router as the gateway? What about for DNS? Should the clients point to the ISP's DNS servers or my own DNS server? I'm thinking it would be my own DNS server since there would be forwarding capabilities??

The thing is I can't even ping the external nic (192.168.1.2) on the server using the client machine, but I can ping the server's internal nic (192.168.1.9) that the client is directly attached to. Do I need to set up some sort of RIP routing or static route?

I'm also playing around with MS ISA Server 2000, so I want to attach all the client machines behind the server so I can do some testing of configurations. If I attach the client to the router directly, won't that bypass any restrictions that I set on it?

Thx for the help fellas,
Plucky

 

[ivwshane]

<< OK, so on the server's DNS server I remove the "." root and configure DNS to use both the primary and secondary external ISP DNS servers as my forwarders? And set the client to use the router as the gateway? What about for DNS? Should the clients point to the ISP's DNS servers or my own DNS server? I'm thinking it would be my own DNS server since there would be forwarding capabilities?? >>


Yes



<< The thing is I can't even ping the external nic (192.168.1.2) on the server using the client machine, but I can ping the server's internal nic (192.168.1.9) that the client is directly attached to. Do I need to set up some sort of RIP routing or static route? >>



I'm not sure why it can't see it but how would it see it if there is nothing to tell the clients it's there? As far as using rip or a static route, I don't know.



<< I'm also playing around with MS ISA Server 2000, so I want to attach all the client machines behind the server so I can do some testing of configurations. If I attach the client to the router directly, won't that bypass any restrictions that I set on it? >>



I would imagine that if you have all the clients pointed to the server all the router will do is redirect it to the server first anyway.

 

[TheCorm]

Heres how we have ours setup:

All machines including our comms PC & server plug into a patch panel which plugs into a 100mbps switch. Our WAN router (which is also a firewall / ADSL Modem) is plugged into them in the same method.

We have DHCP enabled but no DNS setup on the server, the server points to our WAN router as a gateway, Our local machines have no internet connection settings but the Local area connection TCP/IP points the DNS to the WAN router which deals with that and uses the ISP DNS server.

Corm

 

[Woodchuck2000]

Silly question perhaps, but <why> don't you want to connect the client machine straight to the Router? It would make far more sense than trying to set up a proxy...

Anyway. Your client machine should not be able to ping 192.168.1.2 - It's on a separate physical network, and unless you bridge your connections (which would effectively plug your client into the router anyway so dont) you will never be able to ping it.

DG - 192.168.1.2 <--(points to the WiLinx, is this correct?)
Not as such. Since there's no connection between the cards, packets will never be able to travel to that IP address.

DNS - 205.200.16.65 (ISP's DNS)
Same thing - You won't be able to access the IP.

If all you want is internet access, then set up a proxy server. Someone mentioned AnalogueX - This is a free, fast, easy-to-configure solution, and I would recommend it if all you want to do is surf on the client.

You could use a more advanced solution such as NAT (I have nat running on my home network - 2K server connected to Cable Modem, 5 clients getting transparent internet access - it needs none of the messing around mapping ports and configuring proxy settings) but that is less secure, and I'm assuming that the reason you dont want to plug into the router is a security issue.

good luck anyway.