fizzlefry
asked on
Windows 7 File sharing to XP
I try to do whatever I can, before coming on these boards and asking for help. I try to eliminate the little things (TRY being the opportune word). But here it is:
My issue is with a file share set up on a Windows 7 Pro x64 system. I have a 7 box acting as a file server for an 8 computer environment. I know I'm not at my max simultaneous connections so that's not the issue. The environment consists of 6 Windows 7 boxes and 2 XP. The 7 boxes are fine. No issues. The XP ones will work for a little while but upon booting from being powered down overnight, the cannot find the server. The only way to clear it is to reboot the 7 box. Now I've seen this a few times on these forums and have tried the suggested fixes. All have proven temporary, if impacting at all. I have disabled IP6 on the 7 box. I saw something about clearing the registry for a SMB entry, however when I did this, it caused some sort of issue with the other 7 boxes finding the share. The LAN is not going in to any powersave mode. I am using deny permissions from the 7 box, but only on further nested subfolders. Otherwise everyone is using a local user account (on the 7 box) to access the machine. Call it a pseudo-server of sorts. I have allowed for lower level encryption on the 7 box for the XP machines. I have added EVERYONE to the main share permissions (while still maintaining my deny permissions). I did not disable Password Protected filesharing, as one post suggested, as I wasn't sure what that would do for my permissions. The XP machines are patched and updated to current. No firewall locally or on the 7 box, nor virus software that would impede connection.
I'm at a loss. Believe me, I scoured these boards and others trying to find a solution before presenting this. And I've seen a few people battle with this and emerge victorious. Their fixes, though, just don't seem to work for me (unless I'm doing something wrong, in which case, TEACH ME!!!). Please help!!!
Thank you so much for your time reading this.
My issue is with a file share set up on a Windows 7 Pro x64 system. I have a 7 box acting as a file server for an 8 computer environment. I know I'm not at my max simultaneous connections so that's not the issue. The environment consists of 6 Windows 7 boxes and 2 XP. The 7 boxes are fine. No issues. The XP ones will work for a little while but upon booting from being powered down overnight, the cannot find the server. The only way to clear it is to reboot the 7 box. Now I've seen this a few times on these forums and have tried the suggested fixes. All have proven temporary, if impacting at all. I have disabled IP6 on the 7 box. I saw something about clearing the registry for a SMB entry, however when I did this, it caused some sort of issue with the other 7 boxes finding the share. The LAN is not going in to any powersave mode. I am using deny permissions from the 7 box, but only on further nested subfolders. Otherwise everyone is using a local user account (on the 7 box) to access the machine. Call it a pseudo-server of sorts. I have allowed for lower level encryption on the 7 box for the XP machines. I have added EVERYONE to the main share permissions (while still maintaining my deny permissions). I did not disable Password Protected filesharing, as one post suggested, as I wasn't sure what that would do for my permissions. The XP machines are patched and updated to current. No firewall locally or on the 7 box, nor virus software that would impede connection.
I'm at a loss. Believe me, I scoured these boards and others trying to find a solution before presenting this. And I've seen a few people battle with this and emerge victorious. Their fixes, though, just don't seem to work for me (unless I'm doing something wrong, in which case, TEACH ME!!!). Please help!!!
Thank you so much for your time reading this.
Also, make sure they are all in the same workgroup and have the same IP scheme... 192.168.1....
Ping the Win7 server from the others, you should get 4 replies.
Ping the Win7 server from the others, you should get 4 replies.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
TG-TIS - thanks for your response. They are all on the same workgroup. As for the IP scheme, the server is a static IP set outside of DHCP, so the address wouldn't be assigned. The other workstations are dynamic IP, and pick up what the router is putting out.
I'm not sure I understand what using the command prompt is doing. If I'm reading it properly, you're just mapping from DOS. What would that do differently that the standard windows mapping wouldn't? Usually I'm able to map directly to the 7 box, suing windows mapping. The problem seems to be that the 7 box is either dropping it or not allowing it to reconnect after some set amount of time?
I'm not sure I understand what using the command prompt is doing. If I'm reading it properly, you're just mapping from DOS. What would that do differently that the standard windows mapping wouldn't? Usually I'm able to map directly to the 7 box, suing windows mapping. The problem seems to be that the 7 box is either dropping it or not allowing it to reconnect after some set amount of time?
ASKER
Run5k, thank you so much for your response. I did not see this article in my searching. The name of the article is DEFINITELY not familiar. I will try this in an hour, as I can't mess with the server, let alone the registry, right now. May I ask what the lines basically do, as far as on the backend? Just telling the 7 box it's a file server? What does the system do differently when using these values? I'm just very curious to understand the root of the issue.
I suggest putting static IP's on all systems...
192.168.1.1
192.168.1.2
192.168.1.3
Do this on all systems:
Type commands on all boxes including file server.
go to start, type in cmd
ipconfig /flushdns
ipconfig /registerdns
Ping (server ip) >>> verify you get 4 replies
net use p: /d
net use p: \\Win7Pc\ShareName
192.168.1.1
192.168.1.2
192.168.1.3
Do this on all systems:
Type commands on all boxes including file server.
go to start, type in cmd
ipconfig /flushdns
ipconfig /registerdns
Ping (server ip) >>> verify you get 4 replies
net use p: /d
net use p: \\Win7Pc\ShareName
Hi,
There are a couple of things you need to set for the xp and 7 to connect correctly:
Open Secpol.msc
Local Policies -> Security Options ->
Network security: LAN Manager authentication level: * Send LM & NTLM responses
Network security: Minimum session security for NTLM SSP based (both clients and servers) * Make sure 128 bit encryption is turned off on both.
And have you downloaded and installed the LLTD (Link Layer Topology Discovery Responder) on the XP machines? Without that, the Vista machines will not see the XP machines in the View full map link of Network & Sharing Center:
http://www.microsoft.com/downloads/details.aspx?familyid=4F01A31D-EE46-481E-BA11-37F485FA34EA&displaylang=en
Rgds.
There are a couple of things you need to set for the xp and 7 to connect correctly:
Open Secpol.msc
Local Policies -> Security Options ->
Network security: LAN Manager authentication level: * Send LM & NTLM responses
Network security: Minimum session security for NTLM SSP based (both clients and servers) * Make sure 128 bit encryption is turned off on both.
And have you downloaded and installed the LLTD (Link Layer Topology Discovery Responder) on the XP machines? Without that, the Vista machines will not see the XP machines in the View full map link of Network & Sharing Center:
http://www.microsoft.com/downloads/details.aspx?familyid=4F01A31D-EE46-481E-BA11-37F485FA34EA&displaylang=en
Rgds.
ASKER
TG-TIS - it is your belief that a static IP for all XP workstations and simple mapping will do it? I'm not sure how that would work, as it's the XP machines can't see the 7 box, and not the other way around.
pcfreaker - thanks for your response! The XP boxes are updated current. I would assume this new LLTD is included in that, with the other high priority / optional updates. As for the rest of your solution, just so I understand, how does this impact? I ask only because the system WILL connect and I can open files on the XP box, over the network stored on the 7 box, without problem. It's something happeneing over the course of a timeframe, or when the XP box is powered down and off for the night. Reconnecting requires a reboot of the 7 box. Yet if I leave the XP box on day and night, it always stays connected and my shares, accessible. My initial understanding of your resolution is if connectivity wasn;t there to begin with. Am I misreading? Remember, I'm no network analyst. I'm a hardware guy, before anything. So I'm just taking practical logic and applying it here. Please advise.
pcfreaker - thanks for your response! The XP boxes are updated current. I would assume this new LLTD is included in that, with the other high priority / optional updates. As for the rest of your solution, just so I understand, how does this impact? I ask only because the system WILL connect and I can open files on the XP box, over the network stored on the 7 box, without problem. It's something happeneing over the course of a timeframe, or when the XP box is powered down and off for the night. Reconnecting requires a reboot of the 7 box. Yet if I leave the XP box on day and night, it always stays connected and my shares, accessible. My initial understanding of your resolution is if connectivity wasn;t there to begin with. Am I misreading? Remember, I'm no network analyst. I'm a hardware guy, before anything. So I'm just taking practical logic and applying it here. Please advise.
I use static IP's on all boxes and never have that problem.
Fizzlefry,
This fix has made the rounds for quite some time now, but it actually started as a small footnote within a Windows Sysinternals article in November 2006. Unfortunately the original source is no longer available online, but I preserved a snapshot of that article:
This fix has made the rounds for quite some time now, but it actually started as a small footnote within a Windows Sysinternals article in November 2006. Unfortunately the original source is no longer available online, but I preserved a snapshot of that article:
Yes fizzlefry, you are right, my bad, I thought you were getting networking issues several times a day.
Well have you tryed going into the Network drivers, there is an option that reads Power Management tab that is under the properties of your network connection, just uncheck the three options and sleep your computer again.
Let me know.
Rgds.
Well have you tryed going into the Network drivers, there is an option that reads Power Management tab that is under the properties of your network connection, just uncheck the three options and sleep your computer again.
Let me know.
Rgds.
ASKER
Thanks everyone for your responses! I will begin testing and implementation over the next few hours and allow for a few days worth of testing. I will post back and award points accordingly.
Is the mapping working correctly now?
ASKER
TG-TIS - as of this point in time, it is working, using Run5k's fix to the registry. I did a little more reading on it and it makes more sense, as for the basis of this fix.
His fix was implemented on Thursday evening. I've had 1 full day of testing, 2 morning logon attempts with no issues. I was hoping to allow this to run for a few more days, to confirm testing to be successful. I really appreciate yours, and everyone's insight into this. I will definitely update and award points accordingly.
Thank you again...
His fix was implemented on Thursday evening. I've had 1 full day of testing, 2 morning logon attempts with no issues. I was hoping to allow this to run for a few more days, to confirm testing to be successful. I really appreciate yours, and everyone's insight into this. I will definitely update and award points accordingly.
Thank you again...
Fizzlefry, there is certainly no rush. From my perspective, the points are relatively inconsequential. If you need a bit more time to ensure that your Windows architecture is working properly, that's what really counts!
ASKER
I had to wait to make sure this was the right fix, but the XP machine has been rebooting / powering down every day and reconnects with the server with no issues whatsoever. Thanks again to everyone for their expertise.
Glad to hear that your systems are back to normal!
net use p: /d
net use p: \\Win7Pc\ShareName
If you don't get any errors, the share should be available.