Windows 7 XP Sharing Problem
I have a client who has recently added a Win 7 PC to an established XP Network. He initially had some issues accessing the Win 7 printer from an XP laptop but we resolved this by uninstalling a timed out mcafee firewall which was preventing the xp machine pinging the win 7 pc. The next problem was that the xp laptop could not be seen in the win 7 network map. The XP machine was SP3 so apparently does not require the LLTD fix and I eventually found KB913628 and turned off restrictanonymous. This allowed the machine to be seen but when clicked on win 7 alleged that it could not be accessed due to a naming issue, despite this, a few seconds later the shared printers and shared folders appeared and were fully accessible. Terriffic we thought!
As a final test I tried sharing an additional folder on the XP machine and this duly appeared as a shared folder when viewed from the 7 PC. All good, you might think, but when clicked on the new share proved to be inaccessible. I've been into sharing and shared it full access to everyone (no good) and also shared it full access to anonymous user (also no good).
The new share is fully accessible from another XP machine and various other folders have also failed to share properly to win 7.
A (possibly) unrelated issue is that remote desktop works perfectly well from the 7 machine to another XP machine but not to the laptop although the laptop does have "Allow users to connect remotely" enabled.
I had so many issues like this when Vista first appeared this feels like Groundhog Day!
Any pointers would be much appreciated.
As a final test I tried sharing an additional folder on the XP machine and this duly appeared as a shared folder when viewed from the 7 PC. All good, you might think, but when clicked on the new share proved to be inaccessible. I've been into sharing and shared it full access to everyone (no good) and also shared it full access to anonymous user (also no good).
The new share is fully accessible from another XP machine and various other folders have also failed to share properly to win 7.
A (possibly) unrelated issue is that remote desktop works perfectly well from the 7 machine to another XP machine but not to the laptop although the laptop does have "Allow users to connect remotely" enabled.
I had so many issues like this when Vista first appeared this feels like Groundhog Day!
Any pointers would be much appreciated.
Last Comment
ASKER
Thanks SmartAce WOLF:
You're right, its not quite the answer I want!But I will try granting full access to my new share to admins,users and guests (in addition to everyone). My problem relates to accessing a particular XP machine from a win 7 machine so i would not have thought enabling guest on the win 7 machine would have any effect. Enabling it on the problem xp machine didn't.
What really puzzles me is why the existing shares work but new ones don't, even though properties appear identical. Also why does the new share work to an xp machine but not to a 7 one.
All a bit weird but somehow familiar!
You're right, its not quite the answer I want!But I will try granting full access to my new share to admins,users and guests (in addition to everyone). My problem relates to accessing a particular XP machine from a win 7 machine so i would not have thought enabling guest on the win 7 machine would have any effect. Enabling it on the problem xp machine didn't.
What really puzzles me is why the existing shares work but new ones don't, even though properties appear identical. Also why does the new share work to an xp machine but not to a 7 one.
All a bit weird but somehow familiar!
My problem relates to accessing a particular XP machine from a win 7 machine
That is indeed a bit puzzling though not exactly unheard of in my world either. This particular issue arises with any one or several of the following in my experience.
1.) File and Printer Sharing is not enabled on the XP machine
2.) The workgroup of the XP machine is different than that of others within the LAN
3.) The Computers ID or name within the LAN is duplicated from a cached entry long forgottten about. On this note, perusing your orginal post, you mentioned something about Windows 7 reporting an error regarding the Naming issue. This may be important in that I have encountered numerous problems with Windows 7's IPv6 stack in that area. Upon experiencing any problematic issues of this sort I also take the additional step of removing the tick from the IPv6 property sheet and though it is not likely problematic I do the same with the QOS.
Have you also tried connecting via the Run command by simply typing in the XP machines IP address? i.e. Start/Run/192.168.x.x?
Given your circumstances I believe that I would begin assured that both of the 2 systems were malware free, disable IPv6, ensure they are both within the same workgroup, (many will argue the need for this one but as easy as it is to change I do it anyway), I might even elect to assign a static IP address to one or both machines, and finally I would use the netsh commands within the XP machine as follows.
netsh int ip reset c:\resetlog.txt
netsh reset winsock catalog
netsh int ip delete arpcache
ipconfig /flushdns
then reboot and see what transpires from there. Hopefully, the resolution will present itself without being all convoluted with all of these commands I have thrown up. Good luck Jason.
1.) File and Printer Sharing is not enabled on the XP machine
2.) The workgroup of the XP machine is different than that of others within the LAN
3.) The Computers ID or name within the LAN is duplicated from a cached entry long forgottten about. On this note, perusing your orginal post, you mentioned something about Windows 7 reporting an error regarding the Naming issue. This may be important in that I have encountered numerous problems with Windows 7's IPv6 stack in that area. Upon experiencing any problematic issues of this sort I also take the additional step of removing the tick from the IPv6 property sheet and though it is not likely problematic I do the same with the QOS.
Have you also tried connecting via the Run command by simply typing in the XP machines IP address? i.e. Start/Run/192.168.x.x?
Given your circumstances I believe that I would begin assured that both of the 2 systems were malware free, disable IPv6, ensure they are both within the same workgroup, (many will argue the need for this one but as easy as it is to change I do it anyway), I might even elect to assign a static IP address to one or both machines, and finally I would use the netsh commands within the XP machine as follows.
netsh int ip reset c:\resetlog.txt
netsh reset winsock catalog
netsh int ip delete arpcache
ipconfig /flushdns
then reboot and see what transpires from there. Hopefully, the resolution will present itself without being all convoluted with all of these commands I have thrown up. Good luck Jason.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Ahhh! The proverbial light bulb goes off here as well. I have heard others giving caution regardiing the differences between the two. I had always assumed they were speaking more in terms of which would take precedence given any permissions that seemed to be in contrary to each other.
There is a good article about it here, but it will require you to create an account. The site is definitely an asset to anyone in IT.
Thanks for posting the resolution Jason. Good day mate
There is a good article about it here, but it will require you to create an account. The site is definitely an asset to anyone in IT.
Thanks for posting the resolution Jason. Good day mate
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for jasonJladas's comment http:/Q_27381529.html#36923976
for the following reason:
I dont like awarding myself points, but I did find the fix m yself - in the end!
Accepted answer: 0 points for jasonJladas's comment http:/Q_27381529.html#36923976
for the following reason:
I dont like awarding myself points, but I did find the fix m yself - in the end!
ASKER
I need to ask another question, so I am objecting to my own acceptance of my own answer in order to give the points to SmartAceWolf who tried hard.
Windows Networking
The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.
51K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
It is worthy to note here that though I am not what I would consider to be "proficient" in ACLs and WIndows shares, I am not by any means new to them. Nor are many of my constituents who almost universally concur that this choice is far easier than upgrading every single workstation within a given LAN to Windows 7.