two ip's, two networks, one modem

April 15, 2010 at 18:54:20
Specs: Server 2003, 2008
I have two networks that I want to keep
separate but connect to the same cable
modem.I have several switches available and
a WRT54 Router and a 11S4 Router. I have
two static Public IP addresses. I've tried
connecting and configuring 8 ways from
Sunday and all I have is Internet on the
original network (server 2003/WRT54).

See More: two ips, two networks, one modem

Report •


#1
April 15, 2010 at 19:02:35
Connect both routers (WAN interface) and the modems LAN interface to a small switch.
The modems WAN interface should be connected to the wall plug (ISP).

The initial requester should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#2
April 15, 2010 at 20:25:27
Thank you for your quick reply. That was the first setup that
didn't work.

Report •

#3
April 15, 2010 at 20:30:35
If both routers do have a public ip address and no other authentication is needed, to establish the connection to your provider, this should work.

The modem in this scenario is running in bridge mode.

You may provide more infos to help you, to get it to work.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

Related Solutions

#4
April 15, 2010 at 20:49:38
did you assign those static ip addresses to each routers wan interface?

usually the routers have a test internet connection button/interface. Did you test at this time from the routers?


Report •

#5
April 15, 2010 at 21:26:24
The system was working as normal with a server and network
connected to the router to the modem. An additional IP was obtained so that a new server could be added to the Internet.
The static IP's were assigned to each Router. The setup was
then changed to = modem > switch > two routers. The original
server connects to the Internet as always, the new server does
not connect. I suspect the second router has a configuration
problem, but I'm at a loss to figure it out. It seems to me the only
change from default settings should be the separate IP address.

Report •

#6
April 15, 2010 at 21:34:30
So simply compare the settings of both routers.
The difference should be the static public ip and the static private ip, nothing else.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#7
April 16, 2010 at 07:33:36
You should be daisy-chaining the routers. It should look as follows:

Internet >> WAN port router 1 >> LAN port router 1 >> WAN port router 2 >> Switch/clients

Click on my name above in my response and read my "how-to" guide on adding a second router.


Report •

#8
April 16, 2010 at 08:23:14
Sorry CurtR but that isn't what the OP wants and would not utilize the two public ips.

jsimmons
Post the results of an ipconfig /all from the server not connecting for review.

Once again there should be a "test the wan connect" interface in the router. Usually it connects you to the manufacturers web page or gives a message like test Ok or failed. Please find this interface in the router and test from the router to the internet. Some also have ping as a test so ping yahoo.com for example.

Another approach is to take that static ip and assign it to a workstation. Put the workstation on the switch [disconnect the problem router] and see if the workstation connects.

If it doesn't call you isp. It is something at their end not yours that is the problem.

If it does connect then the problem is located specifically tg the router. We will address that once you have done the tests above.


Report •

#9
April 18, 2010 at 18:32:51
I'm sorry I haven't responded sooner, but life has been
happening.
I went back over everything. I set the 2nd router back to the
factory default. Then set the correct IP address. Then wired it
all up again as PaulSep suggested in the 1st reply. Then I
ran the "Connect to the Internet routine" built into Server 2008.
The routine failed with an error that said it could not start the
DNS server. BUT the Internet DID connect and I then went to
whaismyipaddress.com and it returned the correct IP
address. Success at last!
The only problem now is that Server 2008 thinks it is NOT
connected to the Internet. None of the setup routines will
work without connecting to the Internet. Now what?

Report •

#10
April 18, 2010 at 20:31:12
You simply have to configure the Server 2008 with a fixed private ip address, that matches the ip address range of the router, it's connected to.
Also you have to use the right subnet mask.
The default gateway and the DNS server should be the private ip address of the router, the server is connected to.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#11
April 22, 2010 at 07:11:00
Thanks mostly to PaulSep I now have my systems up and
recognized by their respective servers. I appreciate the hand
holding.

Report •

#12
April 22, 2010 at 09:30:31
That's great !
You're welcome !

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

Ask Question