I have a TZ170 at work and have administrative priveledges and can't connect to my slingbox at home. I didn's see any answers posted to your problem, but was wondering if it got solved eventually.
I have an Action tech DSL modem, and a Sonic Wall TZ170 firewall, and I can't get the Slingbox to work outside of my home network. The Action tech has a static ip, but NAT is enabled so that the SonicWall is at 192.168.168.168. The Slingbox is at 192.168.168.137. Port forwarding is set up on the Action tec to send 5001 to the sonic wall IP, then onto to anyIP. The SonicWall has two firewall rules, one allows the .137 address to connect anywhere on the WAN (internet) and the second allows any internet address to connect to the .237 address. Still I can't get through to it. Anyone familiar with Sonic wall? That is where I suspect the problem is.
Unfortunately, I couldn't get past the Sonic wall at home, so for now, I've taken it out of the loop and am relying on Norton personal firewalls. The Sonic wall at the office doesn't have any specific rules allowing the sling box through, so I am assuming the player works without having to have 5001 enabled. Can you conect to your slingbox from anywhere else--like a public hot spot, a friends house?
Do you have a Sonicwall at work? I didn't try it at another location, but tech support at sling said they could see it from there.
Yes, I have the same sonic wall both at home and at the office--the home one is disconnected for now.
One rule I have that *may* let the player work, while I have a rule to deny any activity coming into the LAN from outside that isn't speciifically allowed, like this:
Source Destination Service Action
* LAN Any Deny
That protects us from any random attempts to connect to our machines, unles I specifically add in allowing rules, like for web, ftp, etc.
I also have a rule like this:
LAN * Any Allow
While that would cause problems if we had a trojan or virus on one of our machines, we have a pretty small network and its not a problem.
I have set up a Slingbox Pro behind a TZ170 (Sonic OS Standard) with no problems. In that case it is a double NAT situation and still works fine. It is not clear from the original post if double NAT is being used or not. If so, on the Action Tech make sure you port forward to the Sonicwall's WAN IP adress (not its LAN IP). In a double NAT situation, the trick which BK missed is you have to set up an implicit port forwarding rule on the Sonicwall. Unlike other firewalls, there is no explicit page to set up port forwarding rules. To get through a Sonicwall NAT and using private IP address (the case here) you have to set up a Slingbox service and assign the Slingbox TCP port you use. Then set up a rule that allows access from WAN to the specific Slingbox IP for that specific service. That effectively create port forwarding on the TZ170.
On my TZ170 NAT is the only WAN option, so the above config applys, but if using Enhanced OS maybe there are other options. If you are not using NAT on the Sonicwall and it only has a LAN IP (true router mode) which is on the same subnet as the Slingbox, then I think you you need to port forward from the Action Tech to the Slingbox IP not the Sonicwall IP.
So has anyone got anywhere with a Sonicwall? I've got a TZ 190 that I'm trying to get to work but haven't had any luck. I know this isn't a cheap device.. but someone got to have one of these things working....


RSS
