Link to home
Start Free TrialLog in
Avatar of John Crawford
John CrawfordFlag for United States of America

asked on

32 bit os machines can't access a windows 7 64 bit shares.

Howdy, I have xp 32 bit, w2k 32 bit, and windows 7 32 bit machines that cannot access shared folders or even connect via tcp to a windoes 7 64 acting as a small office server, any ideas?
Avatar of John
John
Flag of Canada image

The XP and Windows 2000 machines will have SMBv1 installed on them (dead, not updates) and Windows 7 got rid of SMv1. That is one reason.

Then Windows 7 32 bit must be Pro. and I assume Windows 7 64-bit is Pro.

On the 64-bit machine, Advanced Network Sharing Options: Make sure Network Discovery is ON, File and Print Sharing is ON, Homegroup is OFF, Password Protected Sharing is ON.

Now make a userid (users and groups) on the Windows 7 64-bit machine that is the username of the Windows 7 32-bit machine. Restart both and try sharing again.
Avatar of Wayne88
Running SMBv1 is not best practice or recommended but if you still want to proceed here it is:

To enable SMBv1 on the SMB1 in W7, run the following cmdlet.  Use Windows PowerShell or Registry Editor.  Windows PowerShell 2.0 or a later version of PowerShell:

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 -Type DWORD -Value 1 -Force

Restart the computer then test the folder share again.

Or you can simply go to this link (got to "Disable SMBv1 Hacks") download the file then click on the file named Enable SMBv1

https://www.howtogeek.com/321072/how-to-disable-smbv1-and-protect-your-windows-pc-from-attack/

Restart after applying the file.
Avatar of John Crawford

ASKER

What strange though is that these same 32 bit boxes can access all my other win 7 pro 64 machines via tcpip or computer browser. One day I was backing across the network to the win 7 pro acting as a main server to a attached USB drive and the next morning connections broken, its just to this one machine, I'll try the user id approach.
Perhaps because an overdue update was installed overnight blocking the share?  It's hard to tell without thoroughly inspecting log files, share permission, etc.  It can be anything.
All these machines have the built in administrator account. So if i try from logging in with a standard user or administrator still get the same results. The 32  bit boxes can ping the win 7 pro no problem. Also as i said the 32 bit boxes can also connect via \\XXX.XXX.XXX.XXX to another win 7 pro box without a hitch, theres something blocking in this win7 pro box  but i can't find it. It could be the firewall rules section so I will compare the list with the good win7pro box. By the way, the win7pro box that works has password protection OFF.
By the way, the win7pro box that works has password protection OFF.

Turn that ON because OFF turns on Home Group which may screw things up.

Make sure the two Windows 7 machines have user names AND passwords.
When using "sc.exe query lanmanworkstation" on the box acting as a server, I see a "running" state so I assume SMBv1 is on.  

I will change both win 7 pro workstations to password ON and keep my fingers crossed see what happens. This really appears to be a compatibility problem with 32 bit windows. On Windows 64 bit systems, they behave much better with browser issues.
Keep us posted. I share folders / files between machines a lot. But I have not used a 32-bit operating system for a decade.
ASKER CERTIFIED SOLUTION
Avatar of John Crawford
John Crawford
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Summary:  A USB with a shared folder had to be unshared, then drives physically detached. After rebooting desktop which is acting as server, computer can be access via computer browser services or tcp \\xxx.xxx.xxx.xxx