Ok I have had enough of this. I have Windows 7 Ultimate box. Just want to map a drive to Unraid Share.

 

\\192.168.20.22\Video_and_Movies

 

I have setup Unraid according to the video examples online. unRAID Server Basic version: 5.0-beta2

 

Spend 4 hours on the forums and online trying to figure this out.

 

We are all in the same network 192.168.20.X on the same switch.

 

I can ping 192.168.20.22 (Unraid server)

 

I can ping tower (again unraid server)

 

I can ping myself (192.168.20.

 

I have done this with static address and DHCP.

 

We are all on the same workgroup. (WORKGROUP) Unraid is configured for this.

 

UNRAID is set to Local Master = Yes

 

Error Message: Windows cannot access \\192.168.20.22 - Check the spelling of the name. Otherwise there might be a problem with your network. To try to identify and resolve network problems, click Diagnose. Of course that doesn't do squat. It stated the error message instantly.

 

In windows explorer I click on Network Icon and on the right is my PC (Jimbo-PC) Click on that and I get that same error.

 

I am at a loss. This should be so easy? What am I missing? Any help is welcome.

 

Jimbo

 

I have done the following:

 

Network and Sharing Center -> Change from128-bit to lesser encryption.

 

I also changed these Security Settings

- Local Policies

-- Security Options

--- Network security: Minimum session security for NTLM SSP based (including secure RPC) clients

---- Uncheck "Require 128-bit encryption"

--- Network security: Minimum session security for NTLM SSP based (including secure RPC) servers

---- Uncheck "Require 128-bit encryption"

 

Enable or disable network discovery. In fact I enabled everything here.

 

Tower login: root

Password:

Linux 2.6.32.9-unRAID.

root@Tower:~# ifconfig

eth0      Link encap:Ethernet  HWaddr 00:0c:6e:fa:7c:03

          inet addr:192.168.20.22  Bcast:192.168.20.31  Mask:255.255.255.224

          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:6963 errors:0 dropped:0 overruns:0 frame:0

          TX packets:709 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:654576 (639.2 KiB)  TX bytes:291649 (284.8 KiB)

          Interrupt:22 Base address:0xe000

 

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:8 errors:0 dropped:0 overruns:0 frame:0

          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)

 

root@Tower:~#

 

shouldn't the netmask on the unRAID server be 255.255.255.0 ?

 

Joe L.

I have a small network so I dont have to use a 254 node subnet.

 

What ports numbers does Unraid or Windows 7 use to facilitate communication?

Port 80 and 8080

 

http://lime-technology.com/forum/index.php?topic=8159.msg78972#msg78972

Port 80 and 8080

 

http://lime-technology.com/forum/index.php?topic=8159.msg78972#msg78972

That is not even close to being all inclusive and a correct answer to the question being asked.  Port 80 is the default port used by the unRAID web-server. 

Port 8080 is the default port used by the unMENU web-server.    Port 89 is the one used by default by the unRAID-Web lighttpd web-server.  In addition to those is a whole host of other ports used.  Note I do not use NFS, so it will not show below.

 

[code]root@Tower:~# netstat -an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 0.0.0.0:37              0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:45836           0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:21              0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:23              0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:3551            0.0.0.0:*               LISTEN
tcp        0      0 192.168.2.100:60462     192.168.2.110:445       ESTABLISHED
tcp        0      0 192.168.2.100:23        192.168.2.6:53011       ESTABLISHED
tcp        0      0 192.168.2.100:23        192.168.2.6:51304       ESTABLISHED
tcp        0      0 192.168.2.100:445       192.168.2.110:36787     ESTABLISHED
tcp        0      0 192.168.2.100:23        192.168.2.6:50463       ESTABLISHED
tcp        0      0 192.168.2.100:445       192.168.2.6:49156       ESTABLISHED
udp        0      0 192.168.2.100:137       0.0.0.0:*
udp        0      0 0.0.0.0:137             0.0.0.0:*
udp        0      0 192.168.2.100:138       0.0.0.0:*
udp        0      0 0.0.0.0:138             0.0.0.0:*
udp        0      0 0.0.0.0:37              0.0.0.0:*
udp        0      0 0.0.0.0:717             0.0.0.0:*
udp        0      0 0.0.0.0:111             0.0.0.0:*
udp        0      0 0.0.0.0:58618           0.0.0.0:*
udp        0      0 192.168.2.100:123       0.0.0.0:*
udp        0      0 127.0.0.1:123           0.0.0.0:*
udp        0      0 0.0.0.0:123             0.0.0.0:*

[/code]

 

Just to throw this out there, saw VERY similar thing with my local Win7 boxes accessing a Windows Home Media server, which they all accessed fine a few days prior. I assume this due to a windows update. Changed the following in secpol:

Security Settings -> Local Policies -> Security Options:

Network Security: LAN Manager Authentication Level

 

Changed it to "Send LM & NTLM - use NTLMv2 sessions security if negotiated"

 

Reboot and all worked. The issue was the local Win7 box was trying to do a v2 NTLM only and of course, WHS doesn't support. Sounds very similar.

 

Cheers