Koozali.org: home of the SME Server

No Internal Web Site Access

jfabate

No Internal Web Site Access
« on: April 27, 2005, 12:28:16 AM »
Why would a web site be unreachable from within my LAN but accessible from the internet?

I moved my web site from a commercial provider to an internal SME server configured as Server-Only several days ago. I set up my DSL modem/router with the appropriate pinholes to allow internet access on port 80. I can reach the site from the internet, but not from within my own organization. The only way I can reach it internally is to go to http://mywebserver and it comes up fine. I can ping the domain name and it responds with my IP. I get a good ping, whether inside or outside. I even used http://<myIPaddress/index.html to no avail.

I have another installation elsewhere and I do not have this problem there.

I appreciate any help you can give me.

Thanks,
John

Offline jackl

  • ****
  • 136
  • +0/-0
No Internal Web Site Access
« Reply #1 on: April 27, 2005, 02:29:09 AM »
John,

In server-manager check hostnames and addresses and see if the location of www.yourdomain.com is set to remote. If it is, which is likely since your website was external, set it to local and add the internal address of your webserver and should work fine.

Regards
Jack
......

jfabate

No Internal Web Site Access
« Reply #2 on: April 27, 2005, 02:43:36 AM »
In Server Manager, my site is set to global visibility and the location is set to self, meaning on the SME machine. Are you saying that the visibility should be set to local vs global? If so, how does the outside world see it? Am I missng something here?

Thanks,
J

Offline jackl

  • ****
  • 136
  • +0/-0
No Internal Web Site Access
« Reply #3 on: April 27, 2005, 09:32:40 AM »
John,
 Sorry maybe I mis-read the situation here, are you using external nameservers to resolve your current setup? If you are, then the information I gave  you should work as these settings will only effect the internal network and only if the SME server is set as dns server for the internal network. The system will use it's own DNS first to resolve an internal request if it can't resolve it it tries a list of public dns servers. I doubt if you are using your SME as public DNS seeing you only mentioned opening port 80.
 In other words to resolve names your external nameservers are first choice for external users, for internal requests SME has first go at name resolution and if it has an entry for that request that's what you get, despite your external name servers.

Regards
Jack

PS depending on your dhcp configuration, serv er-manager may require the mac address of the server and there should no need to publish globally.
......