1namyln
asked on
Windows 7 machine won't access network devices
I have a Windows 7 Home Premium machine. I'm unable to access a NAS via its UNC or IP. I can view the NAS via its webportal. I can access the NAS either way via another computer. I have removed the Norton software completely and disabled the Windows firewall during my troubleshooting.
I have set the network to home. I am connected to a printer via IP also.
I have set the network to home. I am connected to a printer via IP also.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sorry, I didn't mean to tell you to stop the Windows Firewall service - that can have unpredictable results for network operations. So please start it again, but keep it disabled (for the moment).
Try if the following gives you a result:
telnet YourNASIP 139
You should get a console where you can type in (nothing returned). Stop the connection by pressing Ctrl+Plus, and typing quit.
Try if the following gives you a result:
telnet YourNASIP 139
You should get a console where you can type in (nothing returned). Stop the connection by pressing Ctrl+Plus, and typing quit.
ASKER
I'm unable to connect using \\mycomputername or \\127.0.0.1.
If you can access the web portal I might think it could be a permission problem.
Make sure the permission is set. For testing purposes add "everyone" to the acess list.
Make sure the permission is set. For testing purposes add "everyone" to the acess list.
ASKER
Permissions error on the NAS? I can access it from other computers with no issue. XP and Windows 7. If you're referring to the users and groups in the Buffalo software I can't add everyone without a password.
ASKER
I can ping the name of the device and its ip.
What about http:#a38308166 ?
ASKER
The link posted is a link to this page.
ASKER
When I type telnet ip 139 into a command prompt another black window pops up with telnet myip at the top but it just stays there. Nothing happens. The windows stays black and displays no further text.
That is to be expected. If you type in that window, nothing happens (in particular the window does not close)? If the window does not close, either kill it or press Ctrl+Plus, then type quit (as described in my prior comment).
The window remaining open means that the connection to the NAS works on the old SMB port (139/tcp). Then I'm supposing the W7 machine tries with CIFS (445/tcp), and does not fall back to the "conventional" SMB protocol ports ...
The window remaining open means that the connection to the NAS works on the old SMB port (139/tcp). Then I'm supposing the W7 machine tries with CIFS (445/tcp), and does not fall back to the "conventional" SMB protocol ports ...
ASKER
Still no resolve. I needed this functionality so I could backup to the NAS. The backup program can also backup via FTP. I enabled this on my NAS and I'm able to work around it for now.
ASKER
Sweet! Thx. I don't feel neglected. I always feel like I get my $13 bucks worth. :)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Please check on Windows 7 Home Premium machine
Control Panel |Credential Manager
Remove any stored credential for that NAS.
Create one new user that has same username and password as other windows 7 machine on which you are able to access the NAS.
Control Panel |Credential Manager
Remove any stored credential for that NAS.
Create one new user that has same username and password as other windows 7 machine on which you are able to access the NAS.
I would upgrade to windows 7 pro instead of home it has better networking capabilities.
If your system is Windows 7 Home Premium, you may change it from Registry.
1. Launch regedit from Start Search box.
2. Find the following branch.
HKEY_LOCAL_MACHINE\SYSTEM\ CurrentCon trolSet\Co ntrol\Lsa
3. Create a DWORD key under Lsa and set:
Name: LmCompatibilityLevel
Value: 1
4. Restart."
Source: http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/91fe4e10-a0d4-45db-94df-fad885d8f64f
If your system is Windows 7 Professional, try the following:-
1. Run secpol.msc and a window called "Local Security Policy" will be open;
2. Goto Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Network security: LAN Manager authentication level
3. Change the default value of "LAN Manager authentication level" to "Send LM & NTLM - use NTLMv2 session security if negotiated:"
4. Restart
1. Launch regedit from Start Search box.
2. Find the following branch.
HKEY_LOCAL_MACHINE\SYSTEM\
3. Create a DWORD key under Lsa and set:
Name: LmCompatibilityLevel
Value: 1
4. Restart."
Source: http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/91fe4e10-a0d4-45db-94df-fad885d8f64f
If your system is Windows 7 Professional, try the following:-
1. Run secpol.msc and a window called "Local Security Policy" will be open;
2. Goto Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Network security: LAN Manager authentication level
3. Change the default value of "LAN Manager authentication level" to "Send LM & NTLM - use NTLMv2 session security if negotiated:"
4. Restart
ASKER
Jackieman, I'll try this and repost. Should be late this evening. Thanks.
Please read my post. I guarantee it is your problem! http:#a38309724
ASKER
Davis, I did everything except remove the Norton. This customer wants to maintain their Norton. I agree its crap but...
In Norton, then, you need to create a trusted network. How you do it depends on the version. Which version of Norton?
ASKER
Internet Security, the latest version. Earlier in my post though I mentioned removing Norton completely, using the removal tool, and still couldn't access via unc or IP.
But the network location is now "Work"?
As long as the network type or location is Home, Windows will outsmart you. You must change it to a Work network.
Norton's network "trust" settings will also put the kabosh on viewing network devices (other than printers or routers) so you'll need to set that, too: https://www-secure.symantec.com/norton-support/jsp/help-solutions.jsp?ct=us&lg=en&product=home&pvid=f-home&version=1&docid=v15978324_NIS_Retail_2012_en_us
Norton's network "trust" settings will also put the kabosh on viewing network devices (other than printers or routers) so you'll need to set that, too: https://www-secure.symantec.com/norton-support/jsp/help-solutions.jsp?ct=us&lg=en&product=home&pvid=f-home&version=1&docid=v15978324_NIS_Retail_2012_en_us
ASKER
Jackieman, tried the registry changes, no change. Davis, verified Work network and added network to trusted within Norton. No change.
So when you open the network and sharing center, double-click the center icon at the top, and let Windoze scan the network, nothing appears?
Are there other PC's on the network?
Are there other PC's on the network?
ASKER
I can see one pc. If I click start the type \\unc or \\ip for the computer that I can see when I click the network I get the same error as if j types the nas or other devices.
ASKER
The nas and the computer in question are I'm the same workgroup.
ASKER
As a reminder I can't access the PC using \\myunc or \\127.0.0.1. However a ping to either replies successful.
ASKER
I'm unable to share on this system. When I attempt to share I get the same type error. This action can't be completed on this system. I have created another user with admin permissions to see if its specific to the user but I have the same problems.
"Earlier in my post though I mentioned removing Norton completely, using the removal tool" -> Have you reestarted the computer before you tried to access the NAS?
ASKER
Yes.
Was there another antivirus product in the past?
CA, Trend Micro, and McAfee all love to only partially uninstall and leave network sentry drivers behind.
To check, do Start, and in the search box type CMD <CTRL-SHIFT-ENTER> to open an elevated CMD window. In it, type:
set DEVMGR_SHOW_NONPRESENT_DEV ICES=1
devmgmt.msc
Then, in the Device Manager, click View -> Show hidden devices.
What you will have is a device manager which shows every device Windows ever detected rather than one which shows what is there now.
Check the non-plug-and-play section for MFE, NAI, SYM, T?, and VET entries. If they are all grayed out, yeah (!); but, if any are not, run their removal tool.
CA, Trend Micro, and McAfee all love to only partially uninstall and leave network sentry drivers behind.
To check, do Start, and in the search box type CMD <CTRL-SHIFT-ENTER> to open an elevated CMD window. In it, type:
set DEVMGR_SHOW_NONPRESENT_DEV
devmgmt.msc
Then, in the Device Manager, click View -> Show hidden devices.
What you will have is a device manager which shows every device Windows ever detected rather than one which shows what is there now.
Check the non-plug-and-play section for MFE, NAI, SYM, T?, and VET entries. If they are all grayed out, yeah (!); but, if any are not, run their removal tool.
ASKER
None of the above non-plug-and-play are present.
OK; whatever is preventing you from sharing is the source of the problem and there ought to be events listed regarding it. It is probably a service which is failing to start.
You can either right-click on Computer and choose Manage, or type EVENTVWR.MSC<enter> in the search box. Look in the System section of Windows Logs for red-x's and the Security section for Audit Failures.
Because Vista and 7's logs get so huge, I often right-click on the logs folder and clear it (not worth saving either), then attempt the failing action which, in your case, would best be done by going to the advanced sharing options and trying to share the Public folders (its a checkbox). Afterwards, check the event logs again.
What errors are there?
You can either right-click on Computer and choose Manage, or type EVENTVWR.MSC<enter> in the search box. Look in the System section of Windows Logs for red-x's and the Security section for Audit Failures.
Because Vista and 7's logs get so huge, I often right-click on the logs folder and clear it (not worth saving either), then attempt the failing action which, in your case, would best be done by going to the advanced sharing options and trying to share the Public folders (its a checkbox). Afterwards, check the event logs again.
What errors are there?
ASKER
I will check this and re-post. I can only do so in the evening on this machine. Thanks for the help.
ASKER
Checked the logs and cleared. All security audits state successful. One error in system to speak of. Its below.
TCP/IP has chosen to restrict the scale factor due to a network condition. This could be related to a problem in a network device and will cause degraded throughput.
TCP/IP has chosen to restrict the scale factor due to a network condition. This could be related to a problem in a network device and will cause degraded throughput.
Did you try to share the public folders?
That will generate the error we need to address.
That will generate the error we need to address.
ASKER
Been away. I will check this tonight and post results. If I can't get it resolved I'm going to reload. Not sure what other issues I might be inheriting.
ASKER
Public sharing works well. I can share a folder on the desktop and edit it from other computers. I'm not able to access the computer in questions public folders from the same computer though. If I double click it I'm told I don't have the appropriate permissions. If I browse to the local folder I can do what I want.
Try this to fix the TCP scaling problem: http://support.microsoft.com/kb/934430
ASKER
Reloaded the system. Thanks for your efforts.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for 1namyln's comment #a38370378
Assisted answer: 250 points for Qlemo's comment #a38308166
Assisted answer: 250 points for DavisMcCarn's comment #a38309724
for the following reason:
Points are for efforts. Thank you!
Accepted answer: 0 points for 1namyln's comment #a38370378
Assisted answer: 250 points for Qlemo's comment #a38308166
Assisted answer: 250 points for DavisMcCarn's comment #a38309724
for the following reason:
Points are for efforts. Thank you!
ASKER
I did not mean to accept my own comment. Can we disregard this and award to the others? Thanks.
ASKER
Thanks for your efforts. Had to reload the machine.
ASKER
After stopping the firewall service the problem still exists.