Solved

Win Server 2003

Posted on 2013-12-23
9
334 Views
Last Modified: 2014-01-12
I have a server that runs Windows 2003 standard. I built a Windows 7 desktop and created a shared drive on the Win 7 Pro box. These are both in the same domain and on the same subnet. The Windows 2003 server was not having any issues at first with accessing the Windows 7 shares but now it has lost the ability to access the shares on the Windows 7 box. What is really weird is that the Windows 2003 server can still access shares on any other boxes or servers. I have made sure the firewalls are off and disabled any antivirus apps.
This is the error I receive on the Windows 2003 box when trying to connect. Image attached.
Error.gif
0
Comment
Question by:TabDB
  • 5
  • 3
9 Comments
 
LVL 29

Expert Comment

by:becraig
ID: 39737135
Can you run ipconfig on the win 7 machine and see what IP address you get then ping the win7 machine from the win2k3 server and see if both are the same.

If the addresses are the same then try doing a runas as a user that has permission on the win7 box e.g

runas /user:win7pro\user1 explorer
then enter the password it might just be as simple as the shares on the win7 box have not granted permissions to the account you are using on the win2003 server

Also are the users members of a domain or are they just local users on each computer in question?
0
 
LVL 32

Expert Comment

by:PowerEdgeTech
ID: 39739490
After determining they are on the same network segment and nothing network-related is preventing the communication as recommended ...

Are you connecting with local or domain credentials?

Does Windows 7 have its domain network connection labeled as Home, Work, or Public?

How many computers are using this share?  Mapped or direct?
0
 

Author Comment

by:TabDB
ID: 39740175
They are actually plugged into the same switch on same network. Tried local and domain credentials same issue. It is set the same for Work and Domain Current Profile. I have at least three servers that can connect to this share. I only have this one server that cannot connect.
0
 

Author Comment

by:TabDB
ID: 39747347
I have now been told by several others that Windows 7 has an issue with Windows 2003 servers connecting to shares on them. 2008 and 2012 servers seem to work fine with connecting to a Windows 7 box. Any thoughts?
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 32

Expert Comment

by:PowerEdgeTech
ID: 39747515
Just curious ... why are your shares on the workstations instead of the servers again?
0
 

Author Comment

by:TabDB
ID: 39750375
I ordered this very large capacity Windows 7 Pro workstation to send backups to. So all my servers send backups using LiveState into the shared drive of the Windows 7 machine.
0
 
LVL 32

Expert Comment

by:PowerEdgeTech
ID: 39750383
I see ... I'd have to think there is some difference in authentication from XP to 7, although I'm not sure where I'd look.  (I only ask, because I have 2003 servers with shares used by Windows 7 PC's with NO problems ... so I can only guess that some level/protocol (NTLM possibly?  2003 would likely be using v1 (default) and 7 would be using v2) of authentication is the difference.)
0
 

Accepted Solution

by:
TabDB earned 0 total points
ID: 39763259
Closing this issue. Have redirected the backup of this server to another server.
0
 

Author Closing Comment

by:TabDB
ID: 39774471
Redirected to another server.
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
SQL Server error 26 102
please tell me windows 1-10 7 56
Runtime Error 2 28
Malware Exploit 5 72
By default the complete memory dump option is disabled in windows . If we want to enable the complete memory dump for a diagnostic purpose, we have a solution for it. here we are using the registry method to enable this.
While working, an annoying popup showing below will come and we cannot cancel or close it form the screen. The error message will come again and again.
This Micro Tutorial will teach you the basics of configuring your computer to improve its speed. It will also teach you how to disable programs that are running in the background simultaneously. This will be demonstrated using Windows 7 operating…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

919 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now