HD300 'Hostname' in System Info

[tvmaster2]

I got a used HD300 from another member here a while back, and am getting around to implementing it, except something is odd:

In the Setup Menu/System Information/System Status area, the HOSTNAME is listed as 'Tango3', which is I assume the last owners Server hostname?

Any idea how I get that to correctly read the hostname of MY server?

I've done a RESET of the HD300 I believe, so that wasn't it.

I also looked in the properties of my SageTV Clients folder, found the MAC address for this unit, but could find no line item for 'HOSTNAME' in the properties file.

Any ideas?

[graywolf]

The hostname of the HD300 is tango3

tango3[~]# cat /etc/hosts
127.0.0.1 localhost
127.0.0.1 tango3

[tvmaster2]

Originally Posted by graywolf

The hostname of the HD300 is tango3

tango3[~]# cat /etc/hosts
127.0.0.1 localhost
127.0.0.1 tango3

every HD300 in the world's hostname is tango3?
sorry, not following.

EDIT - just checked all my HD200's, whose hostname's are all STP-HD200. Naturaly I thought the HD300 followed suit. Apparently not, as I checked my older HD300... tango3.
What's up with that? Could be the stupidest thing to call the machine? There must be a reason...

[wnjj]

The hostname is only on your local network. I assume the 3 is because it's version 3. Tango3? I don't know. Maybe a reference to T3 (Terminator 3)?

[tvmaster2]

Originally Posted by wnjj

The hostname is only on your local network. I assume the 3 is because it's version 3. Tango3? I don't know. Maybe a reference to T3 (Terminator 3)?

But there's no way to change it to something meaningful? lol. Alpha, Beta, Charlie, Tango?

How about STP-HD300?

[wayner]

Originally Posted by tvmaster2

every HD300 in the world's hostname is tango3?
sorry, not following.

I thing what he means is that if you telnet into the HD300 (username root, no password required) you will see that the Hostname is tango3. This can be seen in the file /etc/hosts. If you change the name of the localhost in the hosts file to whatever you want then you may be able to change that name.

But why does it really matter? I am not sure that you will really see this anywhere and that is NOT the server, name just the default client name. But you likely won't ever see that unless you go to this System Status area of the extender, which you shouldn't ever have to do.

Note - to edit this you likely have to use vi as that is the only editor available in the Linux version on the extender. And vi is freakin' painful to use.

You may be able to edit it on a PC and SCP it over to the extender, but I am not sure that an extender accepts SCP connections.

Note - here is the hosts file on an HD200:

STP-HD200[/etc]# cat hosts      
127.0.0.1       localhost STP-HD200

To compare with what was posted above.

You also see this at the telnet login prompt. For a 300 you get "tango3 login:" whereas for a 200 you get "STP-HD200 login:"

Even if you can, you may not want to change this as there may be certain routines that depend on receiving tango3 to identify that it is an HD300. You may, or may not, be using such tools. I have written a groovy web utility that can list all of the SageTV clients and miniclients on your LAN and list the type of client. That utility will depend on this API extension which (I thiknk) was written by Slugger a few years back.

[tvmaster2]

Originally Posted by wayner

I thing what he means is that if you telnet into the HD300 (username root, no password required) you will see that the Hostname is tango3. This can be seen in the file /etc/hosts. If you change the name of the localhost in the hosts file to whatever you want then you may be able to change that name.

But why does it really matter? I am not sure that you will really see this anywhere and that is NOT the server, name just the default client name. But you likely won't ever see that unless you go to this System Status area of the extender, which you shouldn't ever have to do.

Note - to edit this you likely have to use vi as that is the only editor available in the Linux version on the extender. And vi is freakin' painful to use.

You may be able to edit it on a PC and SCP it over to the extender, but I am not sure that an extender accepts SCP connections.

Note - here is the hosts file on an HD200:

STP-HD200[/etc]# cat hosts      
127.0.0.1       localhost STP-HD200

To compare with what was posted above.

You also see this at the telnet login prompt. For a 300 you get "tango3 login:" whereas for a 200 you get "STP-HD200 login:"

Even if you can, you may not want to change this as there may be certain routines that depend on receiving tango3 to identify that it is an HD300. You may, or may not, be using such tools. I have written a groovy web utility that can list all of the SageTV clients and miniclients on your LAN and list the type of client. That utility will depend on this API extension which (I thiknk) was written by Slugger a few years back.

Thanks for this very thorough response. I guess you’re right - better just leave well enough alone. It’s just an odd thing to name it after the STP-HD200 seemed so logical.

[dstanley]

You need to stop the HD300 BEFORE it connects to the server to get to the system settings.
In the Main Menu go to the Settings option.
Select Advanced Setup
Go to the Server section
Set 'Windows File Server' to Enabled
Set 'Windows File Server Workgroup' to WORKGROUP (This is usually the default of any Windows installation)
Set 'Windows File Server Network Name' to your choice - apparently Tango3 in your case

Back your way out and reconnect to your server as usual.

Hope this helps.

[wayner]

Originally Posted by dstanley

You need to stop the HD300 BEFORE it connects to the server to get to the system settings.
In the Main Menu go to the Settings option.
Select Advanced Setup
Go to the Server section
Set 'Windows File Server' to Enabled
Set 'Windows File Server Workgroup' to WORKGROUP (This is usually the default of any Windows installation)
Set 'Windows File Server Network Name' to your choice - apparently Tango3 in your case

Back your way out and reconnect to your server as usual.

Hope this helps.

I don't think that's the same. Tango3 isn't the server name, it is the default client name for the HD300 extender.

[dstanley]

Just changed mine from its current HD300 to LIVINGROOM and that is what is says under System Status now for HOSTNAME

Image of system status

[tvmaster2]

Originally Posted by dstanley

Just changed mine from its current HD300 to LIVINGROOM and that is what is says under System Status now for HOSTNAME

Image of system status

Cool.

[KryptoNyte]

When an extender connects to the SageTV Server, and I bring up the Web UI on a local PC, I typically click on the client name and just change it there. Is this having the same effect?

[wayner]

Originally Posted by dstanley

Just changed mine from its current HD300 to LIVINGROOM and that is what is says under System Status now for HOSTNAME

Image of system status

Where did you change it? In the hosts file or somewhere else?

If you telnet does it give you a prompt like:
LIVINGROOM login:

[wayner]

Originally Posted by KryptoNyte

When an extender connects to the SageTV Server, and I bring up the Web UI on a local PC, I typically click on the client name and just change it there. Is this having the same effect?

Not quite the same. I do that for all of my extenders as well and that is the best way to keep track of them in the web UI if you have a lot - like I do.

[dstanley]

Works on my system - this is the Telnet screen from my MAC after I have changed the 'name' in the settings as my previous post.

IMG_0665.jpg

[wayner]

I just plugged in an HD300 extender that I bought used and when I telnet into it it has a hostname of JKITCHEN. As discussed in this thread, you can change the name in the extender standalone UI if you go into Settings/Advanced Setup/Server. You have to then Enable Windows File Server. When you do that you can change the Windows File Server Network name and it uses that for the hostname in the extender's Linux settings.

But when you change the settings it looks like you can only change to capital letters. I was trying to change it to tango3 as that is what all of my other servers have. But when I change it to tango3 when you telnet into the server it says TANGO3.

I tried changing the hostname via a telnet session, both by changing the entry in the hosts file to be tango3 and using the hostname command from the command prompt. But those changes do not stick. Somehow they keep getting reset to what was entered in the extender onscreen UI.

I don't know that this really matters, but I have some telnet scripts to automatically turn the extenders on and off, and I was worried that having a different hostname may screw up the telnet scripts if they have a waitfor"tango3") somewhere in them.

Hope someone finds this info useful...