Welcome to WebmasterWorld Guest from

Forum Moderators: Ocean10000 & incrediBILL & phranque

Message Too Old, No Replies

How does everyone setup network to see webserver?



8:05 pm on Nov 17, 2007 (gmt 0)

5+ Year Member

Running windows xp with appache.

I need to setup the network so the workstations so they can see the webserver from the internet and also transfer files via the lan.

Is there a standard way to do this?




8:54 pm on Nov 17, 2007 (gmt 0)

10+ Year Member


Huge question, probably best asked in a forum dealing with networking, not an Apache Web Server forum.

Without knowing your size, scope & topology of your network, if the server(s) are hosted in house, or outsourced, it is almost impossible to answer.

In general, keeping in mind there are many ways to accomplish this depending on the budget and requirements of server(s)loads, and issues with security.

Most Secure:
In a large network, use of firewalls & routers is common to create a DMZ(s) to put the webserver(s)in, with security allowing internal users access to put files on the server.

Least Secure:
In a small network, you might have multiple nics in the box, one facing your internal network, the file server is literally just another server on the network, and the other nic facing the Internet.

If you are having difficulty understanding what I have posted, you should bring in a Network Engineer to design this for you for the best results for your needs.



10:00 pm on Nov 17, 2007 (gmt 0)

5+ Year Member

I have a windows/apache webserver with 5 domains. It is going through the same dsl modem as my lan. There are 2 nic in the webserver that got to 2 different router setups. Both routers go into a switch and then into the dsl modem.

I can see the websever files across the lan but can't access it via the internet from a lan workstation.

Other people can access the websites.

One router is: Dynamic

Lan is :

Other router is: Static

Lan is:


12:22 am on Nov 19, 2007 (gmt 0)

WebmasterWorld Senior Member jdmorgan is a WebmasterWorld Top Contributor of All Time 10+ Year Member

The problem is clearer if you realize that "accessing the server on the internet from the LAN" inplies that as seen by your modem and router, this would be a connection that was out-going and in-coming at the same time, and that is impossible.

A quick fix that avoids having to have a separate connection to the internet for your non-server machines is to go into the 'hosts' file on each of the LAN machines, and define the local DNS for your domains so that they point to the local IP address of your server. The DNS in the 'hosts' file will then override the 'internet' DNS for your local machines only.



2:38 am on Nov 19, 2007 (gmt 0)

5+ Year Member

It is not impossible because it worked for over a year.

I talked to Dlink, two DI-604 routers, the other day and they did not say it could not work but tried to help figure out why it was no longer working.

Hosts files do me no good because I have a static ip and registered domains. My isp and router config already has the dns server addresses and looks it up automatically.

When it was working I did not have a host file.


11:47 am on Nov 19, 2007 (gmt 0)

WebmasterWorld Senior Member jdmorgan is a WebmasterWorld Top Contributor of All Time 10+ Year Member

Well it is impossible for a TCP/IP packet to be routed in two directions at once. I don't know how you had this set up before, but if your LAN workstations were accessing your server 'from the internet' --that is, by using the WAN-- then perhaps you were using a proxy server on the WAN to receive these packets, and then re-originate incoming packets to your WAN IP address on port 80.

Alternatively, perhaps your router was configured to recognize internal requests for your WAN address on port 80 and to port-forward them internally.

In the first case, the proxy servers would not be sending the same TCP/IP packet they received -- it would be a new packet with different routing headers. In the second case, your LAN machines were not accessing your server 'over the internet' as you stated, because the packet routing remained within your LAN.

Hopefully, this may steer you in the right direction.



7:51 pm on Nov 19, 2007 (gmt 0)

5+ Year Member

If you read my earlier post you will find I have two different routers. Each one has a different IP due to one being static and the other dynamic. No collission.

It seems to me there is a different setup on the web that has one router going through another router (series). In that setup the workstation can see the webserver because it is on the first router.
That setup would have all the workstations and webserver all with the same IP when the went onto the net.

Matter of fact, the DLink manual for the DLink switch states it does not support two machines with the same IP address. So, if they were the same, the switch would block it.

I have called DLink three times on this matter and they are absolutely no help. I am currently using DLinks DSS-5+, DI-604 and a DI-704P and they wanted me to download the latest firmware for the 704p and dss5+ which do not have upgraded firmware.

I wonder if their call center is out of the country. I think they have more than one call center too because sometimes when I call I get a lot of background noise in that center and when calling the same number 1/2 hour later I got a quite office.


10:41 pm on Nov 20, 2007 (gmt 0)

5+ Year Member

After switching out all of the NICs, switches and routers the only thing left was the dsl modem. I replaced that today and I still had the problem!

Upon calling isp tech support it was suggested I do a traceroute. after doing a traceroute to my domain and to a known other good website I was able to see it was dying at an ip address.

It turns out it is my isp. They are checking into it. My guess is that they made either a software or hardware change during the last 2 weeks that does not allow 2 ip addresses for the same mac address of the modem.


Featured Threads

Hot Threads This Week

Hot Threads This Month