3 replies
by priorlee Accepted solution
by larryd4 Accepted solution
The only nat route you setup is the one for the web server. As soon as you go off of that server for other links they will fail. You will need to do the same for the other servers that have web pages you want them to see.
Ahh but you could setup a virtual directory on your web server, but what experience do you have with virtual directories is the question.
by deadly ernest Accepted solution
1. are the links full absolute links or partial or relative? In such a case they should be full absolute links, but think how they're written.
having the link as www.blogs.com/hr/vacanies requires a dns resolution before it can find it and then the server stated needs to be available from where the do the dns. But if it's internal and you have it as 192.168.0.57/hr/vacancies then it can be bounced straight over by the router.
2. Check both servers can speak to each other both ways through the routers in between, many gateways have one way only connections with things outside the gateway and inside the lan. You may have to move the other server into the gateway DMZ, or duplicate it out there.
3. the second server is expecting and allowed to serve pages to the first - this relates to the network settings and may be affected by the gateway router settings. If one server is in the gateway DMZ and on say the 192.168.6.x network with a mask of 192.168.6.255 and the other is on the 192.168.1.x with a mask of 192.168.1.255 they won't be able to see each other due to being on different logical networks.
if all that is OK, you will really have to have a close look at the routing tables in each router in between.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending