Website on Network only accessible through its own server (with internal '192' ip)

[austin2359]

First of this is an IIS setup, not apache.

My problem is that a website is set up in Windows 2003 over a network. Of course it works using localhost, 127.0.0.1. From the same pc it can also be accessed with an internal ip, 192.168.xxx.xxx.

You would think that because it has an internal IP associated that on a client computer you could still access it using the 192 ip, but you cannot, it just blanks out.

Web searching has lead me to recommendations to alter firewall settings, which could be interfering, but when I start the firewall, I get this error:

windows firewall cannot run because another program or service is running that might use the network address translation component (Ipnat.sys)

Searching the internet tells me to disable the 'Routing and Remote Access' service then to configure the firewall. This does not work either. The same error appears even with the service disabled.

What are your recommendations to make the internal ip accessible on the internal workstations without remoting into the server?

I am relatively new to IIS and may have overlooked something there.

 

[JackMDS]

Open the port used by IIs (default is usually 80) through the Server Firewall. Forward the port i the Router (if your network is connected through it) toward the IP of the server.

http://www.windowsecurity.com/artic...iguration-Wizard-Windows-Server-2003-SP1.html

Router - http://portforward.com/

 

[hextet]

I don't think its a firewall, nor is it a port issue on the Server it's self as you can access it using the 192.x.x.x IP Address. This leads me to believe you haven't configured port forwarding on your router properly. You'll want to configure it to forward TCP port 80 and 443 to the PC that's hosting the IIS server. Also make sure the IIS server is using a static IP address, and make a reservation for that IP on your router providing it is running DHCP.

 

[debian0001]

Telnet to port 80 from a desktop computer to the server and see if that works.

Telnet 192.168.xxx.xxx 80.

Check if IIS is limited to only localhost accessing the site.

 

[VirtualLarry]

I don't think its a firewall, nor is it a port issue on the Server it's self as you can access it using the 192.x.x.x IP Address. This leads me to believe you haven't configured port forwarding on your router properly. You'll want to configure it to forward TCP port 80 and 443 to the PC that's hosting the IIS server. Also make sure the IIS server is using a static IP address, and make a reservation for that IP on your router providing it is running DHCP.

From OP's description, I think he wants to share the web site on an intranet, not open it up to the internet-at-large. If that were the case, then yes, your instructions are sound.

 

[hextet]

Oh I see well than I misread the post! OP I'm guessing you are running the Server on a virtualized windows server box? If this is the case you should set it's network mode to "bridge" I believe it is, which gets the local DHCP server to lease out an IP to it just as if it were functioning your LAN as it's own seperate computer. I believe you are using a network configuration like host-only, or something like that which only allows it to be accessed by the host its self. My names of the network modes may be off, I don't have a virtualizer that I can access at the moment.