[jgmorten]

I have followed the airport extreme/ slingbox problem thread and am encouraged by your responses although most are over my head. I have tried to understand the basics and read the AX manual sections you sugested, but am just as frustrated as lyronis. I have a Westel router receiving the DSL phone line. A cat 5 cable runs from the router to the Airport extreme. Two pc and one Mac have cat 5 lines to the AX. One Mac book is connected wirelessly to the AX. The mac book can view the Sling box all around the house, but can not communicate from other wireless hotspots. The Ax is currently only setting up in bridge mode. The "share a public IP address" mode encounters a set up problem (My fuzzy last night memory thinks it said "two wan numbers exist".) Beyond that I can set up in the 10.x.x or 127.x.x subnets, but the 192.168.1.x will not accept any ending addressess. (192.168.0.x is accepted, but the slingbox address is supposed to be 192.168.1.201 and that is outside the beginning and ending range) I usually type in the beginning address as 192.168.1.1 which is accepted, then try every number up to 192.168.1.255 to no avail. (255 is the highest three digits it will even let me type, and then it tells me the number is invalid.) Failure at this juncture will not allow me to move on to port forwarding. Also the AX currently only "green lights" in bridge mode. If you have any simple advice it would be much appreciated.

[smax013]

Quote:

---

I have followed the airport extreme/ slingbox problem thread and am encouraged by your responses although most are over my head. I have tried to understand the basics and read the AX manual sections you sugested, but am just as frustrated as lyronis. I have a Westel router receiving the DSL phone line. A cat 5 cable runs from the router to the Airport extreme. Two pc and one Mac have cat 5 lines to the AX. One Mac book is connected wirelessly to the AX. The mac book can view the Sling box all around the house, but can not communicate from other wireless hotspots. The Ax is currently only setting up in bridge mode. The "share a public IP address" mode encounters a set up problem (My fuzzy last night memory thinks it said "two wan numbers exist".) Beyond that I can set up in the 10.x.x or 127.x.x subnets, but the 192.168.1.x will not accept any ending addressess. (192.168.0.x is accepted, but the slingbox address is supposed to be 192.168.1.201 and that is outside the beginning and ending range) I usually type in the beginning address as 192.168.1.1 which is accepted, then try every number up to 192.168.1.255 to no avail. (255 is the highest three digits it will even let me type, and then it tells me the number is invalid.) Failure at this juncture will not allow me to move on to port forwarding. Also the AX currently only "green lights" in bridge mode. If you have any simple advice it would be much appreciated.

---

What are the IP addresses of the two PeeCeee computers and the Mac? What IP address does the Airport Extreme show in the Internet connection window of the Airport Utility? What is the IP address of the Slingbox? If I am understanding your setup correctly, your modem also has a router built into it...and it is THAT router (not the AEBS) that is assigning IP addresses to everything. If so, then you should only need to get into the Westel's setup to forward port 5001 to the Slingbox's IP address. But, then I might not be understanding your setup.

[jgmorten]

Thanks for responding. Following up your Westel thought, I called my provider and they informed me that I would need a static ip address to remotely access a device in my home network. (I am currently on a dynamic setup.) This may have been mentioned in some of the previous discussions, but I would not have understood the significance. Hopefully that is the answer. Thanks again

[smax013]

Quote:

---

Thanks for responding. Following up your Westel thought, I called my provider and they informed me that I would need a static ip address to remotely access a device in my home network. (I am currently on a dynamic setup.) This may have been mentioned in some of the previous discussions, but I would not have understood the significance. Hopefully that is the answer. Thanks again

---

You should NOT need a static IP address. A static IP address will HELP make it easier to some degree. But, if you use the Slingbox Finder ID function, a static IP address is NOT needed. I have a dynamic IP address with my cable modem service and I have absolutely no problem accessing my Slingbox from outside my internal network. The Slingbox somehow lets Slingmedia know the IP that it is operating from and they match that IP address up with the Sling Finder ID and it finds your Slingbox.
Even if that were NOT the case, you could still establish a domain name for your dynamic IP address and have a dynamic DNS service "point" to that domain name. That process is kind of like how I believe the Sling Finder ID works.
If you had a static IP address, then you could set the Slingplayer to use a direct connection by using that IP address.
But, again, you should NOT need to do that. The Sling Finder ID should work just fine...assuming that you get everything setup properly.

[jgmorten]

I discovered that Slingbox can work with a dynamic IP address. I have tried to have the Westel router port forward directly to the SlingBox, but I'm concerned that the Airport Extreme(AEBS) may still be denying remote access to the Slingbox. The AEBS will only configure with connection sharing turned off (Bridge Mode). I had hoped this meant the AEBS was no longer a barrier. Sling comunity discussions have instructed a two router system requires both routers have port forwarding intiated, but AEBS in bridge mode does not offer a port forwarding option. I know just enough to be dangerous, so I'm sure there are many significant settings I'm failing to recognize. Your input would be appreciated.

[smax013]

Quote:

---

I discovered that Slingbox can work with a dynamic IP address. I have tried to have the Westel router port forward directly to the SlingBox, but I'm concerned that the Airport Extreme(AEBS) may still be denying remote access to the Slingbox. The AEBS will only configure with connection sharing turned off (Bridge Mode). I had hoped this meant the AEBS was no longer a barrier. Sling comunity discussions have instructed a two router system requires both routers have port forwarding intiated, but AEBS in bridge mode does not offer a port forwarding option. I know just enough to be dangerous, so I'm sure there are many significant settings I'm failing to recognize. Your input would be appreciated.

---

So, I will ask again:
What are the IP addresses of the two PeeCeee computers and the Mac? What IP address does the Airport Extreme show in the Internet connection window of the Airport Utility? What is the IP address of the Slingbox? If I am understanding your setup correctly, your modem also has a router built into it...and it is THAT router (not the AEBS) that is assigning IP addresses to everything. If so, then you should only need to get into the Westel's setup to forward port 5001 to the Slingbox's IP address. But, then I might not be understanding your setup.

[bobyau]

Not sure if people saw this yet, Slingbox has a decent video tutorial on how to setup your airport extreme router. I found it, took me 5 minutes. Open airport utility, click 1 thing type in 10 numbers and you're good to go.
http://www.slingmedi.../KB-005164.html