Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

View website from inside the network

Status
Not open for further replies.

Cirrus9

IS-IT--Management
Aug 21, 2001
248
US
I have a customer with a website that is online with a public IP address *.*.*.147

I am using a Dynamic DNS service that resolves the Domain name to the Public IP address (*.*.*.147).

The public IP address (*.*.*.147)is a router that forwards the visitor to a web server within the network to view the website.

The web server's internal (intranet) IP address is 192.168.1.10.

The users inside the network can't view the website because when they are referred to *.*.*.147 which is the local router and it tries to log them into the router.

I had expected to get the users to use the internal IP address of the Server (192.168.1.10) to see the web site.

I was then going to change the HOSTS file on each PC in the network to make the domain resolve to 192.168.1.10 so they would'nt have to keep typing the IP address.

The problem is that they can't see the site inside the network.

What am I missing? The server is on the same subnet but the LAN is in a workgroup and the server is in it's own domain, disconnected from the rest of the workgroup. Could this be it? Do the members of the workgroup have to be in the same domain or workgroup as the server to see the site?

I am at a loss. I am hoping that one of you experts in this type of networking can offer a solution or idea.

Thanks for your help in advance.
 
This doesn't sound like a general hardware problem, more likely it is something specific with your web server. You might try posting the the specific forum for your software.

1. Have you tried hitting the web site from another PC on the outside? You should be able to pull it up from another internet connected PC that isn't behind that router. If not, it could be a configuration issue on the web server.

2. As long as the PCs inside the network have connectivity to the internal web server (can ping, etc) then they should be able to pull up the web site via IP address. The only exceptions that I can think of would be if both the internal and external addresses were somehow configured on the web server, and the server was configured to only listen for http traffic coming to the external address.

 
If you can see the website from the outside using the domain name do the same from the inside. a call to should go out to the dns server and resolve to the IP of the router which should forward the call to the web server. At least that's how mine works.

The answer is "42"
 
I can view the website from outside the network. However, I can't see the website from within the network. Trying to use the IP address inside the network just gets a 404 error.
When it resolves the IP as *.*.*.147 then while inside the network, it recognizes it as the Router and prompts for a router login.

My biggest hurdle is that I am 2 hours away from the server and they can't set up a remote service like logmein

Thanks for your help, Do you suggest I go to the Server 2003 forum?
 
Many routers cannot do a reverse loopback.

Set in your HOSTS file a substition using the local IP of the server.

e.g.

192.168.1.12 my.website.com


____________________________
Users Helping Users
 
The thing that really gets me is that even if they browse to the server via it's internal address (192.168.1.10) they still can't see the site. I'm wondering if there may be some code on the web site that redirects the page to another directory or file that uses absolute links/paths instead of relative paths, especially if those paths use the server's FQDN. For example, the web server loads the default web page (index.html or whatever), and then that page links/redirects to " instead of "/home/index.html". That would definitely cause a problem if the router was blocking http traffic coming from the inside.
 
I tried the IP address before I posted and there was no luck. I haven't put anything on the site yet but a default page to let me know I hit the site. I can get there from outside but there is no luck internally. I am inheriting this project from someone else and it looks liek I moght be better off restarting the whole thing from top to bottom. I took the advice from kmcferrin and posted to the Server forum. Someone there pointed out that the DNS is not being initiated internally and that I might need to set it up so that the request is routed correctly from inside the network. I think they might be on to something. I was looking at setting the HOSTS file on all PC's inside the network from the beginning but this may allow me to bypass that level of maintenance.

Thanks for all of your help. I learned a good bit from your suggestions. I still may need your help I will post back if I do not succeed.

Thanks Again
 
Using DHCP, my small LAN all can access the internet. My Netgear ADSL/modem/router assigns any attached device in the range 192.168.0.2 onwards. The pcs are all set to receive their IP automatically in the LAN Card settings. I don't assign them the router address of 192.168.0.1 otherwise they will try and log on to the router.
I used to have to mess around with all sorts of rubbish with ICS but DHCP via the router is a godsend.
Sorry if I'm missing the point here.

My Feeblegirl.com Forum boards for mmorpgs, sport, fun, politics...
 
Guthro, that's not what he was getting at. He actually has a web server behind the router, and in order to make it available to people from the Internet he has to configure port forwarding on the router to forward traffic coming to the router on port 80 to the web server behind it. The problem is, when he tries to access the web server from a PC that is behind the router (rather than on the Internet side), the router recognizes that the requesting PC is behind the router and takes him to the router's management/configuration page instead of the web server.
 
I got the server in-house (the client was 2 hours away and all configs were by phone because client could'nt get logmein to work) I started from scratch and got it to work. I don't know what caused the issue but it works now. Thanks for all of the help. I really appreciate your time in helping me.
 
Is this one of those weird situations where the order in which things are started/intstalled governs success or failure ?


My Feeblegirl.com Forum boards for mmorpgs, sport, fun, politics...
 
If your computers on LAN are setup as workgroup, you need to set them up as part of the domain,otherwise there wont be a network to the server.Let me know if this helps,Good Luck.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top