Can't access unraid folders and files from Win10

[efrhm]

Hello,

I'm using unraid 6.2.2. About a week after upgrading to Win10 Pro Version 1607 build 14393.693 (upgrade from win7), and after a reboot to the PC, I was denied access to unraid folders and files. I even can't access the Web GUI from the browser by typing tower/. This is the message I get:

 

the requested URL /Main was not found on this server.

Apache/2.2.16 (Debian) PHP/5.3.3-7+squeeze19 with Suhosin-Patch Server at tower Port 81

 

Though I can access the Web GUI by typing the IP address directly.

 

Anyway, a list of things I've tried without any success:

1. Verified I'm signed as a local account and not as microsoft account

2. Add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters to the registry and set it's value to 1

3. Manually add Windows credential with both "Tower" + password and tower IP address + password

4. Desperately, reboot both PC and unraid server...

Any other suggestions I should try?

Thanks,

Haim

[John_M]

the requested URL /Main was not found on this server.

Apache/2.2.16 (Debian) PHP/5.3.3-7+squeeze19 with Suhosin-Patch Server at tower Port 81

 

That looks very much like the response from a different server that's running Debian Linux and not your unRAID server at all. Port 81? Have you changed it? By default unRAID uses port 80.

 

[efrhm]

I didn't changed it. As I said, I can access it by typing the IP address...

Actually, this is what i get while typing //Tower:

No site configured at this address

Typing http://tower/Main gets me the answer with Por t81

Any ideas?

[gubbgnutten]

If you open a command prompt and run

ping tower

does it show the expected address?

 

[efrhm]

I get a weird adrress when pinging tower:

Pinging tower.Home [173.45.161.113] with 32 bytes of data:

Reply from 173.45.161.113: bytes=32 time=158ms TTL=47

Reply from 173.45.161.113: bytes=32 time=158ms TTL=47

Reply from 173.45.161.113: bytes=32 time=166ms TTL=47

Reply from 173.45.161.113: bytes=32 time=158ms TTL=47

 

Ping statistics for 173.45.161.113:

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

Approximate round trip times in milli-seconds:

    Minimum = 158ms, Maximum = 166ms, Average = 160ms

 

Address should be 192.168.1.11

[trurl]

That address is not on your local network.

 

Do you have your server set as the local master in SMB settings?

 

See this sticky for more ideas.

[efrhm]

Yes. The server is set as the local master in SMB settings

[trurl]

Yes. The server is set as the local master in SMB settings

And is it actually the local master? Do you have the Dynamix Local Master plugin installed? It will show you which computer on your network is actually the local master.

 

Is "tower" actually the name of your server? If not that would definitely explain everything.

[gubbgnutten]

I get a weird adrress when pinging tower:

Pinging tower.Home [173.45.161.113] with 32 bytes of data:

Reply from 173.45.161.113: bytes=32 time=158ms TTL=47

Reply from 173.45.161.113: bytes=32 time=158ms TTL=47

Reply from 173.45.161.113: bytes=32 time=166ms TTL=47

Reply from 173.45.161.113: bytes=32 time=158ms TTL=47

 

Ping statistics for 173.45.161.113:

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

Approximate round trip times in milli-seconds:

    Minimum = 158ms, Maximum = 166ms, Average = 160ms

 

Address should be 192.168.1.11

 

Hmm. Don't like that at all...

 

Why tower.Home? 

 

If you run

ping i.dont.exist

does it also resolve to 173.45.161.113? Is something appended to it?

 

Edit: Don't have Windows 10 anywhere, so I can't be more specific, but I would verify the DNS settings (server, suffix, everything) and additionally make sure there are no toolbars, crap security software or other malware interfering with the settings.

[JonathanM]

Can't tell you exactly what's going on, but I've got a gut feeling it's your ISP's modem or router that's misbehaving.

 

If you want to solve the issue for that specific PC, you could always make a manual entry in the hosts file

192.168.1.11        tower

and that would solve the immediate issue, but only for the specific PC(s) that you make the hosts change.

https://support.rackspace.com/how-to/modify-your-hosts-file/

[efrhm]

Hi,

Thanks for all of you.

I have Dynamix Local Master plugin installed. It's shows that Tower is the current local master browser.

ping i.dont.exist returns:

Pinging i.dont.exist [173.45.161.113] with 32 bytes of data:

Reply from 173.45.161.113: bytes=32 time=161ms TTL=47

Reply from 173.45.161.113: bytes=32 time=159ms TTL=47

Reply from 173.45.161.113: bytes=32 time=157ms TTL=47

Reply from 173.45.161.113: bytes=32 time=158ms TTL=47

 

Ping statistics for 173.45.161.113:

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

Approximate round trip times in milli-seconds:

    Minimum = 157ms, Maximum = 161ms, Average = 158ms

same...

Pls bare in mind I can access the folders and files for a win7 machine

 

[efrhm]

OK, I've added 192.168.1.1 tower line to my windows host file. It immediately enabled me open the server GUI by typing tower/ at the address bar of my browser.

The folder and files weren't accessible as before, so i've deleted all credentials associated with the tower and tower ip address, rebooted the PC and everything is back to normal, everything looks fine. Great - thanks for you all. However. I believe i still have an inherent problem:

pinging tower works now fine

pinging i.dont.exist tries to ping that weird ip address,  [173.45.161.113], outside my network.

Any ideas?

[gubbgnutten]

OK, I've added 192.168.1.1 tower line to my windows host file. It immediately enabled me open the server GUI by typing tower/ at the address bar of my browser.

The folder and files weren't accessible as before, so i've deleted all credentials associated with the tower and tower ip address, rebooted the PC and everything is back to normal, everything looks fine. Great - thanks for you all. However. I believe i still have an inherent problem:

pinging tower works now fine

pinging i.dont.exist tries to ping that weird ip address,  [173.45.161.113], outside my network.

Any ideas?

 

There is a bad DNS server configured somewhere. Either on your Windows 10 machine, your router or your ISP.

 

What results do you get with ping on your Windows 7 machine?

[efrhm]

Win7 machine replies with Ping request could not find host i.dont.exist. Please check the name and try again

[trurl]

Could that be your WAN address?

[efrhm]

Not my WAN address

[trurl]

What does your Win10 computer have for DNS?

[gubbgnutten]

There are plenty of users complaining about non-existing addresses resolving to that particular IP, so I would suspect either some crappy security software gone awry, or malware. Unlikely to be due to the ISP since the Windows 7 machine can resolve things properly. Compare the DNS settings of the 10 and 7.

[efrhm]

Win10 has a Use the following DNS server addresses 208.67.222.222 ...

i switched to Obtain DNS server address automatically.

Nevertheless pinging elsewhere goes to [173.45.161.113]

[trurl]

I also suspect malware.

[gubbgnutten]

Win10 has a Use the following DNS server addresses 208.67.222.222 ...

i switched to Obtain DNS server address automatically.

Nevertheless pinging elsewhere goes to [173.45.161.113]

 

Sounds like OpenDNS. Famous for extending their DNS services with crap that breaks stuff.

 

Edit: You might need to reboot or wait for cached results to expire.

[Boo Eliot]

Hi there,

 

I just had to make a comment regarding this as I had the exact same problem for 2 months where trying to ping any non existent name or local machine name would return the IP [173.45.161.113] and it turned out to be Panda AntiVirus' URL safe web browsing and filtering.

 

Uninstalling this and also uninstalling the other parts of Panda to do with safe searching, but leaving the antivirus part itself installed fixed all the problems and now IP's resolve correctly again.

 

Hope this may help anyone else using Panda antivirus, as it was only after hours googling the ip address I found a whois lookup saying it was Panda ( [http://whois.domaintools.com/pandadomainadvisor.com] )

 

All the best

Boo