Topic 'Port Forwarding on SMCD3G' in forum 'Networking' - dslreports.com

Re: Port Forwarding on SMCD3G

Wed, 07 Mar 2012 10:19:15 EDT

NetFixer posted :

Thanks so much for the replies. I was unable to get back to the store last night and try these options, but I think I know what my issue might have been when I put the static IP info into my WAN interface. I was using the same IP that was assigned to my SMC gateway, which I didn't even think about, but that cant happen. Comcast told me I have a block 50.x.x.196/30 -198. with .197 being my WAN internet IP address in my SMC. Tonight I have am going to give the sonicwall 50.x.x.196/30 with a gateway if 50.x.x.197 and see what happens.

You don't have to guess, or depend on what you have been verbally told, just look at the network summary page in the SMC gateway.
--
We can never have enough of nature.
We need to witness our own limits transgressed, and some life pasturing freely where we never wander.

Re: Port Forwarding on SMCD3G

Wed, 07 Mar 2012 08:45:02 EDT

theITguy0903 posted : Thanks so much for the replies. I was unable to get back to the store last night and try these options, but I think I know what my issue might have been when I put the static IP info into my WAN interface. I was using the same IP that was assigned to my SMC gateway, which I didn't even think about, but that cant happen. Comcast told me I have a block 50.x.x.196/30 -198. with .197 being my WAN internet IP address in my SMC. Tonight I have am going to give the sonicwall 50.x.x.196/30 with a gateway if 50.x.x.197 and see what happens.

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 18:52:32 EDT

NetFixer posted : From my interpretation of what you have posted, it certainly sounds as if bdnhsv's advice that your SMC gateway is not properly setup for static IP usage may be correct (although it is not entirely clear to me that you ever setup your SonicWall to properly use your assigned static IP address).

Once you get your SMC gateway's static IP config either verified or corrected by Comcast, one primary thing you need to bear in mind is that Port Forwarding in the SMC gateway has absolutely nothing to do with any device connected using one of your assigned static IP addresses, it only applies to devices that use the SMC gateway's NAT router.

Shown below are some screen shots from my SMCD3G (and some comments) that might help you with troubleshooting:

[att=1]

If you don't see the same static IP information in the above page that Comcast told you to use, then there is definitely a config problem. If you see static IP information (but it is different than Comcast told you to use), you may want to try using the IP information that has been programmed into your SMC gateway just to see if it works.

[att=2]

If you scroll down in the Network page and click the [Connected Computers] button you should get a popup similar to the above image. At least one of the devices should be your SonicWall device, and it should have an IP address in your assigned static IP block, not the SMC's default 10.x.x.x subnet. Note that I use the 192.168.10.x subnet instead of the SMC's factory default settings, hence the devices in the 192.168.10.x subnet on my screen shot.

Also note that the devices using the 75.146.8.40/29 subnet have their WAN interface statically set to those values, and have their gateway IP address pointed to 75.146.8.46 (my SMC router's gateway IP address). This is critical, if you don't do that, you will not be able to use your assigned static IP address(es). Once you get that working, any port forwarding that you need to do for devices behind your SonicWall will need to be done in your SonicWall, not in the SMC gateway.

[att=3]

Above is a screen shot of my SMC Port Forwarding setup. I only have one port forwarded, and that is to a device that uses the SMC gateway's LAN subnet, and not one of my assigned static IP addresses. There is no way (and no need) to do port forwarding to a device using one of your assigned static IP addresses.

Shown below is an image of my current network, which might help with your interpretation of the above screen shots from my SMC gateway:

[att=4]

My Netgear router would be my equivalent to your SonicWall, and it's WAN setup is shown below:

[att=5]

Note that in the Netgear router's WAN setup, I am using one of my assigned static IP addresses, not DHCP, and not an IP address on my SMC gateway's LAN subnet. Also note that because I am using static assignment for the WAN interface, I have to explicitly specify DNS server IP addresses (there is no automatic assignment for DNS servers if you use static IP assignment)

The two servers that are directly connected to my SMC gateway have dual NICs and their WAN NICs are also setup to use IP addresses in my assigned static IP block, and point to the SMC gateway's 75.146.8.46 gateway IP address. They also are configured with valid DNS server information since static IP assignment does not allow for automatic DNS server assignment.

Any port forwarding that I need to do to devices on my LAN is done in the Netgear router, not in the SMC gateway. The use of assigned public static IP addresses makes port forwarding in the SMC gateway unnecessary (and impossible).

I hope that the above information will help and not further confuse you (especially since your user name implies the you are "The IT Guy").
--
We can never have enough of nature.
We need to witness our own limits transgressed, and some life pasturing freely where we never wander.

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 18:43:56 EDT

JohnInSJ posted : Is your SMC in "true static" mode? It should NOT be doing anything other than routing your static IP WAN to LAN. Kill all firewall/dhcp options, enable true static mode.

In "true static" mode the SMC should be a fairly dumb router. Otherwise you're doing double NAT, which would be bad.

Comcast ->SMC in dumb router true static mode -> SonicWall (your static IP) -> Nodes (10.193.x.x)
--
My place : »www.schettino.us

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 14:07:43 EDT

bdnhsv posted : if you manually set the static info in a pc connected directly to the modem and it does not work, then you need to call Comcast and have them double check your static IP info.

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 13:53:01 EDT

theITguy0903 posted : NAT Enables is what the Sonicwall tz-170 calls static ip..

Your options are NAT enable, NAT with DHCP, NAT with PPTP and NAT with L2TP

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 13:42:03 EDT

theITguy0903 posted : no i checked that NAT with PPPoE is not used..the network mode is NAT enabled

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 13:40:45 EDT

theITguy0903 posted : ah, I did not try that. I will though, What I did try is setup a machine behind the modem, let dhcp from SMC hand out info to the pc and then forward traffic on 3389 to the ip of the pc and it worked.

yes exactly, i set a continous ping to 8.8.4.4 and when I set the sonicwall WAN to the static info, it times out..change the WAN back to something in the scope of the SMC and it gets replies

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 13:38:50 EDT

bdnhsv posted : Also just re-reading. You changed from DSL to Cable. Is your sonicwall still set to use pppoe by any chance?

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 13:29:00 EDT

bdnhsv posted : And expound a little on what you mean when you say you lose connectivity. Are you unable to surf? Are you unable to ping a known public address (like 8.8.4.4) ?

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 13:26:11 EDT

bdnhsv posted : OK... Those look fine. What happens when you connect a PC directly to the modem and configure it with the static (50. address) info you got from Comcast? Will it surf?

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 13:22:31 EDT

theITguy0903 posted : DHCP is off on the sonicwall and the LAN default gateway is 10.193.99.129 and subnet is 255.255.255.192 all the clients are static clients in the scope of 10.193.99.xxx with the subnet of 255.255.255.192 and d/g of 10.193.99.129.. They are all in a simple workgroup, no domain and they can all talk to each other, even if I change to WAN IP to the ISP's Static info

I cant believe that there is an issue on the LAN side of my router, because this worked until I changed to Comcast right before christmas and I am just now getting around to fixing some remote setup i had, i also had some remote setup to view security cameras.

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 13:10:33 EDT

bdnhsv posted : Yes you have more than one problem. First - your network is mis-configured. That will need to be fixed first.

As I said before you need to configure the WAN interface of the router with the 50. address info. I suspect that the LAN loses connectivity to the outside world once you do that because you have the LAN side of your router either configured incorrectly or all of your clients configured incorrectly. What is the subnet mask you have assigned to your internal LAN (the S/M you are using on all of your clients and on the LAN interface of the router)?

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 13:05:37 EDT

theITguy0903 posted : hey no problem ask anything as many times as you want :)

I can run ping -t to www.google.com to watch connectivity

If i set the WAN interface of my router to 50.x.x.197/30 and Default gateway to 50.x.x.198, the settings that comcast gave me...I will lose connectivity... ping times out. I can set the WAN interface on the router back to an IP in the scope of the SMC, lets just say 10.1.10.10/24 and default gateway of 10.1.10.1

and BAM connectivity back..

I guess I really have 2 problems here and a solution to either one would fix me I think

A) traffic is not forwarding through the SMC
b) i cant connectivity using the public WAN settings the sonicwall WAN interface

The network modes I have available on the SonicWall is Nat Enabled (which I assume is the static option) NAT with DHCP, NAT with PPPoE, NAT with L2TP

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 12:20:22 EDT

bdnhsv posted : So just to be sure - the WAN interface of your router has the IP address 50.x.x.197, right? Sorry to belabor this question but I read your answers two different ways in previous entires.

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 11:57:07 EDT

theITguy0903 posted : yeah all that is set correctly. Everything is great behind the sonicwall on the LAN side, i have 25 clients all static IPs in the 10.193.99.xxx range, its just gettings traffic from the outside to the SMC to the Sonicwall and on my my pc on 10.193.99.140

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 10:41:34 EDT

bdnhsv posted : the 10. address you see from comcast is for their internal management by the way.

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 10:40:46 EDT

bdnhsv posted : you need the public IP on the WAN interface of the router. On the Lan interface of your router use the first usable IP of your subnet - 10.193.99.1 probably. Then on the PC you want to control assign a static address from your subnet (10.193.x.x) and use the LAN IP of the router as your default g/w on that pc. Make sure you have the correct subnet mask (a 10. network would normally have 255.0.0.0 unless you have subnetted it further). Any other devices in your network probably should be using DHCP for their IP assignments (and your smc router should be acting as your dhcp server).

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 10:30:41 EDT

theITguy0903 posted : thanks for the quick reply! I tried to set port forwarding to the PC on my lan directly on from SMC and it said Invalid LAN, I assumed it was because the PC that want to control remotely was on a different subnet than my SMC, the PC I want to control is on 10.193.99.xxx

I did put the static IP info in the WAN side of my Sonicwall and as soon as i did, I lost all connectivity. Quickly changed it back to 10.1.10.10 and regain connectivity. 10.1.10.10 is an IP i picked can be anything that the in the scope of the DHCP on the SMC and it will work. Static settings, no good.

Re: Port Forwarding on SMCD3G

Tue, 06 Mar 2012 10:15:08 EDT

bdnhsv posted : The forwarding needs to be to the IP of the PC you want to control (not the IP of your router). Also, make sure you have your static IP from Comcast configured on the WAN side of your router (I'm not sure you have it that way from your post).

Port Forwarding on SMCD3G

Tue, 06 Mar 2012 10:07:43 EDT

theITguy0903 posted : Ok, I searched the forums and looked for something close to this, but couldnt find exactly what I was seeing. I am trying to setup RDP on a PC on my LAN. Here is my setup

Comcast--->SMCD3G(10.1.10.1)--->Sonicwall TZ-10(10.1.10.10)---> Nodes (10.193.xxx.xxx)
I cannot get the SMC to pass traffic on 3389 to the sonicwall.
I have a static IP from comcast 50.XXX.XXX.197/30 and default gateway is 50.XXX.XXX.198. I can setup a pc in front of the sonicwall ( Comcast-->SMC--> PC) and remote desktop will work correctly, but as soon as I move that pc behind the firewall, it breaks.
I have my sonicwall WAN as NAT Enabled and 10.1.10.10.
I have setup port forwarding rules in SMC to forward 3389 traffic to 10.1.10.10 and allowed all traffic through the SMC, Nothing. I even tried to have comcast setup so called "bridge" mode, but really all it looks like they did was turn off DHCP on the SMC. I then set my WAN in the sonicwall with my Static info.. 50.xxx.xxx.197/30 and default WAN gateway to 50.xxx.xxx.198, when i do this I lose all connectivity out and in. I can run a ping -t, and change the settings back to 10.1.10.10/24 with default 10.1.10.1 and regain connectivity. Soooo. I come to conclusion that the SMC is not passing traffic to the sonicwall. I cant even get to the Web management of my sonicwall, which is turned on.

This all worked without issue until we switched from Windstream DSL to Comcast.

Oh yeah, I have setup firewall rules in the TZ-170 to allow tcp/udp traffic on 3389 and allow traffic on WAN:3389 to LAN and traffic from 10.1.10.1:3389 to LAN 10.193.xxx.xxx. Nothing has worked.
I hope this makes sense, I have been fighting with it for about 24 hours now. I am Comptia A+, Network+ and studying for my CCNA, I have a lot to learn, but i know what I am looking at, well atleast I think I do.. thanks!