I know similar threads exist and I've gone through some of those, but I think this is slightly different.  I also updated from 4.3.3 to 4.4.2, although this problem occurred in both.  I recently moved and had to setup my system again.  The problem I'm having is that I cannot connect by sever name (http://tower).  I can connect with the ip address, so the web interface is running and everything looks fine.  I can also see the server in Explorer (\\tower works just fine).  I can telnet to the ip address, but not the server name.

 

I switched to static ip address, but that made no difference.  I ran the ps -ef command in telnet and emhttp is running, of course, since I can connect by ip address.

 

Connecting by ip address isn't the worst thing, but UnMenu won't work since it tries to connect by server name.

 

Attached is my syslog for reference.

 

Thanks!

 

The most common reason for that is answered here:  "Why does //tower not work in my browser?"

 

Connecting by ip address isn't the worst thing, but UnMenu won't work since it tries to connect by server name.

I believe others are using UnMENU with the IP address.  If I remember right, you can access your UnMENU with 192.168.0.11:8080.  It is possible that you have to edit the unmenu.conf file though, but I don't think so (I could be wrong!).

 

Just a few suggestions:

* According to the syslog, your motherboard has 4 IDE channels (potentially supporting 8 IDE drives).  You have one drive on IDE0, and both of the others are on the same cable, on IDE2.  It would be better to add another cable for the third drive, so it will have an IDE channel to itself.

* You have added a nice higher performance Intel gigabit card, but are only connecting at 100mbps.  I don't know if you are aware of that or not.

* You have NTP time support turned on, but it does not work in that version without some special commands.  I would suggest you upgrade to v4.5-beta6, which has fixed a number of things including the NTP support.

Thanks.  But, I'm not using a Mac.  Those posts pointed to Mac not recognizing NETBIOS, but it didn't give any detail.  I'm using WinXP, could this be a NETBIOS issue and, if so, what do I look at?

 

For UnMenu, 192.168.0.11:8080 works, but the links at the top point to tower:8080.  I looked at unmenu.conf and changed MyHost to 192.168.0.11, but that didn't work.  Does UnMenu need to be restarted to read the change?  Can I restart it (how?) or does the system have to be rebooted?

 

Thanks for looking for other issues.

*I'll look into the IDE cable. 

*Unfortunately, all my other computers, switches and routers are 100mbps.  I hope to upgrade someday.  On a related note, I use RoboCopy to copy over files and it reports copying at about 450MB/min.  If I calculated it right, a 100mbps network's maximum throughput is 750MB/min (100mbps / 8 bytes/bit * 60 secs).  Given that I'm going through a switch and router, plus not the best cables, this seems reasonable, don't you think?

*I'll look into upgrading to 4.5-beta6

 

Thanks for your help!

 

I had this problem with XP. There are some relevant parts in the links in the FAQ which are operating system independent. For me what worked best was to reserve the IP address for tower in my router and then add that address to the hosts file on the XP machine.

 

In addition to solving the access issue with the links in unMenu, it also made access a lot snappier since it didn't have to look up the address for tower.

For UnMenu, 192.168.0.11:8080 works, but the links at the top point to tower:8080.  I looked at unmenu.conf and changed MyHost to 192.168.0.11, but that didn't work.  Does UnMenu need to be restarted to read the change?  Can I restart it (how?) or does the system have to be rebooted?

You do have to kill and restart UnMENU, but I think I was wrong to suggest that editing unmenu.conf might help.  I think razmajazz's advice is better.

 

*Unfortunately, all my other computers, switches and routers are 100mbps.  I hope to upgrade someday.  On a related note, I use RoboCopy to copy over files and it reports copying at about 450MB/min.  If I calculated it right, a 100mbps network's maximum throughput is 750MB/min (100mbps / 8 bytes/bit * 60 secs).  Given that I'm going through a switch and router, plus not the best cables, this seems reasonable, don't you think?

That is a decent speed for 100mbps.  Because of overhead and collision handling, you can't actually get the max anyway.  The number we use around here for a maximum is 10MB/sec, which is about the best you can expect for Fast Ethernet, at 100mbps.

For UnMenu, 192.168.0.11:8080 works, but the links at the top point to tower:8080.  I looked at unmenu.conf and changed MyHost to 192.168.0.11, but that didn't work.  Does UnMenu need to be restarted to read the change?  Can I restart it (how?) or does the system have to be rebooted?

to stop unMENU, easiest for most people will be to log in via telnet and type:

killall awk

 

To start it back up again, use the same command you used the first time.

If you put its files in a /boot/unmenu directory, you would type:

/boot/unmenu/uu

 

Oh yes, when you edited MyHost in the unmenu.conf, you should have removed the proceeding "#" on the line that comments out the value for most people.

It should have looked like this:

MyHost=192.168.0.11

 

You also need to use an editor that does not put carriage returns at the ends of the lines.  (Many windows editors do this)

Thanks, raz, that works.  But, I have a feeling I'm just masking a problem that will come up again.  If it's not an UnRaid problem, then it's something with my network setup.  Oh well, I'll just happily use it until something happens.

 

Thanks, joe, I wasn't sure how to kill UnMenu.  But, raz's suggestion fixes it, too.  So, no need for me to set the myhost variable.

 

Thanks, raz, that works.  But, I have a feeling I'm just masking a problem that will come up again.  If it's not an UnRaid problem, then it's something with my network setup.  Oh well, I'll just happily use it until something happens.

 

Thanks, joe, I wasn't sure how to kill UnMenu.  But, raz's suggestion fixes it, too.  So, no need for me to set the myhost variable.

 

Glad you are now working... Those "links" at the top of unMENU have some pretty interesting features.

 

It is true, it is normally your router's job to map the tower name to the IP address.  There are times I've had issues here when the local Time-Warner-Cable/RoadRunner decided to route any unknown URL to their search page/advertisements.  That drove me crazy, as attempts to get to "tower" went there instead of to the local machine.  I found I had to "opt-out" of their forced URL redirection to get things working properly again.  It was even worse with me trying to use VNC to get to machines on my LAN, none would connect until I opted-out of the forced URL capture.

 

Perhaps your ISP is doing you a "favor" too.

 

Joe L.

Perhaps your ISP is doing you a "favor" too.

 

I don't think that's the case.  I have my router set to use OpenDNS instead of Cox's DNS.  It's the same setup that worked before I moved.  The only difference is the cable modem, a Motorola SB5101, and the hardware setup is switched up a bit (same hardware, though).

 

 

I wondered if you were using OpenDNS. So was I. In troubleshooting my access problem I verified that switching to my ISP's (Comcast) default DNS server was a solution and I used that for a while. I modified the hosts file for speedier browser updates a little later and as a side benefit discovered that I could switch my router back to OpenDNS.

 

So it seems OpenDNS is somehow involved. It may be possible to resolve the issue by creating an account with them and modifying some settings but I haven't pursued that.