I was reading through the release notes, and saw there was some change on the hostname reported back to the DHCP server. 

 

My router box is now calling the machine "hostname" instead of my whatever I put in the "Server Name" field, and changing the name didn't have any effect.

 

Anyone else seeing this?  My router is kinda a piece of $!#!, so might be just my setup....

You can check the actual config file on the flash drive.  Go to the config directory and open up the ident.cfg file in notepad and see what the values are.  Find the line that has  NAME="server name"

 

If its not set to the "server name" then for some reason it didn't take the update.  I just tried the web configuration page and it worked fine.  I also edited the ident file and that worked too.

I was reading through the release notes, and saw there was some change on the hostname reported back to the DHCP server. 

 

My router box is now calling the machine "hostname" instead of my whatever I put in the "Server Name" field, and changing the name didn't have any effect.

 

Anyone else seeing this?  My router is kinda a piece of $!#!, so might be just my setup....

 

That exact problem is fixed in -beta2, are you sure that's what you're running?

I'm seeing it here too.

 

I started with 4.3-beta1, changed the hostname to "Stacker".  Noticed that my router (which is running DD-WRT) said the hostname was set to "hostname".  I then upgraded to 4.3-beta2 by copying the new bzroot and bzimage files.  The web interface confirms that I'm running 4.3-beta2.  DD-WRT still thinks the hostname of unRAID is "hostname".  The "Stacker" hostname does work though, both in beta1 and beta2, as I'm able to type "stacker" in my web browser and it takes me right to the unRAID web interface.  I just checked, and ident.cfg has this line:

 

NAME=Stacker

I just checked my router running dd-wrt and it too says the name is hostname but when I use firefox and type backup it some up to my unraid box.  I tried hostname and it doesn't see it.  When I use tracert to backup it comes up but shows hostname ip address

 

It seems like a value isn't being passed right out of the server.

or there is need of flushing DNS?

 

(looks like that, I dunno how you do it on your routers)

 

 

Depending on your router, might not show up in it's list of attached devices until a different IP address is doled out, or router gets reset.

As far as I can tell, it didn't start happening to me until -beta2.  I upgraded to fix the user-share issue, and noticed that I couldn't access the box via hostname anymore, and had to use IP.  Didn't realize what happened until I read the release notes and saw the DHCP fix, then realized what might have happened and checked my router's DHCP assignments.  Tried changing the server name, and booted both it and the router to see if it was temporary.  In all tests, its name showed up as "hostname"

 

My ident.cfg looks good:

root@FServer:/boot/config# cat ident.cfg

# Generated names

NAME=FServer

COMMENT="Media server"

WORKGROUP=WORKGROUP

localMaster=yes

smbPorts="445 139"

timeZone=GMT+4

root@FServer:/boot/config#

 

I can try reverting it back to -beta1 as a test if useful....  Its vaguely possible that it first broke in -beta1 but the router didn't refresh its tables the 3-4 times I booted the unRaid box...

What happens if you just type in hostname at the telnet prompt?

 

unraid login: root
Linux 2.6.24.3-unRAID.
root@unraid:~# hostname
unraid

 

Isn't the hostname already shown in the prompt?  Though to be sure....

 

root@FServer:~# hostname
FServer
root@FServer:~#

 

What happens if you just type in hostname at the telnet prompt?

...

OK that looks good, Just checking.

I'm sort of baffled, I know DHCP clients have a way of announcing their host name to a DNS server, but I've never used that in my network. Everything for me is defined on the DHCP Server and NAME server.

This only has to do with the 'host name' given to the DHCP server for informational purposes - has nothing to do with system hostname or netbui name, etc.

Hmmm - after further testing, it seems like the dhcp hostname is getting borked for 4.3-beta2 & 4.3-beta3.  I think its broken for 4.3-beta1 as well, though not positive - I was getting conflicting results, and I'm too pooped to do more tests tonight.

 

4.2.4 looks seems fine though.

 

I realized my router actually allows me to rename the devices, so for now I've fixed it on that end.  Not a big deal.