|
|
|
Philips Pronto Professional Forum - View Post
|
|
|
|
|
|
|
The following page was printed from RemoteCentral.com:
TSU9600, wired RFX9400 fails through BT WAP
| |
|
Topic: | TSU9600, wired RFX9400 fails through BT WAP This thread has 4 replies. Displaying all posts. |
|
Post 1 made on Monday December 8, 2008 at 10:08 |
fungirlslim Lurking Member |
Joined: Posts: | December 2008 3 |
|
|
HI, sorry if this is basic, but had a system setup last year by a company, which worked great with a TSU9600 connecting to Dlink wirless router, connected to extender 9400 controlling devices. Had to change to a new wireless access point from BT which and it no longer works. Network and BT adsl see the extender ok, but the TSU9600 will not connect. When I plug dlink back in it works, so I think it may be to do with encryption on BT hub not allowing the TSU to connect to it wirelessly, the dlink had no security set.. can anyone help a beginner work this one out
|
|
Post 2 made on Monday December 8, 2008 at 21:34 |
avainnovations Long Time Member |
Joined: Posts: | October 2005 28 |
|
|
Is the network information the same (SSID name, encryption and IP settings). If you are not sure, copy the information from the D-Link and paste it into your new access point. Or, go into the setting screen on your 9600 to verify the network information that is programmed into the remote. That should work.
Otherwise, contact your installing company and have them edit your pronto file.
Good luck
|
|
Post 3 made on Tuesday December 9, 2008 at 08:10 |
buzz Super Member |
Joined: Posts: | May 2003 4,380 |
|
|
Some of those BT units are no fun at all. Check to see if yours is supporting enough HDCP clients.
As avainnovations suggests, probably the easiest solution is to turn OFF the BT's wireless, remove all of the wired devices, connect the WAN port of your D-Link to a network port on the BT, then connect the wired devices to the D-Link. At this point the D-Link becomes your wireless access point and router. Limitations of the BT unit are swept under the carpet.
|
|
OP | Post 4 made on Monday December 22, 2008 at 05:34 |
fungirlslim Lurking Member |
Joined: Posts: | December 2008 3 |
|
|
Thankyou both for replying, I have infact followed the route of removing the Bt to the back, again thanks
|
|
Post 5 made on Thursday December 25, 2008 at 17:22 |
GuerillaBuild Long Time Member |
Joined: Posts: | December 2008 79 |
|
|
If you're original setup was done by professionals, it is more than likely that some form of encryption key has been used to ensure that bad people stay out of your network. If you can see or ping the pronto, your network settings (IP, etc) are correct. What has potentially changed is the encryption key used (or not used.....) to access the wireless network. If your BT device uses WEP, WPA or WPA2 to act as a security guard against illegal access to your network, then you would need to update the Pronto with the new key. The Pronto only supports WEP, not WPA or WPA2. Thus if your BT device does not support WEP, you would need to disable encyrption. Please note that this is not a recommended option (disabling encryption) as it does leave a rather important door open to hackers.
Also extenders tend not to like DHCP allocated IP addresses as they can change from one session to the next. I would usually create a DHCP reservation for the device based on its MAC address and ensure that the same IP is always allocated to that device on connect.
|
You can hide almost anything until you have to put the drywall up! |
|
|
Before you can reply to a message... |
You must first register for a Remote Central user account - it's fast and free! Or, if you already have an account, please login now. |
Please read the following: Unsolicited commercial advertisements are absolutely not permitted on this forum. Other private buy & sell messages should be posted to our Marketplace. For information on how to advertise your service or product click here. Remote Central reserves the right to remove or modify any post that is deemed inappropriate.
|
|
|
|