Updating Firmware Through A Proxy

[EdwardATeller]

I have my HD Extender connected directly to my STV server via a crossover cable. Then the STV server is connected to the internet via a router through another NIC. I have the HD Extender settings pointing to the STV server's IP address, 192.168.4.101, in order to access the STV software. The STV server gets to the internet through 192.168.2.1.

I might be able to figure this out by trial and error, or maybe it's not possible. Can I set up the HD Extender network settings so that it can get to the internet through the STV server's connection? Thanks.

[reggie14]

It's probably not possible. Your server would need to be running proxy server software, and even then the HD extender would have to be proxy-aware, which it's not (to the best of my knowledge).

But, you could download the firmware file to your server, and use the recovery procedure to load it onto your HD100. That ought to work.

But, I have to ask, why not just hook the HD100 up to a switch and not have to worry about this stuff? You shouldn't need to segregate the HD extender bandwidth.

[EdwardATeller]

Thanks for the reply and saving me from trying something that probably isn't possible. I'll update once the new firmware is officially released.

My router is out of ports, but I do have an extra switch. I also thought I saw better performance with a direct connection, but I'll try it again.

[bcjenkins]

hmm.. The way you describe your connection doesn't indicate your HD Extender needs a proxy. Your PC essentially becomes a router for internal network segments.

Have you tried updating the firmware?

B

[reggie14]

Originally Posted by bcjenkins

hmm.. The way you describe your connection doesn't indicate your HD Extender needs a proxy. Your PC essentially becomes a router for internal network segments.

Are you sure? I don't think the computer will act like a router without running extra software. You might be able to run a software router on the server, as opposed to a proxy server, but I would think it would get more complicated than it's worth.

[bcjenkins]

A little trip to google land turns up this:

http://msmvps.com/blogs/nuoyan/archi.../05/69051.aspx

caveat: I don't know what OS (Pro/Home) the user has.

B

[reggie14]

Sounds like an interesting thing to try. This page gives some more details on how to set it up.

I'd be interested to hear if it works.

[EdwardATeller]

Originally Posted by bcjenkins

A little trip to google land turns up this:

http://msmvps.com/blogs/nuoyan/archi.../05/69051.aspx

caveat: I don't know what OS (Pro/Home) the user has.

B

I have XP Pro, and now my signature includes that info.

EDIT: I've tried enabling IP Routing in my STV Server with the registry edit, and the Extender still doesn't find the internet. Going to watch some Olympics now, and I'll work on this later.

[bcjenkins]

If you have another PC that you could hook up, I would make sure you can sort it out with that first. Also, try to telnet into the Extender and see what you can figure out from there.

If you wouldn't mind post some details about the network ranges and a route print statement.

B

[EdwardATeller]

Here are the details of my settings.

STV server NIC #1 connects to Router (192.168.2.1) which then connects to internet

IP - 192.168.2.113
Mask - 255.255.255.0
Gateway - 192.168.2.1
DNS - 192.168.2.1

STV server NIC #2 connects to HD Extender via crossover cable

IP - 192.168.4.101
Mask - 255.255.255.0
Gateway - BLANK
DNS - BLANK

HD Extender connects to STV server NIC #2

IP - 192.168.4.102
Mask - 255.255.255.0
Gateway - 192.168.4.101
DNS - 192.168.4.101

I enabled the IPEnableRouter switch in the registry and rebooted as suggested above, and I still can't get the Extender to do a firmware update through the STV server's internet connection.

I think I need to do something with the Gateway and DNS settings for the extender and NIC #2, but nothing I've tried has worked.

[bcjenkins]

Gateway is fine, but do a DNS change to the router's IP. Can you do a route print from the cmd line in XP?

B

[EdwardATeller]

Thanks. Which DNS should change to 192.168.2.1? NIC #2, Extender, or both?

[bcjenkins]

Both

B

[EdwardATeller]

I'll give it a try.

One other thing I was looking at yesterday was Internet Connection Sharing. Never tried it, but the NIC going to the internet does not currently have this option checked.

EDIT: Bingo! I think ICS really made the difference, or maybe it was just the last piece in the puzzle. Thanks for all the help.

[bcjenkins]

It looks like you're missing a route statement which connects 192.168.4.0 to anything else via 192.168.2.113.

B

[bcjenkins]

route help shows:

> route ADD 157.0.0.0 MASK 255.0.0.0 157.55.80.1 METRIC 3 IF 2
destination^ ^mask ^gateway metric^ ^ Interface^
If IF is not given, it tries to find the best interface for a given
gateway.

I am a little rusty on this, but:

route add 0.0.0.0 mask 0.0.0.0 192.168.2.113 metric 20 IF 192.168.4.101

If that works, run the same command with a -p to make it stick past reboots.

[EdwardATeller]

Really interesting stuff. I didn't know about ROUTE before this thread. Switching on Internet Connection Sharing and looking at the ROUTE PRINT output now, I see a path from the Extender's IP address to the STV's NIC #1 IP address. This is the NIC that goes out to the internet.

Bottom line, it works now with ICS, so I'll try your suggestion some time I'm feeling adventurous. Thanks for the help.