Router and TV Portal

Petrus Jag

New Member
Newbie here, and very green.
Been reading about wireless conections on here, and have tried to connect my HDR to the TV Portal, with some success.

Hardware

HDR, Edimax usb adapter, Belkin PLAY N600.

I have had the portal working with wired connection no problem.
When I connect using wireless, it connects to the router, but will not connect to the TV Portal.
I have 65 mbps which should be plenty. I have rebooted the HDR a few times with no change.

Also I cannot pick up the HDR looking through network on computer (is this relevent).

As I said I am very green when it comes to connections and all Abbreviations that go with it.

If anyone could help that would be great (Be kind)
Thanks
Pete
 

Ezra Pound

Well-Known Member
You can check to see if basic communications can be made to your Humax by having a PC that is connected to the same router as your Humax and then going to START >> Run >> [enter cmd in the run window] >> OK, you will now get a new screen / window and a '> prompt' enter ping 10.0.0.200 where the numbers 10.0.0.200 are replaced by the IP address of you Humax,you should get something like This :-
ping.jpg

Try this with both wired and wireless connections to your Humax, Note the IP address will change when switching from cable to wireless
 

Ezra Pound

Well-Known Member
Are the IP address for wired and wireless in the same group? e.g. both starting with 192.168.169, your router may-be preventing the Wi-Fi USB dongle access to the internet for some reason
 

Ezra Pound

Well-Known Member
So if looks like your wireless router has a wired network on 192.168.2.XXX and a wireless network on 192.168.169.XXX My guess is that there is some setting on your router that allows address's on 192.168.2.XXX to access the internet but not items on the wireless network of 192.168.169.XXX
 
OP
P

Petrus Jag

New Member
Ok looked at my client list on the server and wired and wireless devises have 192.168.2.XXX IP addresses. I have the humax wired at the moment and there is no host name either.
Why is this when humax sends 192.168.169.XXX when wireless. Any ideas on what to do next
 

Black Hole

May contain traces of nut
What does your router say about the Humax's IP address (identifiable by MAC address if not name)? Could your router be responsible for treating the Humax wireless connection as suspicious, and not allow it access to the Internet?
 
OP
P

Petrus Jag

New Member
In LAN settings the IP pool starting and ending Addresses are 192.168.2.2-100 so the humax wireless ip is outside these ie 192.168.169.XXX.

how do i change the humax ip address to be within the ip pool on the router?

Do I have to turn off the DHCP function and put in a manual ip address within the pool?

Am I barking up the wrong tree?

Help!

P.s The humax shows up on the DHCP client list with the IP address 192.168.169.XXX. and MAC address but no host name, so it can see it.
 
OP
P

Petrus Jag

New Member
Hi Black hole, I would not know how to look at what router is saying about the humax other than in the security log, and there is only the following related to the ip address of the humax. Ignore the date .Hav not changed it.
3 07:58:21 router daemon.info udhcpd[27530]: sending ACK to 192.168.169.2
Jan 3 07:58:21 router daemon.info udhcpd[27530]: check_conf_ip_assign s Sat Jan 3 07:58:21 1970
Jan 3 07:58:22 router daemon.info udhcpd[27530]: check_conf_ip_assign d Sat Jan 3 07:58:22 1970
Jan 3 07:58:22 router daemon.info udhcpd[27530]: sending OFFER of 192.168.169.2
Jan 3 07:58:22 router daemon.info udhcpd[27530]: received REQUEST
Jan 3 07:58:22 router daemon.info udhcpd[27530]: sending ACK to 192.168.169.2
Jan 3 07:58:22 router daemon.info udhcpd[27530]: check_conf_ip_assign s Sat Jan 3 07:58:22 1970
Jan 3 07:58:22 router daemon.info udhcpd[27530]: check_conf_ip_assign e Sat Jan 3 07:58:22 1970
Jan 3 07:58:22 router daemon.info udhcpd[27530]: sending ACK to 192.168.169.2
Jan 3 08:00:00 router daemon.info udhcpd[27530]: received DISCOVER
Jan 3 08:00:00 router daemon.info udhcpd[27530]: sending ACK to 192.168.169.2
Jan 3 08:00:00 router daemon.info udhcpd[27530]: check_conf_ip_assign s Sat Jan 3 08:00:00 1970
Jan 3 08:00:00 router daemon.info udhcpd[27530]: check_conf_ip_assign d Sat Jan 3 08:00:00 1970
Jan 3 08:00:00 router daemon.info udhcpd[27530]: sending OFFER of 192.168.169.2
Jan 3 08:00:00 router daemon.info udhcpd[27530]: received REQUEST
Jan 3 08:00:00 router daemon.info udhcpd[27530]: sending ACK to 192.168.169.2
Jan 3 08:00:00 router daemon.info udhcpd[27530]: check_conf_ip_assign s Sat Jan 3 08:00:00 1970
Jan 3 08:00:00 router daemon.info udhcpd[27530]: check_conf_ip_assign e Sat Jan 3 08:00:00 1970
Jan 3 08:00:00 router daemon.info udhcpd[27530]: sending ACK to 192.168.169.2
Jan 3 08:00:02 router daemon.info udhcpd[27530]: received DISCOVER
Jan 3 08:00:02 router daemon.info udhcpd[27530]: sending ACK to 192.168.169.2
Jan 3 08:00:02 router daemon.info udhcpd[27530]: check_conf_ip_assign s Sat Jan 3 08:00:02 1970
Jan 3 08:00:02 router daemon.info udhcpd[27530]: check_conf_ip_assign d Sat Jan 3 08:00:02 1970
Jan 3 08:00:02 router daemon.info udhcpd[27530]: sending OFFER of 192.168.169.2
Jan 3 08:00:02 router daemon.info udhcpd[27530]: received REQUEST
Jan 3 08:00:02 router daemon.info udhcpd[27530]: sending ACK to 192.168.169.2
Jan 3 08:00:02 router daemon.info udhcpd[27530]: check_conf_ip_assign s Sat Jan 3 08:00:02 1970
Jan 3 08:00:02 router daemon.info udhcpd[27530]: check_conf_ip_assign e Sat Jan 3 08:00:02 1970
Jan 3 08:00:02 router daemon.info udhcpd[27530]: sending ACK to 192.168.169.2
Jan 3 08:03:19 router daemon.info udhcpd[27512]: received REQUEST
 

Black Hole

May contain traces of nut
If this were a LAN connection, I would expect to have DHCP turned on and to be allocated a suitable IP address (192.168.2.x) or set manual and configure an IP address (keeping fingers crossed it did not clash with something else). We have seen cases where a manual setting went haywire when a HomePlug link failed, and when the Humax was (somehow) not compatible with a TP-LInk router (solved by routing it via another router).

Regrettably I can't help with the WiFi side; unless I disconnect my LAN and plug in a WiFi adapter the WLAN settings are inaccessible. If it does allow you to set the IP address manually, try it.
 

MartinLiddle

Super Moderator
Staff member
The manual for the Belkin Play N600 talks about guest access; it says "A person using your guest network will be able to join
without a password, but will be shown a login page when they attempt to surf the Web." I suspect the Humax is getting guest access. You need to get it full access. perhaps security type is wrong?
 
OP
P

Petrus Jag

New Member
It is not connected to the guest. It gives me the choice on the wi-fi settings page, and I chose the secured network.

I changed from DHCP to manual and put the gateway and dns the same as wired connection and gave the humax a ip address 192.168.2.20. Nothing else near that number on the network. It connected, but when I refreshed the client list it still came up with the old IP address 192.168.169.2. and would not connect to TV portal.
Any thing else i can try?

Can't help feeling I'm missing a very simple trick here:(
 
OP
P

Petrus Jag

New Member
disabled guest account on the router to see if the password account was piggy backing the guest account, and bingo can no longer connect with router:mad:
Getting a little wound up now:frantic:.

Any ideas as to why my humax will not connect wirelessly with the router?

Now i have disabled guest I can no longer change to manual fromDHCP on the wireless settings. Only available on LAN
 
OP
P

Petrus Jag

New Member
Ok. Very embaressed right now.:oops:. The old uppercase lowercase password Jem. online now. Sorry to have wasted all of your day off chaps.

Next challenge using xbmc
 
Top