Unable to connect to website via Server's IP address

[Moses]

I am unable to connect to my website (IIS 5.0) via <server IP Address>\website. I am able to connect via <server name>\website.
Does anyone have any idea what settings or permissions might cause this? When I try to connect via IP address I get a web page that states "You are not authorized to view this web page"

Thanks

[diurnal]

Are you using a router? Also, make sure the directory where the website information is , is directed to the right location. TO make sure go to admistration tool/ IIS/ then click on the website folder, right click and hit properties.

Then click on the home directory tab, and make sure the website information is directed(Local Path) to the correct destination.

[Moses]

I have double checked all the paths, I am not using a router, I cannot figure this one out. I have gone through just about every IIS setting I can find and am still getting "you are unauthorized" when attempting to view the website via IP address.

[Moses]

Update...I have a pix available and so I tried putting the webserver on the inside of the pix. This isolated me from my companies house net. Once I did this I was able to connect to my webserver via IP Adress from the inside of the Pix only. It almost appears that the house net is impeeding my connection some how. I know the house net is run on an Active directory domain...does anyone know of any settings which might deny logon to an IIS server via ip address? Does this even sound reasonable?

[Ghost_Hacker]

...which might deny logon to an IIS server via ip address? ...


If your company uses Microsoft's ISA server, then YES it can be done. However, this would still work no matter how you tried to acccess the site. (as long as the ISA server is your only path to the internet and it is setup correctly)

[mjc]

a rules-based firewall can do it too......and it is frequently done to deny access to "undesireable" sites......

[Moses]

Here is the scenario: I'm setting up a web based application. Each app server has its own webserver and website which may or may not be exposed to the internet.

Server #1 sits behind a PIX firewall which is not exposed to the internet and is isolated from the Housenet that runs off of AD. I am able to connect to this server via IP Address from within the PIX but not from the outside. Outside connection gives "you are not authorized"

Server #2 sits on a completely isolated Windows NT 4.0 domain. It too can connect via ip address from within the isolated domain.

Server #3 sits on the house net which runs AD. I can connect via url but not IP address. Attempting to connect via ip address gives "you are not authorized" page.

All of the above coupled with the fact that this worked before our current network was merged with the network of the company which acquired ours suggests that problem came in with the new network.

Any ideas?

[Ghost_Hacker]

PIX can be setup to ask for user name and password, if you don't get a "box" asking for that information (and PIX is setup for it). Then your browser is sending cached authentication information. (this is not the same as cached passwords)


Which might also explain why the URL works but the IP doesn't. Can you give an example of the URL and IP combo? Also what browser are you using?