| Author | linuxbob |
| Date | 2004-08-26 15:25 |
| Posts: |  Quote: So are you saying that users cannot access the site if they use the following notation: http://172.xx.xx.xxx/opn/ 
Why would this be? I seem to be having the same problem. I have a small internal webserver I run, to serve in-house applications for our software implementation team. I'm running a SuSE box with Apache2, inside our firewall, on our internal network. I have other PHP/MySQL apps running and everyone gets to the site by using the IP address and the proper directory structure. It is doubtful I could get the network guys to add my box into the DNS, so my users have to use the IP address. Mine is the only Linux box in the mix, everyone else is using Windows and IE. My local /etc/hosts has the name translation, but that doesn't help the others. From the local machine it works via hostname, localhost, or IP address. From all other boxes it's just the login page over and over. Which module would I modify, or am I just out of luck? 
Bob |
