Pulling my hair out with port forwarding and SMC Barricade: Sling Community

Member

member since: 12/20/2005
rank: 29152 of 29958
153 comments

January 13, 2006 1:20 AM

Palm -

On the Barricade router have you tried MANUAL port forwarding the x.x.x.237 IP Address of the Slingbox on Port 5001 for both TCP/UDP?

If you need some screenshots they can be found here:
http://portforward.com/english/router...

Hope this helps,
Sling On!!

palmsolo

Member

member since: 01/12/2006
rank: 2156 of 29958
2 forum threads started
5 comments

January 13, 2006 10:10 AM

Yes, I have. I did find that portforward.com website and followed the directions without success. I think I'll go pick up a Linksys router tonight and give that a try since I can always pass my other router on to another family member again.

Check out my blog at www.palmsolo.com

palmsolo

Member

member since: 01/12/2006
rank: 2156 of 29958
2 forum threads started
5 comments

January 14, 2006 12:44 AM

OK, so I went to CompUSA today and saw they had a good deal on a DLink G router so I bought that. Then when I got it home and tried to set it up it would not work with my old Qwest DSL Cisco 678 for basic internet. It looks like there is a cable incompatibility there, which is a bit strange.

So now I have a couple thoughts I will try tomorrow. First, I'll try picking up a Linksys router to see if that works. I am also thinking of buying a newer DSL modem and maybe then my SMC Barricade will work. Do any of you have a recommendation about which would be the best choice to start with? I just don't understand why port forwarding won't work on my SMC and wonder if it is due to the older Cisco DSL modem.

Check out my blog at www.palmsolo.com

josborne

Member

member since: 06/12/2007
rank: 18534 of 29958
6 comments

June 13, 2007 8:57 AM

I'm having the same issue with my SMC7004VWBR. Did you ever get this to work without replacing your router?

budman

Member

member since: 03/13/2007
rank: 20242 of 29958
44 comments

June 13, 2007 11:16 AM

What is the MODEL number of your "modem" 99 out of 100 times people have issues with port forwarding, is because they are behind a double nat.

Devices now a days are quite often really gateway type devices with modem/router combination. If you put a router behind that - double nat, an then yes portforwarding is a pain, etc.

If this is the case - you need to either set your "modem" as just a modem - ie bridge mode an use your router as the nat device.

Or you need to just use the wireless router as an accesspoint - an use the first device as the nat an dhcp, control portforwards, etc.

When having issues - PLEASE always give model numbers of ALL devices on your network.. be it you think its only a modem..

Had the longest time trying to help this person, found out they had a voip router in the mix doing NAT. etc..

josborne

Member

member since: 06/12/2007
rank: 18534 of 29958
6 comments

June 13, 2007 11:01 PM

Thanks for the reply Budman. here is my setup:

Cable modem is a Motorola Surfboard SB3100...It's running into a Motorola VOIP box model number VT1005V that then connects to my SMC Barricade SMC7004VWBR. I have never tried port forwarding of any kind with this setup. I have never had issue getting out with my PCs, Tivo, XBOX360 or VOIP box. Any Suggestions would be appreciated.

Thanks in advance.....

budman

Member

member since: 03/13/2007
rank: 20242 of 29958
44 comments

June 14, 2007 7:07 AM

Well what do you know a voip box ;) Guess what, that is most likely doing NAT.. If you look on the internet/wan IP address of your smc -- is more than likely a private address, 192.168.x.x, 172.16-31.x, 10.x.x.x

You can tell your SMC to forward something to all day long.. the PUBLIC ip is on the wan interface of your voip box.. Did you tell it to forward the traffic inbound to your smc wan interface?

What you want is this type of setup

Being behind a double nat quite often will not show any problems for outbound traffic, and reponses to your requests.. But any unrequested inbound traffic is going to be a pain.. And in general is not a good idea to double nat, unless you have no other choice -- or some specific reason to do such a thing. Plug your voip device into your smc like any device, and then forward the ports on smc if required for your voip service to work.

edit: if your smc supports it, I would suggest you turn on QOS for your voip traffic. Or another option, is to put the wan IP address of your router (static setup would be better if doing this on your smc) into the DMZ of your voip device. You can access the web interface of the voip box on 192.168.102.1 - you may need to directly connect a pc to voip device to access this IP?

I would suggest you setup as shown.. with the voip device connected to your router vs the other way around.. But there are many different ways to skin a cat ;)

josborne

Member