Hi,

 

All of a sudden, I can't access my UNraid server. Using Windows explorer as normal, I just get an error message saying could not connect to tower. Connecting a monitor to the server shows this on the screen .

 

"Tower login: exportfs : warning : /mnt/user/music dvds does not support NFS export."

 

This is repeated a few times for different user shares.

 

I cannot enter any commands via the keyboard which is conected to the server. Re-booting doesn't help.

 

It looks like it might be something to do with nfs shares and I'd quite happily dissable them if I could only find a way to access the machine.

 

Please help.

Update. OK so now the keyboard is working for some reason. I can also access all the disk and user shares from my PC. But I still can't logon to the server either using tower or tower 8080 for UNmenu. Please help.

Further update. I can log on to the server by using the static IP address but not the name "tower". I've managed to turn off all the nfs shares and restarted the array, which has got rid of the error messages. I can log on to UNmenu by using the IP address followed by :8080 rather than tower:8080 which does not work. But non of the menu options in UNraid work any more. I can get to the main page but that's it.

Http://Tower:8080

 

Doesn't work any more. It used to.

 

http://192.168.1.50:8080'>http://192.168.1.50:8080 works (at least it gets me to the main page of Unmenu) but http://tower:8080'>http://tower:8080 does not work.

 

Also http://tower no longer works but http://192.168.1.50 does.

Sounds like it has something to do with the hosts file in windows, let me see if I can find that post

Try this

http://lime-technology.com/forum/index.php?topic=6915.0

 

C:\WINDOWS\SYSTEM32\DRIVERS\ETC

 

In that folder there is a file named

hosts with no extension. example NO .txt or anything of the sort.

 

I just put the following in it.

192.168.1.127 [TAB] Pizza

You sir, are a star. Thankyou.

 

That has indeed fixed the problem, although as the link suggests, it may be a "bandaid" solution to something else. I suspect the NFS share mesages were harmless and a red herring.

 

All I can say is thank God I'd already set the server up with a static IP address.

 

So, in summary I was unable to log on to my Unraid server using the name "tower" but the IP address worked. This also caused issues with UNmenu in that I could not log on using the name "tower:8080" but using the IP address followed by ":8080" worked. Also, none of the menu items in Unmenu worked because they were using the server name rather than the IP address.

 

The solution was to explore to C:\WINDOWS\SYSTEM32\DRIVERS\ETC and (using notepad) add the line "192.168.1.50  tower". i.e the static IP address follwed by at least 1 space and then the name tower.

 

I'm not sure if the cause of the problem is anything to do with my recetly upgrading from 4.5.4 to 4.5.6 but I didn't have the problem before. Or maybe it was caused when I started playing around with nfs shares ?

 

I use a Mac and had to do the same thing.  Joe L can probably tell you what the real problem is, he is the STAR not me, oh and Kizer for the original post

You sir, are a star. Thankyou.

 

That has indeed fixed the problem, although as the link suggests, it may be a "bandaid" solution to something else. I suspect the NFS share mesages were harmless and a red herring.

 

All I can say is thank God I'd already set the server up with a static IP address.

 

So, in summary I was unable to log on to my Unraid server using the name "tower" but the IP address worked. This also caused issues with UNmenu in that I could not log on using the name "tower:8080" but using the IP address followed by ":8080" worked. Also, none of the menu items in Unmenu worked because they were using the server name rather than the IP address.

 

The solution was to explore to C:\WINDOWS\SYSTEM32\DRIVERS\ETC and (using notepad) add the line "192.168.1.50  tower". i.e the static IP address follwed by at least 1 space and then the name tower.

 

I'm not sure if the cause of the problem is anything to do with my recetly upgrading from 4.5.4 to 4.5.6 but I didn't have the problem before. Or maybe it was caused when I started playing around with nfs shares ?

 

Everything you are describing seems to indicate your router is no longer routing.  (or the nameserver your PC uses has been hijacked by your ISP)  You might check your router. (or reboot it)

 

Joe L.

OK. This is kind of heavy stuff for an old guy who is a carpenter by trade. However, I've dug around in my BT Home Hub and found a list of devices. "Tower" did not appear anywhere on that list. However, within that list was the IP address I had assigned to my unraid server, but the name of the device was that of an old, "inactive" computer. I changed the name back to "Tower" and all now seems well. No idea how this managed to get screwed up.

OK. This is kind of heavy stuff for an old guy who is a carpenter by trade. However, I've dug around in my BT Home Hub and found a list of devices. "Tower" did not appear anywhere on that list. However, within that list was the IP address I had assigned to my unraid server, but the name of the device was that of an old, "inactive" computer. I changed the name back to "Tower" and all now seems well. No idea how this managed to get screwed up.

More than one device assigned the same IP address will certainly get things very confused.  Glad you figured things out.

 

  You're doing fine, regardless of your official "trade."  Perhaps somebody in your household plugged that old PC in recently, and it had been assigned the same IP address you had fixed in "tower", and it got your router confused.

 

Joe L.

Thanks Joe.

 

You got me thinking.

 

That old PC you mentioned has been gutted of it's original HDD and is now my "Tower" Unraid server fitted with 3 brand spanking new HDDS. Is it possible that the device name could somehow be stored in the original BIOs or the LAN card or some other component?

 

I'd have thought tearing out the HDD and running a new operating system from a USB flash would have go rid of any semblance of the PCs original identity. But it seems a bit spooky that the server name got changed to what this PC used to be "known as".