NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Cuzz
Jan 14, 2010Aspirant
Windows 7 Ult 64bit & ReadyNAS 1100 not connecting to shares
Hi,
I have been using the 4tb readyNAS 1100 on a domain for almost a year now flawlessly. We have over 20 workstations all Windows XP and several Windows servers from 2003-2008 all using the ReadyNAS 1100 daily. This has been and still is a great device.
I recently installed a Windows 7 ULT 64bit box on the network and have had no luck getting it to access any of the shares on the ReadyNAS device. It shows up in Network Discovery, Radiator, Frontview, http access, etc just not through cifs.
I've also added another identical Win 7 box which is experiencing the same connection issues.
I’ve spent the last 2 days searching the forums and trying all the suggestions from other posts like changing the local policy settings, trying almost all the different security/advanced options in frontview, updating the firmware to 4.1.6, all to no avail. Below is a snippet of the smdb.log file showing errors related to the Windows 7 box trying to connect and successful logs of windows xp boxes.
The support on these forums looks outstanding and I'm hopeful someone out here can help me :)
Thanks,
Brent
I have been using the 4tb readyNAS 1100 on a domain for almost a year now flawlessly. We have over 20 workstations all Windows XP and several Windows servers from 2003-2008 all using the ReadyNAS 1100 daily. This has been and still is a great device.
I recently installed a Windows 7 ULT 64bit box on the network and have had no luck getting it to access any of the shares on the ReadyNAS device. It shows up in Network Discovery, Radiator, Frontview, http access, etc just not through cifs.
I've also added another identical Win 7 box which is experiencing the same connection issues.
I’ve spent the last 2 days searching the forums and trying all the suggestions from other posts like changing the local policy settings, trying almost all the different security/advanced options in frontview, updating the firmware to 4.1.6, all to no avail. Below is a snippet of the smdb.log file showing errors related to the Windows 7 box trying to connect and successful logs of windows xp boxes.
[2010/01/13 15:25:42, 2] auth/auth.c:check_ntlm_password(309)
check_ntlm_password: authentication for user [Andrew] -> [Andrew] -> [SPC\andrew] succeeded
[2010/01/13 15:31:41, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 10.0.0.131. Error = Connection reset by peer
[2010/01/13 15:34:31, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 10.0.0.131. Error = Connection reset by peer
[2010/01/13 15:46:14, 0] smbd/server.c:main(942)
smbd version 3.0.34 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[2010/01/13 15:49:46, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 10.0.0.131. Error = Connection reset by peer
[2010/01/13 15:53:41, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 10.0.0.131. Error = Connection reset by peer
[2010/01/13 15:56:16, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 10.0.0.131. Error = Connection reset by peer
[2010/01/13 15:56:33, 0] smbd/server.c:main(942)
smbd version 3.0.34 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[2010/01/13 15:58:24, 2] auth/auth.c:check_ntlm_password(319)
check_ntlm_password: Authentication for user [Brent] -> [Brent] FAILED with error NT_STATUS_NO_SUCH_USER
[2010/01/13 15:59:21, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 10.0.0.131. Error = Connection reset by peer
[2010/01/13 16:01:01, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 10.0.0.131. Error = Connection reset by peer
[2010/01/13 16:02:21, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 10.0.0.131. Error = Connection reset by peer
[2010/01/13 16:08:46, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 10.0.0.131. Error = Connection reset by peer
[2010/01/13 16:20:39, 2] auth/auth.c:check_ntlm_password(309)
check_ntlm_password: authentication for user [Ronf] -> [Ronf] -> [SPC\ronf] succeeded
[2010/01/13 16:42:31, 2] auth/auth.c:check_ntlm_password(309)
check_ntlm_password: authentication for user [Andrew] -> [Andrew] -> [SPC\andrew] succeeded
[2010/01/13 17:00:04, 2] auth/auth.c:check_ntlm_password(309)
The support on these forums looks outstanding and I'm hopeful someone out here can help me :)
Thanks,
Brent
23 Replies
Replies have been turned off for this discussion
- ewokNETGEAR ExpertI'll ping them again and ask them to respond directly in this topic.
- bonezAspirant
ewok wrote: I'll ping them again and ask them to respond directly in this topic.
Many thanks for the follow-up! A quick in-advance note that I'm happy to get into nasty-low level details/invest in troubleshooting/logs/etc. - just say the word. - bonezAspirant
bonez wrote: ewok wrote: I'll ping them again and ask them to respond directly in this topic.
Many thanks for the follow-up! A quick in-advance note that I'm happy to get into nasty-low level details/invest in troubleshooting/logs/etc. - just say the word.
any luck, ewok? Still having the same issue and haven't been successful in finding a workaround. - Trial_MasterAspirantFYI - I've got Windows 7 Ultimate connected and working with both an NV+ and NVX
- bonezAspirant
Trial_Master wrote: FYI - I've got Windows 7 Ultimate connected and working with both an NV+ and NVX
64-bit?
The issue is with Win7-64bit; specifically, in non-domain mode with (password)-protected shares - both visible and hidden. If you've found a way for things to work, I'm all ears :) - Trial_MasterAspirantYeah 64-bit, I use Workgroup (non-domain) all shares are password protected. I don't know what to tell you I just set up the shares like I have in XP & Vista and it worked fine.
- bonezAspirant
Trial_Master wrote: Yeah 64-bit, I use Workgroup (non-domain) all shares are password protected. I don't know what to tell you I just set up the shares like I have in XP & Vista and it worked fine.
So strange. A few questions, if you don't mind:- How do you connect to the share on the ReadyNAS? (browse? UNC (e.g. \\readynas\share or \\192.168.1.101\share - name? IP?)
Do you get prompted for a username/password on connect? If so, what do you enter for username? (since not needed by the readynas) - anything special? like trying to reverse the domain of the user (e.g. username = readynas\username, password = the share's password)
Have you made the registry change to allow old-style encryption?
Do you have your ReadyNAS setup as a WINS server on your network?
ReadyNas firmware version?
thanks in advance if you're able to share.
-Bonez - Trial_MasterAspirantI connect using Mapped Drives I connect using either \readynas\share or \\192.168.1.101
I did get a prompt the first time I mapped the drive but I saved the Readynas user and password so the share auto connects.
Haven't made any registry changes
No WINS server, set up
RAIDiator 4.2.11 (x86) - bonezAspirant
Trial_Master wrote: I connect using Mapped Drives I connect using either \readynas\share or \\192.168.1.101
I did get a prompt the first time I mapped the drive but I saved the Readynas user and password so the share auto connects.
Haven't made any registry changes
No WINS server, set up
RAIDiator 4.2.11 (x86)
I don't have a ReadyNAS username...maybe it's because of the Readynas you have. I'm just in share mode. Also on RAIDiator 4.1.7-T29 [1.00a043] on an NV+. Ewok - maybe something fixed in 4.2.x is doing the trick? Any plans for it to come to the NV+?
(thanks for the response, Trial_Master) - Trial_MasterAspirantWhen i had my NV+ I ran it in User Mode so Shared Mode could be your issue?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!