General discussion

Locked

SonicWall/DSL Connection Problems

By rawright ·
This one's making me talk to the walls! Help!

I have a SpeedStream 5667 DSL Modem connected to the WAN side of a SonicWall SOHO2; the LAN side of the SOHO is connected to our LAN hub. Although we have a fixed IP from our ISP, they insist on auto-configuration of the connection so that they can change gateways and DNS servers on the fly.

The modem seems to be working fine - It has a management port at 192.168.168.168 that shows that it is connected and working with the ISP connection. According to the manufacturer, it is supposed to pass traffic thru to the SOHO without change. But when I access the SOHO, it displays a WAN address in the 192.168.168.x range, not the correct public IP address!

Clients on the LAN can access theInternet thru this setup, but I can't connect thru it from the Internet. I've set up a rule to allow incoming traffic from my home IP, but it still refuses the connection. I've also forced the SOHO WAN port address to our public IP, but that caused the outgoing connections to fail. Both manufacturers insist the problem is with the other's box, and the company that sold the SOHO to us is clueless.

Can anyone give me some guidance here? I'm at wits' end, and the bosses are becoming unfriendly!

This conversation is currently closed to new comments.

8 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

SonicWall/DSL Connection Problems

by Ann777 In reply to SonicWall/DSL Connection ...

If the only problem is that you cannot see the routable ip address from the inside... to tell people how to connect.... then all you have to do is:

go to http://www.grc.com
scroll down until you see shields up icon
click on the words "Shields Up!"
scorll down to "test my shields"
click on Test my shields
YOUR EXTERNAL ROUTABLE IP ADDRESS IS THAT NUMBER (your modem/isp is converting it to 192.168.168.168 ... but people will need to connect to the routeable ip address -- which may change from time to time).

Other DSL companies do this too. It's a pain to figure out what ip address you need to be using each time it changes, but it's doable.

Collapse -

SonicWall/DSL Connection Problems

by Ann777 In reply to SonicWall/DSL Connection ...

Basically from outside in -- you need to connect to the static ip address that your isp provided. not anything beginning with 192.168.168.x

Collapse -

SonicWall/DSL Connection Problems

by rawright In reply to SonicWall/DSL Connection ...

Nope. The static IP doesn't work. I can ping it nicely, but the SOHO doesn't respond. I have another in Lake Tahoe, using a different DSL provider with a true fixed connection, and when I access it over the web I get back a logon request for the SOHO management port. From there I can set the internals of the remote SOHO. I need to acheive the same behavior for this end - once I have that, I can complete the VPN easily.

Collapse -

SonicWall/DSL Connection Problems

by isys In reply to SonicWall/DSL Connection ...

You need static IPs for the DSL modem (WAN gateway in the SOHO config)and SOHO WAN port, and they both need to be part of the same network (216.202.123.XXX) and same net mask. If not they will not be able to communicate with each other. If your ISP insists on managing the connection it sounds like you don't have a static IP for your DSL, sepecially if the DNS and gateway changes. GRC.com is a good place to see exactly what your public IP is. But you can not get into the SOHO if the public WAN port has a non-Internet routable IP (i.e. one in the 192.168.168.XXX range). See RFC 1918.

Collapse -

SonicWall/DSL Connection Problems

by rawright In reply to SonicWall/DSL Connection ...

The ISP does manage the connection, but the IP is permanently assigned. The modem mfr assures me that the box passes all the traffic straight through to the SOHO, and the SOHO is manually set to use the reserved public IP for the WAN interface. The SOHO is also correctly passing through DNS requests to and from the ISPs unspecified servers, so that part is working correctly. But incoming connections to the fixed IP are not working; I'm assuming that the fact that ping works is only because the DSL modem is responding...

Collapse -

SonicWall/DSL Connection Problems

by justemazing In reply to SonicWall/DSL Connection ...

The 5667 is capable of both bridge and router modes. It sounds like this one may be in router mode with no napt server configured to send traffic through to the SonicWall. If you can telnet to the 5667 and have the password, use 'show router' command to see which mode the dang thang is in.

If it is in router mode, you have 2 choices:

-enable bridged mode
-add a napt server to pass all traffic (all protocols, all ports) to the SonicWall.
(ie: set naptserver 0 0 <ipaddress of SonicWall>

Also, I seem to remember setting a SonicWall up on with a Speedstream 5851. The SonicWall WAN IP has to match the subnet for the Speedstream LAN ip (192.168.168.xxx) and SonicWall LAN had to use a different subnet. The SonicWall should be using the Speedstream LAN ip for it's gateway not the public ip address. Note: This is for routing mode.

--
Rob

Collapse -

SonicWall/DSL Connection Problems

by rawright In reply to SonicWall/DSL Connection ...

All of the mfrs agree that I'm doing everything correctly, and the 5667 is supposed to bridge, but it's not really. The mfr suggested connecting it straight into a PC - did that and it doesn't work. But I've noticed that my remote setup has more than one public IP - one for the modem, the other for the SonicWall. The boss didn't bother to mention that the other site has multiple IPs assigned. I've ordered the same here and hope that it will be solved in the next week or so. BY the way, the5667 doesn't respond to Telnet; it has only the HTML interface, which doesn't have an option to changes modes other than NAPT.

Collapse -

SonicWall/DSL Connection Problems

by rawright In reply to SonicWall/DSL Connection ...

This question was closed by the author

Back to Networks Forum
8 total posts (Page 1 of 1)  

Related Discussions

Related Forums