Hi. I have the following setup on the Comcast Business Gateway (SMC).
1. My router is connected to the SMC Gateway and has a public IP assigned to it
2. My Web Server is connected to the router and it has an internal IP (NAT)
3. I have allowed access to the Web Server by port forwarding port 80 requests on my router to the web server (using the internally assigned permanently leased DHCP generated IP address). In addition to this I had to configure port forwarding on the SMC gateway (True Static IP Management) to forward port 80 requests to the external static IP that my router is at. Without doing this even though the router was configured to pass all http (port 80) requests to the web server connected to it, it was not doing so, the gateway had to be configured too.
The last step poses another question for me, in this case how would I be able to have an additional Web Server serving http requests ? Port 80 on the SMC gateway is already pointing to the router.
Multiple Web Servers
- YeOldeStonecat
- SG VIP
- Posts: 51171
- Joined: Mon Jan 15, 2001 12:00 pm
- Location: Somewhere along the shoreline in New England
-
cranialsurge
- New Member
- Posts: 16
- Joined: Thu Jun 04, 2009 1:09 pm
Hey there, we meet againYeOldeStonecat wrote:Can do the same thing with a 2nd router...using the 2nd static IP of your Biz account...set it up much in the same manner as your the first DLink router you setup.
The problem is that I already have one port forwarding rule on my gateway to forward http requests (port 80) to one of the servers that is behind a router on a static IP. If I have another router connected to the gateway and assign it another static IP, how can I create another port forwarding rule on the gateway to route port 80 requests to the web server behing the router on the second static IP. How would the gateway be able to decide which http requests to send to router 1 and which ones to send to router 2 ?
- YeOldeStonecat
- SG VIP
- Posts: 51171
- Joined: Mon Jan 15, 2001 12:00 pm
- Location: Somewhere along the shoreline in New England
You'd have 2x routers with their WAN/Internet ports plugged into the back of the SMC gateway.
Each of your 2 routers has a unique external/public/static IP address.
First router takes 123.234.12.101 for example
Second router takes 123.234.12.102
You can make the server behind each of them the same LAN IP address..say 192.168.0.10. Since each server is behind its own DLink.
Port forwarding would therefore be unique on each router...web request to port 80 going to the appropriate server.
Another method...and probably better...get a more SOHO/business grade router/firewall..to replace that DLink 655..which yes is a powerful fast router, but really home grade in features.
With many biz grade routers, you can use a single router, and it will support having multiple WAN IP addresses assigned to its single WAN interface.
So 1x SMC gateway
1x biz grade router
Several public IP addresses mapped to the external interface of the biz grade router
Server servers on the internal side of the router.
Gotta hit the road for a few hours, got 2 clients networks to hit for remainder of afternoon.
Each of your 2 routers has a unique external/public/static IP address.
First router takes 123.234.12.101 for example
Second router takes 123.234.12.102
You can make the server behind each of them the same LAN IP address..say 192.168.0.10. Since each server is behind its own DLink.
Port forwarding would therefore be unique on each router...web request to port 80 going to the appropriate server.
Another method...and probably better...get a more SOHO/business grade router/firewall..to replace that DLink 655..which yes is a powerful fast router, but really home grade in features.
With many biz grade routers, you can use a single router, and it will support having multiple WAN IP addresses assigned to its single WAN interface.
So 1x SMC gateway
1x biz grade router
Several public IP addresses mapped to the external interface of the biz grade router
Server servers on the internal side of the router.
Gotta hit the road for a few hours, got 2 clients networks to hit for remainder of afternoon.
MORNING WOOD Lumber Company
Guinness for Strength!!!
Guinness for Strength!!!
-
cranialsurge
- New Member
- Posts: 16
- Joined: Thu Jun 04, 2009 1:09 pm
Oh yea, I get that part that servers are unique to the routers and the port forwarding on the router is not a problem at all. The problem is that the gateway to which the routers are connected needs to port forward port 80 connections to the appropriate public/static IPs (for each of the routers) too. Now there can be only 1 port forwarding rule for port 80 requests in the SMC gateway. I have already configured it for router 1. How do i configure one for router 2 ? It seems weird but traffic being directed directly to the routers cannot access the routers even though they are on public/static IPs. The SMC gateway to which the router is connected itself needs a port forwarding rule to direct http requests (port 80) to the appropriate router that is connected to the gateway.
- YeOldeStonecat
- SG VIP
- Posts: 51171
- Joined: Mon Jan 15, 2001 12:00 pm
- Location: Somewhere along the shoreline in New England
Nope...remember, you logged into the SMC and disabled the firewall features for true static IP. So the SMC isn't doing any firewall filtering for your static IP address.cranialsurge wrote:Now there can be only 1 port forwarding rule for port 80 requests in the SMC gateway. I have already configured it for router 1. How do i configure one for router 2 ?
Traffic is not going to the WAN IP of the SMC anyways..it's going right to your own routers public IP address.
MORNING WOOD Lumber Company
Guinness for Strength!!!
Guinness for Strength!!!