New Router Can't Connect to AzBox Premium Plus - Help Needed

[jsattv]

Today I replaced my 7 year old D Link Router with a new TRENDnet Router and so far I can't connect my AzBox Premium Plus Rx to this new Router when it is Password Protected. When the TRENDnet Router is NOT password Protected it works fine with the AzBox. I have tried just about everything and Nothing will work to the AzBox when Password Protection is in on the TRENDnet Router.

Also the WIFI password connection from the TRENDnet Router works to my Laptop, But not to my AzBox Rx. I have clicked on AzBox under Internet Connections for WIFI and Dynamic IP (DHCP) but when I Press "Setup" it says Not Able To Connect to Internet, also When I select System Info for the IP Setting it says 0000 Connecting?? Do I need to set up for Static IP, and do I need an IP connection for my new Wireless Connection? Also for my new Router the Listing is there for it on AzBox and it says: This Wi-FI requires Encription Setup. My Password for the Router was posted in the WEP Key Space, but it still doesn't work. Also does the WEP Key Password care if the ALL Caps are used in the Router Password ie is AzBox WepKey password case sensitive? Any help or advice would be much appreciated.

 

[Lone Gunman]

If this is a new router, then I'd see how good their tech support is! I've used Dlink, Cradlepoint and Linksys routers and they were/are pretty simple to setup. Never used a TrendNet so I got no clue about those.

I'd also consider making that AZBox IP static instead of dynamic if you're wanting to FTP to it. It's easier to do that if you already know the IP address and you don't have to make a new logins in Filezilla because that IP address never changes. After that connection is setup, FTP with Filezilla will just be a point and click from the "Quickconnect" drop down menu.

 

[jsattv]

If this is a new router, then I'd see how good their tech support is! I've used Dlink, Cradlepoint and Linksys routers and they were/are pretty simple to setup. Never used a TrendNet so I got no clue about those.

I'd also consider making that AZBox IP static instead of dynamic if you're wanting to FTP to it. It's easier to do that if you already know the IP address and you don't have to make a new logins in Filezilla because that IP address never changes. After that connection is setup, FTP with Filezilla will just be a point and click from the "Quickconnect" drop down menu.

Thanks a lot for the reply Lone Gunman. Trendnet's customer service were real helpful with my Desktop and Laptop's Router encripted connections, but the guy claimed he knew Nothing about Wireless Connections to Satellite Receivers. Mayby I'll call them again. I'll try the Static Connection also something doesn't seem right re my IP Setup on AzBox since when I go into "System Info" setting under IP it constantly says: 0 0 0 0 Connecting - so something is not right there. I do have Maz and ACC but they are currently Not able to connect to my AzBox Premium Plus - when they did before!! May have to look into a better Router ie Dlink, or Linksys?

 

[LocutusOfBorg]

I hope that you're not using WEP because it can be easily hacked. You should be using WPA2 instead. Anyway, the passphrase for the encryption key is case sensitive. If you're saying that you turned off the wireless encryption and the Azbox works OK then you're probably using the wrong wireless encryption passphrase. The Azbox won't draw a DHCP provided address if the encryption key isn't set right. If the passphrase isn't right, setting a static IP in the Azbox won't matter. Until the passphrase is correct you won't be able to associate with the WAP (wireless access point) on your router and that means you won't be able to connect to the LAN (intranet) or to the WAN (internet).

 

[jsattv]

I hope that you're not using WEP because it can be easily hacked. You should be using WPA2 instead. Anyway, the passphrase for the encryption key is case sensitive. If you're saying that you turned off the wireless encryption and the Azbox works OK then you're probably using the wrong wireless encryption passphrase. The Azbox won't draw a DHCP provided address if the encryption key isn't set right. If the passphrase isn't right, setting a static IP in the Azbox won't matter. Until the passphrase is correct you won't be able to associate with the WAP (wireless access point) on your router and that means you won't be able to connect to the LAN (intranet) or to the WAN (internet).

Thanks for the valuable info Johnnynobody.

 

[Cham]

Maybe try connecting using the 10/100 ethernet hard wire connection. If you get that working then go back to wireless.
Been using an Asus RT-N16 router with DD-WRT firmware but I don't bother with the wireless, way too slow for me. Wish they had gigabyte ethernet on these receivers though... No issues that way with security.

 

[jsattv]

Thanks for all the helpful comments JohnnyNobody and guys. Got the Encription working with the new Router using WPA and AES. Key info re JohnnyNobody was that the Paraphrase on AzBox Internet setup had to be Lower Case & I had it previously set to Upper Case on the Trendnet Router settings. Also with the new FW just released by Pwr Surge for the AzBox, the Wireless Internet Connection has never been faster ie up to 1.5MHz (with my new Internet Provider) and the Speeds are extremely fast on You Tube, great stuff - thanks all.

 

[wbarrett]

I messed up my AzBox and needed to reload the firmware. When I reloaded off a USB drive, I found the wireless would not work just as described above.

I tried rolling back from 5402 to 5309 and back to 5402 and could not get wireless to connect. The box would see my network but would not connect. I could not get DHCP or static IP to connect. The symptom was like my password was wrong but it was not.

What finally worked for me was to fill in a static IP, mask, DNS and gateway as I had many, many times. I used my DNS 1 server of 192.168.1.1 but instead of using 0.0.0.0 for DNS 2 I used the Google DNS of 8.8.8.8. It connected right up and has worked since.

Coincidence? Maybe. But for anyone having wireless connectivity issue, this is worth a try. Don't leave DNS 2 at the default 0.0.0.0.

===
Bill

 

[LocutusOfBorg]

What finally worked for me was to fill in a static IP, mask, DNS and gateway as I had many, many times. I used my DNS 1 server of 192.168.1.1 but instead of using 0.0.0.0 for DNS 2 I used the Google DNS of 8.8.8.8. It connected right up and has worked since.

You should never use 192.168.1.1 (i.e. don't use your routers LAN address) for your DNS server setting on the Azbox. That address worked on my Azbox but the network ran extremely slow. Anyway, you should use the DNS servers that are provided by your ISP - these can be manually entered if you're setting up a static address for your Azbox - be sure to setup the gateway address to point to the routers LAN IP address (usually 192.168.1.1). If your local network DHCP server (which is probably running on your router) was setup properly you should have got your DNS fields filled in correctly with your ISP's DNS server addresses. Don't get your ISPs DHCP server confused with the routers DHCP server. Your ISPs DHCP server provides the WAN address for your router while the routers DHCP server provides addressing for devices on your LAN. And you should avoid using Googles DNS service - your ISPs DNS servers will give better performance.

 

[wbarrett]

Thanks, johnnynobody. I'll play around with the settings and see what impact they have.

I actually do not use the AzBox for YouTube or browser functions anyway; just FTA reception. So since my access is only local FTP to manage the three key files, the DNS tied to local router has never been a performance issue. The thing that made me move from the ISP DNS is the annoying habit mine has of changing the IP addresses without warning.

That said, there is no reason to not optimize network performance so I'll give the changes suggested a shot. ;-). Regardless of what DNS is used, I still found that I needed both DNS addresses filled in to get wireless to work with AzBox after doing an application area format and firmware reload.

===
Bill

 

[LocutusOfBorg]

The thing that made me move from the ISP DNS is the annoying habit mine has of changing the IP addresses without warning.

The DNS addresses that you get from your ISP shouldn't be changing but your WAN IP address may change when the lease renewal is executed. The ISP DNS server IP addresses are static addresses. But, you'll probably get the same WAN IP address when the lease renewal is executed (but that's not guaranteed). Since the ISP DNS server addresses are static addresses you should never have a problem with surfing the web or connection problems with the router when the WAN IP address is changed.

 

[wbarrett]

Thanks, johnnynobody. I made your suggested changes... do not see any improvements in networking speed but your information makes logical sense so I'll file this in my "best practices" toolkit. ;-)

===
Bill