Home > Windows Server > Windows 2008 R2 Server Cannot Access Shares On Other Servers

Windows 2008 R2 Server Cannot Access Shares On Other Servers


Also both of these servers on running as VM's. My PC in particular has Win 7 RC. 2nd Edit: I disabled the Guest account and found out that my client PC's username is different from the username I was trying If file sharing has been restricted to users with local accounts and passwords, a list of users can be obtained by clicking on the down arrow. Seems there is a bug in 2008 R2 server somewhere. http://macinstruct.net/windows-server/windows-2003-server-cannot-access-shares.html

So they just start to use it and this shows up. I have experienced this already when trying to map a network drive to \\server\foldr with specific credentials, somehow my credentials are never accepted. Maybe, but it's like if you jolt it the right way at the right time, it must start polling it's connectionsbecause it will reconnect the shareswithout restarting. Check the Share Permissions that are set for the Everyone group.

Windows Server 2008 R2 Loses Ability To Connect To Network Share

Once this has been selected the Share name field and associated button will activate enabling a share name to be entered. the saga continues ............... If a permission is Denied, however, it overrides any cases where that permission may have been granted. I am not happy :( Rob Thursday, May 06, 2010 8:23 AM 0 Sign in to vote I have the exact same issue as others have reported on a 2008

Browse other questions tagged windows-server-2008 networking network-share or ask your own question. I can access the share from RDP, and find the last file that caused the problem...as if it doesn't release the transfer/save process. Suddenly users lost the ability to map shares on an older NT server. Kb2194664 Contents 1 Standard and Public File Sharing 2 Enabling Windows Server 2008 R2 File Sharing 3 Creating Shared Folders with Windows Explorer 4 Creating Shared Folders on Remote Servers with Computer

Tuesday, April 20, 2010 11:01 AM 0 Sign in to vote It looks that we solved the problem with the routing in our case which i worked on with Freek Berson Windows Server 2008 R2 Cannot Access Shared Folder Ever since, I am unable to access any network share on the original network from where I installed and configured the desktop. Finally, click on finish to complete the sharing process. I wrote this post to attend everybody to our conclusion.

Didn't really say much about the update...stability and reliability update concerning windows crashes with 3rd party software (but I don't have any).There were a few other fixes that were unrelated to Windows Server 2008 File Sharing Not Working I will keep you posted if anything happens. Unjoined the Domain from my workstation2). Try from the server. –Ed Fries Dec 4 '09 at 22:29 I don't have workgroup machines to test on, it's very possible the correct syntax is: Net Use X:

Windows Server 2008 R2 Cannot Access Shared Folder

I got Microsoft to login to do some network traces and it just starting working again. Phil Monday, April 05, 2010 4:41 PM 0 Sign in to vote What are the A and PTR records look like on the DNS server for this problem server?MCSA Windows Windows Server 2008 R2 Loses Ability To Connect To Network Share In all of our situations, everything works correctly for ~1 week, and then we start to have issues. Windows Server 2008 R2 Shared Folder Not Working Flushed the DNS on the file server.

Tuesday, March 23, 2010 8:53 AM 0 Sign in to vote Hi, we also have the same problem... http://macinstruct.net/windows-server/windows-cannot-access-network-share-server-2008.html more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed Does a list of the non-letter ASCII symbol macros exist? No firewall on the server. Not Able To Access Shared Folder In Windows Server 2012 R2

Thursday, February 11, 2010 5:51 PM 0 Sign in to vote This issue just started on my server 2 days ago,was working ok for 3 months. The server may be temporarily unavailable or maybe incorrectly configured. (IP of DC) I know it's not true as it was working fine, then produced this error, then went off and Waiting patiently to hear of a fix, all the client sees is no access to the drives and it's p(&&(ng them off. navigate here Monday, February 08, 2010 8:42 PM 0 Sign in to vote How many of you, besides Forsmark, are having this issue with a Win2008 R2 Terminal / Remote Desktop Services server?Conagher?

Found "Automatic certificate enrollment for local system failed" in event logs. –Justin Love Feb 6 '11 at 1:09 add a comment| 1 Answer 1 active oldest votes up vote 0 down Can't Access Unc Share On Windows Server 2012 R2 share|improve this answer edited Apr 6 '15 at 10:06 Andrew Schulman 5,22881835 answered Apr 6 '15 at 9:24 Nithin 1 add a comment| up vote -2 down vote I have windows Hopefully get to the bottom of this soon.

I have had to resort to rebooting the server once a day now just to keep everyone happy.

I think that once the other server is restarted, somehow my RDS server forgets about it, and can no longer connect unless full ip or FQDN is entered. I can't find anything or find any reason for this to occur. Reply to Mr Davo Ask a new question Answer Read More Windows Server 2008 Computers Networking Related Resources Cannot access Windows xp shared folder from Windows 7 but accessing shared folder Network Shares Stop Responding Randomly On Windows Server 2008 R2 Regards Friday, February 12, 2010 4:31 PM 0 Sign in to vote Microsoft have told me to look at this kb article : http://support.microsoft.com/kb/929851 Friday, February 12, 2010 5:34 PM 0

Read - Grants the specified users permission to read and execute files and view and access file lists and sub-folders. Bob Kann Proposed as answer by rkann Wednesday, April 07, 2010 3:30 PM Wednesday, April 07, 2010 3:30 PM 0 Sign in to vote Bob, It will come back. The message I get is "Network path was not found". http://macinstruct.net/windows-server/windows-cannot-access-server-2008.html All the NIC settings and configurations are the same on both 2008 servers.

I have a few VMS installed as this is my Workstation and test machine. Cause: The user does not have the Read permission to the folder in a shared folder on which access-based enumeration is enabled, or the Special permissions have been modified. From my vantage point thios sounds like an issue that started recently so I would suspect a recent update could be causing the issue.Don Murphy Hi Don,During my troubleshooting session, we Teenage daughter refusing to go to school Isn't AES-NI useless because now the key length need to be longer?

After spending a week with Microsoft, we discovered the following: The Network Provider tab was missing. Then they put in a ticket and have to wait til we pick it up during working hours and do the reboot. Can an object *immediately* start moving at a high velocity? Then after a while, that does not work again, and we have to go back to \\servername\Share.

When you do an initial ping, it first reports that the destination host is unreachable and then it starts to respond to pings. As I have previously said the problem didn't occur this week, no idea why but no doubt it will come back. I will update here on any new info. The XP/Vista/Win7 workstations on the network has no problem accessing the shares on the 2003 Server, only the 2008 R2 servers.

Also, I'm finding different phone numbers and "classes" of support. Eventually they will escalate to a top-level engineer..we'll see who gets there first lol. more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation Science So this was a routing problem right here.