Windows Forum

Ask something
Discussion Locked

Win2003 Outside IP not responding

0 helpful
5 replies

by swampdoc

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a 2003 enterprise server, AD, DC, with 2 NIC's in it (one internal and one public IP) that we have setup IIS and are trying to setup a website on it. When we brouse the internet, all is fine. When I try to ping the server from outside, nothing. When I try to ping an outside IP from the server, nothing. When I ping it with my latop setup on the public side of my network, works fine and can see the site. I changed the NIC, same. I changed the cable, nothing. When I changed the IP on my laptop to the public IP for the server, pings works. The server is not behind a firewall (till I get this resolved) and all ports are open (I know, hacker heaven). I need to get this site up for a customer. This seeems to be some strange setting in Win2k3 that keeps it from routing outside traffic. HELP!!!

5 replies

by cg it

ok the public NIC should be set to obtain an ip address and DNS automatically from your ISP service provider. your private NIC should be a static IP address with subnet mask and default gateway as your public NIC. DNS is your DNS server. If your running DHCP, configure the options for DNS, gateway [public NIC] WINS if you run it.

IIS default web site should be all unassigned IP addresses coming in over port 80 [if you run a proxy server later you'll have to change the port on the proxy server to something other than port 80, If you plan on a router, you'll have to foward port 80 inbound to your public NIC]]. when you create a web site, use use all unassigned ip address over port 80 AND then use host headers else you'll get the default web site.

LAN users use UNC to get to the web site e.g \\ or public users use HTTP:// . you'll need to setup with your Domain Name registrar what or who your authoritative DNS server will be. public users will not be able to find your site by name unless your domain name registrar has associated an authoritative name server for your domain name which will provide name resolution.

to verify your web site is up and running from within your LAN, you'll need an ISP that is not your normal ISP like AOL or Earthlink where connect to them, use their network to find your network. pinging yourself via your public address may not work. the loopback address of 127.0.0.1 is yourself, you public ip is your public nic. to verify connectivity on the public NIC, use ipconfig /all from a cmd prompt. you should see your public ip address DNS DHCP . then ping your ISP DNS server or DHCP server. IF you dont see any ip address information for your public nic or a 169.xxx.xxx.xxx ip address and you dont receive a reply if you try pinging your ISP DNS/DHCP servers then you have a connectivity problem.

by rindi1

Check the server itself. Either you have set up some Firewall rules under control Panel/ Network and the network cards, or under Routing and Remote Access Services. Maybe your blocking the icmp protocol or whatever on one your interfaces

This discussion is closed to new replies.