[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 166
  • Last Modified:

Windows 7 / Windows XP Networking

I have a 4 station peer to peer network.  3 Computers are Windows 7 Pro, One is XP Pro.   One of the Windows 7 computers acts as our "server" and stores our Quickbooks and Act files.   I have no problem connecting any of the Windows 7 computers to the "server".  

The XP computer connects to the "server" shared drives when everything comes up.   As long as both computers remain on, the connection is good, for weeks.   If the XP computer is shut down it can't connect back to the shared drives.   The only way to reestablish the connection is to reboot the "server".  

Both the XP computer and the "server" have static IPs.   192.168.1.240 for the XP computer, 192.168.1.250 for the server.   Even when the XP computer can't connect to the shared drive I can ping both computers from each other by host name with out any problem, so I don't think it's a matter of not seeing the computers.   I can also browse from the "server" to the XP computer.   When I try to browse from XP to the "server" I get a message that it can't connect, it appears to be a permissions message.  If I reboot the "server" my shared drives are available.

I don't have any problem with my Windows 7 computers.   Any idea what could be going on here?  I'm guessing there must be something on the Windows 7 "server" that is blocking the XP computer.
0
kdubendorf
Asked:
kdubendorf
2 Solutions
 
MiftaulCommented:
There are different types of sharing in windows 7, could you please check its work network share.
0
 
arnoldCommented:
Issue can be because when the XP is rebooted, the session it had gets stuck (stale session) in these conditions check computer management, shared folder, sessions to see whether there is a session for the XP system.
Close the session and the XP should reestablish/reset the connection and access the data.
0
 
John HurstBusiness Consultant (Owner)Commented:
Remove Persistence on the XP machine.  Open a command prompt, and type:

NET USE  and enter.

See what network shares are listed and then remove them with:

NET USE Z: /Delete.   Do this for all drives.  Then type:

NET USE /PERSISTENT:NO

Now reboot and remap the drives. The original mappings should work.

.... Thinkpads_User
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
kdubendorfAuthor Commented:
None of these solutions has solved the problem.   I have taken to rebooting the server when I know the user on the XP computer will be accessing the server.

I would appreciate any other suggestions.
0
 
John HurstBusiness Consultant (Owner)Commented:
Windows 7 does not block XP (I have used that combination before).

There may be something wrong with the XP operating system (no issue with the other Windows 7 computers). Since XP is now dead, it may be worthwhile to consider a newer computer.

I assume you are not using Homegroup (you cannot with XP) and I assume File and Print sharing is enables (because the other Windows 7 computers work).

Did you disable (turn off) Use Simple File Sharing on the XP computer.
0
 
kdubendorfAuthor Commented:
Unfortunately the experts solutions didn't solve the problem
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now