Hi all, I have just configured my wireless extender in network mode with a fixed ip. The Power and Ethernet LED are green so everything seems to work. I have put the right settings in ProntoEdit at System Properties as well. And added the wireless extender. My TSU9600 doesnt show a wifi icon and it keeps on saying communicating... Every command fails as well. Can anyone help me please?

Not enough information for us to help you.

What extender?
What firmware on Extender?
What are the switches on back of Extender set to ?

What firmware on Pronto?

What Router?
What firmware on Router?

Also, have you searched this forum for any posts related to network connectivity problems

This might be too obvious, but I'm guessing that by network mode you mean a wired connection since you mention the Ethernet LED is on. This means that the extender cannot communicate directly with the TSU9600 over Wi-Fi, only via an Access Point, which you don't mention is present.
So is it possible you are expecting the extender to act as Access Point to the TSU9600? (Regrettably the RFX9400 cannot do this).

I always get frustated by people who start a thread and do not add sufficient information. Now I did the same myself, sorry for that.
- I have a wireless RFX9400 extender
- A TSU9600
- A wireless network, Sitecom router
( I suppose you dont need any more info, but it is just a stupid mistake of me.)

I want to control only the living room with my pronto.

I did the following:
- Plugged in Laptop with PEP2 via ethernet cable in the Router.
- Plugged in the Extender via ethernet in the Router.
- Switched Extender to 3
- PEP2: discovery tool, the extender appeared, I clicked Configure.
- Browser openend, I didnt mess with te SSID and encryption, but I did click 'Fixed IP' with the following setting: IP: 192.168.1.1 , Netmask: 255.255.255.0 (Was aleady there) , Gateway: blank.
- I released the pc from the router.
- Switched extender to 1
- Ethernet and Power LED turned green.

In PEP2:
- Network settings (system properties)> Use network mode > SSID: Broeck WEP64, Pasword: ***** , Fixed IP: 192.168.1.1.
- Add extender and clicked the RSX9400.
- On every page I use 'As system properties'

_______________________________________________________________

Maybe I can better configure in stand alone mode, considering I have only one room?

Thanks for you help again.

So if im following you correctly there, you have assigned the extender 192.168.1.1 through the web browser set up page.

then in PEP2 you have assigned a 192.168.1.1 address too?

which window of PEP2 is that you have added that IP address?
along side where you entered the SSID info? or in the pop window for adding extenders?

if is the first option there then you have assigned the remote the same IP address as the extender hence why the remote is not getting an IP address and not working as the extender already has it.

also most routers have a factory assigned address of 192.168.1.1. so your probably having issues there too.

Also you should log into the router and find out what the DHCP range is set to and make sure your pronto hardware is set out of it to prevent conflicts when the router gets a DHCP request.

so if your router has a DHCP range of 192.168.1.2-192.168.1.50 then set the pronto address as eg. 192.168.1.100 and 192.168.1.101. either address for either item, doesnt matter which way around.

Yes you are correct, I have assigned the extender in the browser to ip 192.168.1.1 and in PEP2 I went to System properties > Network > Wireless > With wireless extender in network mode > SSID Broeck, Encryption WEP64, Password ****. IP setting: Fixed IP: adress: 192.168.1.1
In the pop window for adding extenders I did not add 'Fixed IP'

DHCP Address Router: 192.168.1.100 - 192.168.1.200

instead of using 'for example' , could you just tell me what to fill in? Thanks for you help already.

ok then, to start im gonna say that the IP address of your router is 192.168.1.1.

first change the address of the extender to
IP Address: 192.168.1.10
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.1
DNS: 192.168.1.1

then in PEP2 in the spot next to where you have entered your SSID info enter the following to assign an address to the remote:
IP Address: 192.168.1.11
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.1
DNS: 192.168.1.1

click the "add extenders" button on the same window in PEP and click the "use fixed IP address" button on the extender that you are using and enter 192.168.1.10 into there.

after that you should be ready to roll.

if your router does happen to have an assigned address of 192.168.1.10 or 192.168.1.11 then post back ill let you know what to change in the above.

hope that gets you going.

Thanks for you help, but it still doesnt work. I have configured the extender again. Do I need to fill in the SSID and Wep in the browser? ( I let the settings leave on Ethernet). The Control Panel still says Command failed, I have even turned it off an on again. Do I have to fill in my SSID and Wep in PEP2? Now I did fill it in in PEP but not in my browser. Is that what Im doing wrong?

yes you need to enter the SSID and WEP password into PEP2 only, no need to enter it into the extender setup as its connected via ethernet.

do you definately have the extender ID switch set to the same as in PEP?

what does the wifi indicator on the remote show?
press and hold the backlight-menu-2nd firm keys to open up the diagnostics menu, does it show anything in there?

did you check the IP address of your router?

There is no Wifi indicator, the router IP is definately 192.168.1.1.

Maybe I should just try Stand alone mode.. ?

hrm there should be, next to the battery indicator.

im out of ideas right now, when i get to the office tomorrow ill have another look when ive got a remote in front of me too.

I'm not sure if this will work for you, but try setting your router to 'OPEN' for the password type under WEP settings and not 'SHARED'. You might even have a setting called 'BOTH'. That should work as well. I had a similar situation. It took me forever to find the answer.

Also, vdUnkown, don't apologize for leaving your info out of your initial post. It cracks me up on forums like these, where the idea is to provide help, and so many of these so called weirdos immediately reply with unhelpful, rather rude comments. My favorite comment from these idiots is "search the site". No kidding......... My policy is if you don't know the answer or don't want to contribute something positive to a particular post, then shut the heck up and don't respond. To me it seems that in most cases, an educated guess can be made as to what the problem is, based on the information given by the original poster. (DVWEBSTER tried to help). But of course, the wannabe 'experts' instead of typing a potential solution, types nonsense. Calm down 'experts'..... It's only a remote. Not life or death.

|There is no WiFi indicator, the router IP is definitely 192.168.1.1.
|



Well, if what you said above is true, then your problem is blatantly obvious. Look at the IP range of your router. ANY NODE ON YOUR LAN HAS TO HAVE AN IP ADDRESS WITHIN THAT DHCP RANGE, WHETHER THE NODE(S) ARE SET UP FOR DHCP OR STATIC IP.

If you set up the RFX on ethernet, and then plug it into your network, and use WiFi on the controller, your ethernet settings on the controller and on the RFX need to match what your router is allowing for traffic. If they're different, the controller won't communicate...

What's more is that you need to make sure that the WEP settings match on the controller with what's broadcast from your router (if it's your WiFi point) or WAP. On top of that, the router or WAP might not communicate with the controller if it is set on a "mixed" broadcast mode. I have a Belkin N1 router at home, and my controller won't communicate with it if the router is set to b,g,n broadcast. It ONLY communicates if the router is set to g only.


By the way, yeah, that's me shouting above. I am trying to piss off the douche above (itsonly) that had to make a new name instead of posting under his real name. Grow some stones dude.

^^^DISCLAIMER^^^
Not directed at anyone on this board, so don't get all upset.

There are a lot of people on here that need to be led around by the hand, that spend so much time asking questions, that they could use less time and learn for themselves. Men built all this stuff, so men should be able to figure it out.

There are other people that figure things out, to the extent that they can, and then ask for help. That's okay- it's how you learn.

I don't mind helping at all (have done it quite a bit), and am sure that I have asked a few stupid questions here and there. We all have a good grasp on one thing or another, and help each other where we can.


^^^END DISCLAIMER^^^


Again, if anyone (itsonly) took the time to read through the posts above, they'd have noticed the posts where the problems are located with this configuration.
If he has a working knowledge of IP configuration, or just paid attention, he might have been able to actually contribute instead of just wasting time bitching.

Now, I have spent about fifteen minutes of my time on here holding hands (which is no big deal) because somebody else decided to be a smart ass.

By the way, to the OP, if you need any more help on this, let me know. I'd be happy to help educate you, so that you can then help somebody else.

Hey Evohome, you are right, the router was set to Mixed, I have changed it and everything works! You are a hero. I didnt expect this topic would lead to this, still I want to thank everyone with their effort and trying to help me (though it didnt always have success). Anyway, Im really happy it works!

vdUknown-good to hear you got it sorted.

evohome-quick question for you here, you mentioned "ANY NODE ON YOUR LAN HAS TO HAVE AN IP ADDRESS WITHIN THAT DHCP RANGE, WHETHER THE NODE(S) ARE SET UP FOR DHCP OR STATIC IP"

the poster mentioned "DHCP Address Router: 192.168.1.100 - 192.168.1.200"

i would understand that as the range of addresses that the router will use for DHCP addresses, you will still have between .2 to .99 and .201 to .254 addresses that can access the network and communicate with each other.
also that you should ALWAYS use address outside the DHCP range when using static address for some items on your network to prevent IP conflicts.

thats what i been taught just tryign to clarify it and thats how i have my network set up and it works fine????