XigmaNAS

Posted: **07 May 2015 23:41**

I want to share a dataset with my Windows 8.1 computer, but the Win 8.1 can't find the server

This is the only thread that I could find related to Windows 8.1 and unfortunately, it didn't help.
viewtopic.php?f=21&t=8812

I've played around with quite a few settings and done some investigation with Win power shell and have discovered the following:

I have ensured that I am using the same workgroup name (ensuring it was a valid name [uppercase, no spaces]) and have rebooted both systems (not just the CIFS/SMB service) when trying different setting (this is a huge pain in the behind)
I can manually type \\<ip address> into explorer to find N4F and the share, but it's unable to find the server from its NetBIOS name (yes, on the same workgroup)
E.g. \\192.168.0.198 resolves, but \\ZEUS (NetBIOS name) does not.
I changed the workgroup so that the Win 8.1 and N4F computers were *not* on the same workgroup, and interestingly enough, the IP address still resolves, so it seems that regardless of the workgroup settings, you can find servers via their IP address. To me this isn't a solution, because, frankly, it should just work (I'm not pointing fault at N4F here, as this very well could be due to some setting on the Win 8.1 computer [which is basically a brand new and out of the box install]) and I don't want to have to manually enter the IP address. Also, when something in Windows isn't working, but there is some makeshift workaround, who knows what other things are still broken.
I have tried configurations of "Local Master Browser" both enabled and disabled and I see no difference
I have tested both Map to guest settings: "Never - default" (which isn't actually the default option) and "Bad User - non existing users" (this was the default option, at least for the current version 9.3.0.2.1391)
As discussed on previous topics:
"Never - default" works as a guest account
"Bad User - non existing users" requires a user to be added to "Access|Users" in N4F with the same credentials as the Windows login credentials (if you don't want to be prompted for a username/password every time)
I've tried adding the N4F server and then rebooting to see if it finds it after
Logging out of homegroup
I've settled on a workgroup name of ATLANTIS, because it will be like finding a lost city when I get this thing working

I've been using the following tools:

net view /domain:<workgroup>
net view \\<netbios name>
net view \\<ip addres>
lanscan from http://scottiestech.info/2009/02/14/how ... workgroup/
used to determine master browser

Note: N4F NetBIOS name is ZEUS and workgroup is ATLANTIS

Code: Select all

C:\>net view /domain:ATLANTIS
There are no entries in the list.

Very interesting is that my Win 8.1 machine [lenovo-pc] can't even find itself in the workgroup (gah… perhaps this isn't a N4F issue) if not and you can't really help, any forum recommendations? Perhaps eightforums?

Code: Select all

C:\>net view \\lenovo-pc
Shared resources at \\lenovo-pc



Share name  Type  Used as  Comment

-------------------------------------------------------------------------------
Users       Disk
The command completed successfully.

Clearly, it exists and resolves the NetBIOS name

Code: Select all

C:\>net view \\ZEUS
System error 53 has occurred.

The network path was not found.

Code: Select all

C:\>net view \\192.168.0.198
Shared resources at \\192.168.0.198

NAS4Free Server

Share name  Type  Used as  Comment

-------------------------------------------------------------------------------
SOCRATES    Disk           The unexamined life is not worth living
The command completed successfully.

Just saw that it could be an IPV6 issue https://www.readynas.com/forum/viewtopi ... 23&t=74923
I've also seen some other forums discuss something about relaxing permissions on the Windows 8 machine, but like they mention in the above post, this isn't desirable.

I've attached a the status report [HTML] from N4F as a zip, if that could help troubleshooting.

Posted: **08 May 2015 08:07**

what you can do is make sure that the name resolves to an ip address in your local lan.

i.e ping zeus resolves to something like zeus.localdomain and the dns server on your router returns an ip.

Posted: **08 May 2015 11:07**

Hello ,

You need to open these ports in your Router or at work ...

CIFS/SMB
139 netbios-ssn
445 microsoft-ds
Both UTP and TCP.

and check if there is a WINS Server on your Network. If it does then this is your problem.
if none of the above then it is a problem in your window's hosts.! Try to see the protocols installed on every machine in your network ...I know it is pretty awesome work but if it is a company problem then you should do it..!! GOOD LUCK.

Posted: **08 May 2015 16:25**

b0ssman wrote:what you can do is make sure that the name resolves to an ip address in your local lan.

i.e ping zeus resolves to something like zeus.localdomain and the dns server on your router returns an ip.

Nothing:

Code: Select all

C:\>ping zeus
Ping request could not find host zeus. Please check the name and try again.

C:\>ping nas4free
Ping request could not find host nas4free. Please check the name and try again.

C:\>ping 192.168.0.198

Pinging 192.168.0.198 with 32 bytes of data:
Reply from 192.168.0.198: bytes=32 time=1ms TTL=64
Reply from 192.168.0.198: bytes=32 time<1ms TTL=64
Reply from 192.168.0.198: bytes=32 time=1ms TTL=64
Reply from 192.168.0.198: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.198:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\>ping lenovo-pc

Pinging Lenovo-PC [fe80::49f9:6acd:414e:d17c%4] with 32 bytes of data:
Reply from fe80::49f9:6acd:414e:d17c%4: time<1ms
Reply from fe80::49f9:6acd:414e:d17c%4: time<1ms
Reply from fe80::49f9:6acd:414e:d17c%4: time<1ms
Reply from fe80::49f9:6acd:414e:d17c%4: time<1ms

Ping statistics for fe80::49f9:6acd:414e:d17c%4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

I came across this:

social.technet.microsoft.com wrote: Well the first thing to check is that they actually have Netbios over TCP/IP enabled!

The next thing is, are they in the same IP subnet? Routers usually block LAN broadcasts, and Netbios naming relies on that. In a routed network you need WINS (and at least one DC) to browse across a routed network. Netbios name resolution is an NT legacy system and relies on LAN broadcasts.

Is there an option for this in the NF4 GUI?

Posted: **08 May 2015 16:27**

you need to set up ip resolution in your router if it supports that or get a better one.

Posted: **08 May 2015 16:35**

b0ssman wrote:you need to set up ip resolution in your router if it supports that or get a better one.

I have a DIR-665, so I would assume that it is decent enough to do this. But before I go dive into that here are a few more examples just to see if it ip resolution is actually working.

Oops. I forgot to add these screenshots from the N4F server

ping zeus.jpg

ping nas4free.jpg

ping 192.168.0.198.jpg

ping 127.0.0.1.jpg

Also, does it mean that ip resolution is working if I can ping my own machine name?

Code: Select all

C:\>ping lenovo-pc

Pinging Lenovo-PC [fe80::49f9:6acd:414e:d17c%4] with 32 bytes of data:
Reply from fe80::49f9:6acd:414e:d17c%4: time<1ms
Reply from fe80::49f9:6acd:414e:d17c%4: time<1ms
Reply from fe80::49f9:6acd:414e:d17c%4: time<1ms
Reply from fe80::49f9:6acd:414e:d17c%4: time<1ms

Ping statistics for fe80::49f9:6acd:414e:d17c%4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Posted: **08 May 2015 16:38**

arxaios wrote:Hello ,

You need to open these ports in your Router or at work ...

CIFS/SMB
139 netbios-ssn
445 microsoft-ds
Both UTP and TCP.

I'll check this after a bit more testing, thanks.

arxaios wrote:and check if there is a WINS Server on your Network. If it does then this is your problem.
if none of the above then it is a problem in your window's hosts.! Try to see the protocols installed on every machine in your network ...I know it is pretty awesome work but if it is a company problem then you should do it..!! GOOD LUCK.

I just ran "ipconfig /all" and I didn't see a WINS server come up (this is how you look for it right?)

Posted: **08 May 2015 16:55**

jspen wrote:
I have a DIR-665, so I would assume that it is decent enough to do this. But before I go dive into that here are a few more examples just to see if it ip resolution is actually working.

d-link router have a terrible track record of security
see
http://www.cvedetails.com/vulnerability ... -link.html

and that router doesnt support openwrt/dd-wrt

Posted: **08 May 2015 16:59**

and the d-link router has its own samba server which can screw up the name resolution.

Posted: **08 May 2015 17:27**

b0ssman wrote:you need to set up ip resolution in your router if it supports that or get a better one.

So I think IP resolution is working (haven't chanced any router settings yet)

The Dude wrote:Look, man I've got certain information alright? Certain things have come to light
[…]
I got information man--new sh** has come to light!

OK, so check this out

I borrowed a windows 7 laptop with a machine name "Vaughan-Laptop"

Looks like the IP resolves for N4F and for the lenovo-pc (Win 8.1 machine) and this isn't even on the same workgroup

Code: Select all

C:\>ping zeus

Pinging zeus [192.168.0.198] with 32 bytes of data:
Reply from 192.168.0.198: bytes=32 time=1ms TTL=64
Reply from 192.168.0.198: bytes=32 time<1ms TTL=64
Reply from 192.168.0.198: bytes=32 time=1ms TTL=64
Reply from 192.168.0.198: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.198:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\>ping nas4free
Ping request could not find host nas4free. Please check the name and try again.

C:\>ping lenovo-pc

Pinging Lenovo-PC [fe80::49f9:6acd:414e:d17c%11] with 32 bytes of data:
Reply from fe80::49f9:6acd:414e:d17c%11: time=1ms
Reply from fe80::49f9:6acd:414e:d17c%11: time=1ms
Reply from fe80::49f9:6acd:414e:d17c%11: time=1ms
Reply from fe80::49f9:6acd:414e:d17c%11: time=31ms

Ping statistics for fe80::49f9:6acd:414e:d17c%11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 31ms, Average = 8ms

C:\>ping vaughan-laptop

Pinging Vaughan-Laptop [fe80::e4d3:f205:642e:5681%11] with 32 bytes of data:
Reply from fe80::e4d3:f205:642e:5681%11: time=1ms
Reply from fe80::e4d3:f205:642e:5681%11: time<1ms
Reply from fe80::e4d3:f205:642e:5681%11: time<1ms
Reply from fe80::e4d3:f205:642e:5681%11: time<1ms

Ping statistics for fe80::e4d3:f205:642e:5681%11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

I'm going to add it to the workgroup and see what happens

Posted: **08 May 2015 17:54**

b0ssman wrote:and the d-link router has its own samba server which can screw up the name resolution.

I'm looking at this right now. There's quite a bit of information out there on this, but I'm not coming across any settings I can change on the router.

Could the router messing with samba be the reason that things seem to be working smoothly for the windows 7 machine, but not for the windows 8 machine?

b0ssman wrote:d-link router have a terrible track record of security
see
http://www.cvedetails.com/vulnerability ... -link.html

and that router doesnt support openwrt/dd-wrt

Yeesh. Well, at least only DIR-655 listed is in an old firmware (and in the "B" hardware configuration, not the "A" that I have)

Posted: **08 May 2015 18:39**

So I joined the "ATLANTIS" workgroup on the Windows 7 pc and N4F shows up under "Network" in Windows Explorer.

The following commands also execute without a hitch:

Code: Select all

C:\>net view \\zeus
Shared resources at \\zeus

NAS4Free Server

Share name  Type  Used as  Comment

-------------------------------------------------------------------------------
SOCRATES    Disk           The unexamined life is not worth living
The command completed successfully.


C:\>LANscan_v1.57\lanscan.exe

LANscanner v1.57 - ScottiesTech.Info

Scanning LAN...

Scanning workgroup: ATLANTIS...

VAUGHAN-LAPTOP    192.168.0.194    00-1a-73-7f-50-a2  ATLANTIS  MASTER
ZEUS              192.168.0.198    0c-c4-7a-33-7c-48  ATLANTIS

Press any key to exit...

Interesting that lanscan run from the Win 7 machine finds two machines in the workgroup, but Windows Explorer, reports otherwise as shown in the picture (the Win 8.1 machine is present)

Vaughan-Laptop Network.png

Also interesting is that Lanscan run from the Win 8 machine shows nothing (not even itself) but again windows explorer seems to find a way to find the Win 7 machine (but not the N4F server *sad face*). Looks like some Windows sneakiness is going on.

Lenovo-PC Network.png

Win the Win 7 machine I was able to test that I can save files. I saved a test.txt to the dataset and was able to succesfully open it in the GUI "Advanced|File Editor"

Unfortunately, the Windows 8.1 machine still can't locate the share.

So where am I now? Does this mean that issues with the router can most likely be ruled out? And this is a home network, so I'm assuming I don't have a "WINS Server"?

Posted: **11 May 2015 10:45**

Try something different ...it is stupid but I do not see any reason why You shouldn't see the netbios name of your NAS4FREE....

Try accessing your nasfree using netbios from a Linux Desktop System .! (It is a thought I made ...!!) Post results please..!!

Posted: **11 May 2015 11:01**

Wait ...wait now I understand ... You have Win 7 and Windows 8 machines on the same Network ...!!!!

Then my friend you cannot see from both machines the same share from NAS4FREE BECAUSE in the settings in the CIFS/SMB there is a option Max Protocol you should have SMB3 for windows 8 , 8.1 machines only and if you want windows 7 machines then you should choose SMB2 . If that is the case make different shares for each O.S. (Operating System) you have. Do not forget to press save and restart after each change you made.

I hope I helped.

Posted: **14 May 2015 06:41**

I've just needed to take a bit of a break from this project. While I'm somewhat computer savvy, it's been quite a learning experience at nearly every step of the way.

arxaios wrote:Wait ...wait now I understand ... You have Win 7 and Windows 8 machines on the same Network ...!!!!

Well, actually, I just had the Win 7 laptop lent and used it to test some things. Initially the network consisted solely of Windows 8.1 and N4F.
I found it interesting though that while the machines could be viewed through Windows Explorer, the "net view" command could not locate the Windows 8.1 machine (either from itself, or from the Windows 7 computer)

arxaios wrote:Then my friend you cannot see from both machines the same share from NAS4FREE BECAUSE in the settings in the CIFS/SMB there is a option Max Protocol you should have SMB3 for windows 8 , 8.1 machines only and if you want windows 7 machines then you should choose SMB2 . If that is the case make different shares for each O.S. (Operating System) you have. Do not forget to press save and restart after each change you made.

I hope I helped.

I'll still try this hopefully in the next few days and I'll certainly report back

Posted: **17 May 2015 17:49**

Okay, so I was able to solve the issue.

arxaios wrote:in the CIFS/SMB there is a option Max Protocol you should have SMB3 for windows 8 , 8.1 machines only and if you want windows 7 machines then you should choose SMB2

Not too sure why, but I am still able to use Max Protocol = SMB3 and both the windows 7 and 8.1 computers are able to access the N4F shares.

Anyways, solving the issue was trivial; here's what I did:

I came across the following solution after doing some research indicating that NetBIOS over TCP/IP might not be enabled:

Unable to resolve one network name to an IP address on home network using one specific computer [experts-exchange.com] wrote:[…] if the computer was declared to be on a public network when it was first connected to the internet, netbios might not be enabled at all or may be firewalled

However, when I went to see if "NetBIOS over TCP/IP" was enabled, I wasn't even able to open the "Internet Protocol Version 4 (TCP/IPv4)" properties of my network adapter and received the following error:

Code: Select all

Microsoft TCP/IP
In order to configure TCP/IP, you must install and enable a network adapter card.

The following Microsoft support article suggested trying to unistall and re-install the network adapter.

Error Message: In Order to Configure TCP/IP, You Must Install and Enable a Network Adapter Card [support.microsoft.com] wrote:uninstall the network adapter in Device Manager, and then run the Add/Remove Hardware tool in Control Panel to reinstall the network adapter.

I joined the network, declared it a "Private Network", and everything started working swimmingly!

Posted: **19 May 2015 08:33**

So the problem was in windows ...( ha ha ha...) That is why I love Unix Systems ... never crash in software , only when the hardware fails..!!

XigmaNAS

[CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

[CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name

Re: [CIFS/SMB setup] Windows 8.1 unable to locate N4F via its NetBIOS name