Windows Forum

Ask something
Discussion Locked

gate way configuration

0 helpful
13 replies

by avswamy

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

i am having a problem on configuring gate way to my domain controller, which i am using for authentication and for browing the internet. My conflict is i am not able to connect to internet from my server and my clients also, i am asuming that the conflict is gateway ipaddress problem.

here i am giving how i configured my server

NICS 2 NOS.
ONE NIC IS CONFIGURED AS PUBLIC IP ADDRESS
ANOTHER NIC IS CONFIGURED AS PRIVATE IP ADDRESS

and my connectivity bandwidth from isp is through radio link modems, which is connected to a router at isp end, at my end there is no router and from radio link modem to a switch.

i have configured gateway as ipaddress of router at isp end, is it the problem for not browsing the internet from my server and my clients.

and i am able to connected remotely by ts.

13 replies

by dmccull2000

There are a couple of problems,one is the gateway. On your internal network the gateway would be the internal card that is on the server. On the external card on the server, the gateway would be the ISP router.

You also need to set up Routing andremote Access. There are two ways you can set easy. One is Internet Connection Sharing (ICS)and the other is setting up a routing and remote access server (RRAS) with Network Address Translation (NAT).

There is a nice work up on it on:
http://www.microsoft.com/SERVICEPROVIDERS/columns/windows_2000_home_office_gateway.asp

Otherwise you can setup your Windows 2000 server as a router in admin tools, routing and remote access. Just make sure your internal computers use the gateway of the internal NIC address.

Good Luck, I hope this helps

by dmccull2000

Just a quick comment on your situation... Answer three has some good ideas, but if you have your isp use dhcp to give your external NIC an address you will have problems using terminal server to connect to your server due to IP address always changing... The best solution that I see is to set up your Wil 2000 server as a router, then you do not have to purchase a router... Just go to routing and remote access in admin tools. Right click on your server and select enable routing and remote access. After that select network router and fill in the info. Right now your server may have NIC cards, but it does not know that it is supposed to act like a router. One you do this, it will act like a router and route info back and forth. Then set yourgateway on all internal computers to the internal NIC card on your server.
Good Luck!

by courtney

I agree with the last statement, but setting up RRAS will only help the users on the other side. If you have your external NIC setup with the right IP information and you cannot get to the internet then RRAS wont help your clients. If you cannot gain access on the server with the Ext. NIC try pinging the ISP gateway to make sure you can get to your ISP

Start, Run, type CMD, press enter
type ping x.x.x.x at the C:\
x= is the IP of the ISP gateway.

If you can get to your ISP's gateway then try to get past it.

I hope this helps.

by avswamy

i have given that i am able to connect my server from outside, ie., from dial up to another isp and getting into my server through ts, so there is question of pinging to gate, if there is connection created then i am not able to connect remotely to my server

by avswamy

i am able to ping to gate way(isp router), and connecting to my server through dial up to another isp and connecting to my server by terminal server.

why i should configure gateway as isp router, why i should not configure gateway as my radio link modem(which is also having ip addresses at both end)

by bazz00

The ip address for the internal nic on the server is the gateway for the client computers.

Is there anything else besides the modem connected to the switch? If no, why not connect the modem directly to the external nic on the server and apply a firewall to that nic. Set the nic to obtain an ip address automatically through DHCP from the ISP. This would set up the internet connection for the server fairly easily. Then the server would route traffic to the external nic and out to the ISP.
You can intitiate ICS on the server which would set up NAT and automatically route any internet traffic from the clients on a private addressing scheme out through the external nic on the server. By doing this ICS will do the setting up for you via a wizard. But make sure that the server is connected to the internet and that you have connectivity from the server to the rest of the LAN. Do NOT apply File & Printer sharing on the external nic or client for microsoft networks. Only do this on the internal nic pointing to the Lan.

Remember that by sending and receiving all this internet traffic through the server you can create quite a strain on the nics attached to it. So to be safe purchase two fairly expensive nics to ensure quality and reliabilty, 3com etc.

Another way would be to purchase a decent router with firewall capabilities and connect the modem to it. Then connect the switch to the router via the ethernet port and connect the server and clients to the switch. Then the gateway for the clients and the server would be the ethernet port on the router that the switch is connected to. This would not require any extra burden on the server due to acting as a gateway for internet traffic for the clients.

by mcarswell

Leave the gateway on the internal server blank. This will force All request to the internet to be sent thru the external nic. If you use RRAS this should solve your problem

by avswamy

when i configured dns server as another dns server (which is another dns server linux server) i am able to connect to internet, if i configured in clients as this linux server my clients are also connecting to internet.
is there any configuration is needed in router to configure dns server as a windows server, or only configuration problem in windows.

by avswamy

i solved the problem at server end, why i got the problem at server is i have not configured external dns address for public nic. i only configured for private nic, internal dns i.e.,why i can connect my clients to my server for authentication.

what happend in my case, dns name resolution in my private domain is resolved by my dns in server.
as for external(internet dns)name resolutions can't be solved by my dns, it should be connected to external dns then only connected to internet.

nowi configured nat, but still my clients are not able to connect to internet.

This discussion is closed to new replies.