I have a properly running version of 5.05.  I recently changed my wireless router with which I access the server.  The server I might add is hardwired to the router.  I just access the server with a WiFi connected laptop.  I cannot access it now using http://tower/.  Instead I have to access it using its ip address.  The same condition exists if I try to log on to it using Putty.

 

Using a Linux box (Linux Mint on another partition on the same laptop), there is no problem.  I guess something happened that Windows cannot access it.

 

Any ideas how to fix the access via Windows?

Some points to check:

On the Linux machine what does the following commands return?

# host tower
# cat /etc/hosts

 

 

On the windows machine what does the following command return?

 

# nslookup tower
# ping tower

 

 

C:\Windows\system32>nslookup tower

Server:  cellspot.router

Address:  192.168.29.1

 

*** cellspot.router can't find tower: Non-existent domain

 

C:\Windows\system32>ping tower

 

Pinging tower [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time=10ms TTL=63

Reply from 192.168.1.2: bytes=32 time<1ms TTL=63

Reply from 192.168.1.2: bytes=32 time=1ms TTL=63

Reply from 192.168.1.2: bytes=32 time=1ms TTL=63

 

Ping statistics for 192.168.1.2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 10ms, Average = 3ms

 

C:\Windows\system32>

 

Strange to get the two different results.  I updated the windows hosts file so to at least be able to effectively ping tower.

 

 

Some take away points here:

[*]Windows (and the system components like ping, explorer, maybe IE) can also use smb broadcast and queries to resolve a host name to its IP, besides the usual DNS and hosts file lookups

[*]Your router might not support dhcp based dynamic dns for your LAN (most consumer routers and a number of enterprise routers don't)

[*]Adding the resolution of your unraid server tower to the Windows hosts file should solve your issue and allow browsers like Chrome and Firefox to resolve the httpo://tower to unraid server

Is it working for you now?

 

 

Some take away points here:

[*]Windows (and the system components like ping, explorer, maybe IE) can also use smb broadcast and queries to resolve a host name to its IP, besides the usual DNS and hosts file lookups

[*]Your router might not support dhcp based dynamic dns for your LAN (most consumer routers and a number of enterprise routers don't)

[*]Adding the resolution of your unraid server tower to the Windows hosts file should solve your issue and allow browsers like Chrome and Firefox to resolve the httpo://tower to unraid server

Is it working for you now?

 

Adding the ip address and the machine name worked in Chrome and other browsers.  NSLOOKUP still no effect.  Oh well Works=Good!

Hmm. I neglected to mention that nslookup ignores the hosts file as its supposed to ask a NameServer (DNS server) about the NAME and its IP addresss. At least your problem got solved.