HD100 cant access internet - help!

[infocus13]

Hi guys

Here's my problem. My HD100 can't access the internet for firmware updates. Not a major problem, but has been bugging me for ages so hoping someone can help!

Here's my setup.

SageTV server:
dual core intel running a headless sagetv server (sagetv v6.6.2). The server has two NICS. One is a DLink WLAN which is connected to my Netgear wireless modem/router - this is mainly for internet access for the sagetv server (epg, online vids, etc) as well as wireless media file access for my laptop. The wireless NIC has a static IP of 192.168.0.4, subnet 255.255.255.0, etc.

The server also has a wired gigabit LAN (built into the motherboard). This goes into a netgear GB switch which feeds the HD100 as well as a desktop PC in the same room. The wired LAN has an IP of 10.0.0.1 and a subnet mask of 255.0.0.0.

The different ip ranges and subnet masks are due to the fact that I couldnt run two NICS on the same PC in the same IP range, etc. I would get either IP conflicts on my network or trying things like network bridging, etc would not work.

HD100 extender
The extender is set to use a static ip of 10.0.0.3 and a subnet mask of 255.0.0.0 it can see the server fine, can connect & can access online content in Sage once connected. Problem is that the extender cant see the internet when in the firmware update screen.

I'm assuming the problem is due to different IP ranges and different subnets - the private subnet (255.0.0.0) has no way to access or see the internet-exposed subnet (255.255.255.0).

My question is - how can I route the traffic/IPs on my sage server from one subnet to another to enable the private subnet to access the internet so that my HD100 can get firmware updates.

Please note that this setup is necessary due to the physical setup/layout of my house - unfortnuately I cant just directly plug the hd100 into a router, etc.

Any help is much appreciated. Thanks in advance.

[gplasky]

Well you've answered your own question. You gave the HD100 the IP and subnet for the private subnet which has no internet access. Give it an IP and subnet for the public subnet. Bridge the two NICs if you have to for the HD100 to get out.

Gerry

[infocus13]

Thanks Gerry - have tried that.

Giving the wired NIC in the server a public ip range and subnet (i.e. 192.168.x.x) kills internet access on the server - cant access any sites in IE, etc. The only way around this is the private subnet.

Giving the hd100 a public IP also prevents the hd100 from seeing the sage server. can't pickup the server no matter how many times I hit refresh.

Bridging the connections on the server also doesnt help - doing this kills internet access on the server as well and my network bridge is unable to get a proper DHCP IP from my router - the bridge properties keeps showing "invalid ip" and repairing the bridge results in an error "unable to renew IP address".

any other ideas?

[gplasky]

Doesn't your router have any switch ports on the back? If it does set the HD100 to DHCP and plug it in. Also what OS?

Gerry

[infocus13]

Problem is router cant reach the HD100 - cabling and apartment layout restrictions.

OS is windows XP, SP3 all updates applied.

Unless there's something obvious I can do to fix my problem I'll just buy a really long phone cable to put the router near the HD100 as a once off to update the firmware. Not an elegant solution though!!

[carlgar]

Originally Posted by dkatchalov

Thanks Gerry - have tried that.

Giving the wired NIC in the server a public ip range and subnet (i.e. 192.168.x.x) kills internet access on the server - cant access any sites in IE, etc. The only way around this is the private subnet.

Giving the hd100 a public IP also prevents the hd100 from seeing the sage server. can't pickup the server no matter how many times I hit refresh.

Bridging the connections on the server also doesnt help - doing this kills internet access on the server as well and my network bridge is unable to get a proper DHCP IP from my router - the bridge properties keeps showing "invalid ip" and repairing the bridge results in an error "unable to renew IP address".

any other ideas?

You currently have a class C network of 192.168.0.x and a class A network of 10.x.x.x. Your use of 192.168.x.x would be an invalid class B network. You should change your class A network to a second class C of 192.168.1.x. You could then bridge the two class C networks.

[gplasky]

Your other option is to use the recovery option:

If the STX-HD100 still does not respond, then you can perform the recovery procedure listed below.

Recovery Procedure
Download the following file to the SageTV folder on your server. Place the file in the same directory where sagetv.exe is located.
http://download.sage.tv/firmware/stx1000.bin
Make sure the SageTV software is running on your server and is configured to be able to talk to extender clients, as mentioned above.
Turn off the STX-HD100 at the switch.
Press and hold down both the Menu and OK buttons on the front panel while turning on the switch.
Continue pressing both the Menu and OK buttons on the front panel until the DATA (or ACTIVE) light turns on. Once that light turns on, you can let go of the Menu and OK buttons.
The lights on the front will blink during the update procedure.
The unit will reboot itself automatically when done with this update and should then be running.

This is the latest firmware:
http://download.sage.tv/firmware/stx1000beta.bin

For manual installation via the HD100's "Recovery Procedure" in the above FAQ, download this file, remembering to rename the file to match the FAQ's instructions:
stx1000.bin


Gerry

[infocus13]

Thanks Carlgar.

What about the subnet masks for both networks - do I maintain 255.0.0.0 for the class A and 255.255.255.0 for class B?

Gerry - that also sounds like a good alternative/option. Will try this tonight.

[carlgar]

You should not have a Class A network but 255.0.0.0 is correct for one.
Class B networks have a mask of 255.255.0.0 and as you probably already know class C networks have a mask of 255.255.255.0.
You can have as many as 255 class C networks for you own use.

[infocus13]

Just to update - i changed both networks to class C, bridged the connection on the server and voila - the hd100 can now receive updates.

thanks Gerry and Carlgar for your help.