NetGear RT-338 ISDN Router

[Algonac]

HELP!

I have to set up a remote office to our main office. These Netgear RT-338's say they can do LAN-to-LAN connections. T-1 is too expensive.

The remote office has five computers. Those five will need to see the main office LAN(one server there)and also the internet. The main office is connected to the Corporate HQ thru another router using a T-1. That is where we get our
Internet. At the home office, we have our own "real" static IP's, all in the same subnet. The setup for the Netgear routers says I have to have the remote office on a different subnet. So I will setup the five computers at the remote site to have 192.168.x.x addresses. I can live with that as long as they get Internet access thru the main offfice and can access that server.

I can't seem to get it setup correctly. How does the remote site see the internet? How does it initiate the call? Just bringing up Internet Explorer does not do it. I have set the connection for NAILED-UP and that makes the connection, but the computers cannot access the internet.

What are the correct "Remote IP address", "My WAN address" and "LAN IP" addesses for use in my case where our main office is all on static "real" IP addresses?

Anyone ever do this before?

 

[polarismd]

I have a similar problem...did you get it solved?

CB

 

[Algonac]

Yes, we solved this. At the main office, we had to set a static route in the router there. The static route is set to reflect packets "BACK" to the remote site that are meant to go there. We had to have a corporate IT person log into our T-1 Router that goes upstream and make this addition. I did not have the password.

Our settings for the ISDN gear was simple actually. Our settings were:

Remote site LAN for computers there = 192.168.90.x (where x=2 to 255)We used DHCP from the Netgear router.
remote site ISDN Router LAN IP = 192.168.90.1
remote site ISDN Router WAN IP - 10.0.0.2
Office site ISDN Router WAN IP - 10.0.0.1
Office site ISDN ROuter LAN ip - 170.139.20.6
Office site LAN for computers there = 170.139.20.x
Office site Router to corporate = 170.139.20.1 (This is the router where the reverse static route needs to be established.)

It is fair to say that the router in the middle, main office needs to be a higher end router that can have static routes installed. If you just have a DSL line with a simple router installed there, you may not be able to do this. You will have ask your ISP. If you have a T-1 router, I am guessing that you CAN do this. Again, contact your ISP for help.

The reverse static route settings we used were:

Route = 192.168.90.0 (the zero indicates the whole subnet and this is the subnet of the remote site.)
Gateway = 170.139.20.6 (office site ISDN Router LAN address)

All subnet masks for our applications are 255.255.255.0

I think I left something out, but this is the concept. You know it works when you can ping a main office IP address from the remote site. and then you can get to the internet also.

ALso, on these RT-338's the Netgear folks said, do not use the Windows config app. Use a RS-232 connection for all setups.

Email back if probs.

-Mike T.

 

[polarismd]

Hi, That helped a lot. We can now talk to our main router firewall but we still cannot get out?

We can get to the main routers internal http page and by setting up static routes, here FVS318, we can even talk to our HTTP servers on the internal LAN remotely.

Can you explain how you set up the remote LAN to route through the RT338's and then through the main router to the internet?

To recap we have the following..

Internet and Static IP addresses are provided by our internet provider on this side of the FVS318. Here we have our main servers etc.

Router/Firewall (FVS318) - Static Real World IP Address.
-----------
Router/Firewall (FVS318) - 192.168.0.1 LAN Side.

Local Lan 192.168.0.5- 192.168.0.30 FVS DHCP provide local LAN with pool.

Two servers HTTP and FTP for testing 192.168.0.100/102

ISDN Router Main LAN Side 192.168.0.31
------------
ISDN Router WAN Side 192.168.0.99

ISDN

ISDN Router WAN Side 192.168.1.100
------------
ISDN Router Remote LAN Side 192.168.1.1

Remote LAN 192.168.0.0



I really hope you can throw some light on this. Netgear people are scratching their heads.... I did this once a couple of years ago using Cisco kit but I cannot get the bloomin thing to work here.

I appreciate anything you can point us at?

Regards

CB

 

[Algonac]

I have all the stuff at the office in a binder. But what I see wrong from what I learned from my discussions with Netgear (John and Brad in the Netgear VPN Group in New Jersey) is that you need to setup a whole different subnet for the WAN. Instead of different subnets (192.168.100.x and 192.168.1.y, I used 10.0.0.1 and 10.0.0.2. These addresses must be in the same subnet, 10.0.0.x.

Also, you show the remote ISDN as 192.168.1.1, but then you show the remote LAN to be a different subnet of 192.168.0.0. These need to both be the same subnet (say 192.168.1.x and NOT the same subnet as the main LAN (at 192.168.0.x)

Make the remote LAN pool or other devices all to be 192.168.1.x and leave the main LAN as 192.168.0.x.

The next part is the gateways and static routes. I need to see my screen shots I made (for later reference and troubleshooting) that are in the IT shop in a notebook at work. In general, From the remote site, the users there use the LAN address of the ISDN Router (192.168.1.1 in your example)for their gateway (set in their computers). The rest will have to wait until I look at my sheets. I recall there are two ststic routes installed in the main ISDN router. I will send more info tomorrow.

One thing we noticed that we never did solve once we got it all working was why users could not login to

http://www.aol.com.

We could get to the website, but the users login went nowhere. Maybe it was a Java setting problem or some other thing, but we never solved it.

My direct email is mjtosch@cbs.com. Email me and I will email you back the two word docs with all my screen shots in them.

-Mike T.

 

[polarismd]

Just wanted to say that I did get this sorted with Mike's help, anyone else with the same or similar problem please contact me. I have a large source of information that I am trying to get into a useable form.

It does work.... so don't panic too much if yours does not come together straight away.

Once again thank you Mike.

CB

 

[edslock]

You need two seperate networks for routing to work. Leave the main office as is and on the wan use 192.168.128.1 subnet mask 255.255.255.0 , also you need a defalt address on the wan side 0.0.0.0 mask 0.0.0.0 192.168.128.1 (defalt gateway) . The wan side should be able to connect to the internet thru the main office as well as the main office lan.