Error Cannot Access Domain Info 1351
98 & ME Support Windows Servers Microsoft Office Support Internet Browsers and Email Internet Explorer & Edge Forum Mozilla / Firefox Browsers Other Browsers Email Alternative Computing Linux Support Mac Support Other Operating Systems Hardware Support Overclocking Motherboards, Bios & CPU Hard Drive Support Removable Media Drives RAM & Power Supply Sound Cards Case Mod Driver Support Video Card Support Printer Support Laptop Support Building Other Hardware Support Networking Forum Networking Support Modems / Cable / DSL / Satellite Cabling & Network Cards Protocols & Routing File & Application Sharing Security & Firewalls The IT Pro Certification & Career Programming Gaming Forum PC Gaming Support Game Installation Support Console Gaming Support Online/Network Gaming Support Mods & Maps Gaming Discussion Design Forum Web Design & Dev Graphic Design/Multimedia Web Serving & Management Design Discussion & FAQ Website Design Counsel Smart Devices Apple iOS Android OS Blackberry/RIM OS Palm WebOS Windows Mobile Other Mobile Tech Support Articles Apple Certification Gaming General Hardware Internet Linux Networking Photography Security Software Tips & Tricks Windows Spyware 1st Steps Rules Tech Support Forum > Microsoft Support > Windows Servers cannot access share folder \\hostname\share User Name Remember Me? Password Site Map Posting Help Register Rules Today's Posts Search Site Map Home Forum Rules Members List Contact Us Community Links Pictures & Albums Members List Search Forums Show Threads Show Posts Tag Search Advanced Search Search Site / Google View Posts New Posts Your Posts Go to Page... cannot access share folder \\hostname\share This is a discussion on cannot access share folder \\hostname\share within the Windows Servers forums, part of the Tech Support Forum category. hi all, i got a problem with my server. OS: windows server 2003 r2 i can map the network drive Thread Tools Search this Thread 10-14-2011, 01:26 AM #1 Tukang Bacok Registered Member Join Date: Apr 2011 Posts: 8 OS: Windows XP sp3, Windows Server 2003 R2 hi all, i got a problem with my server. OS: windows server 2003 r2 i can map the network drive with below command. C:\Documents and Settings\user>net use j: "\\server1.local\common" The command completed successfully. C:\Documents an
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Windows XP Network Drive Error 1351 up vote 0 down vote favorite my scenario: 20 Windows (XP/7) Clients one XP file server two http://www.techsupportforum.com/forums/f8/cannot-access-share-folder-hostname-share-606281.html Linux (Suse 9,10) Samba File servers new Samba Domain Controller (Zentyal) So, the Client PCs all were in a workgroup "blabla", where also the old Samba file servers are located. After bringing a few Windows Clients in the new domain ("blabla.intern"), I have problems connecting to the old Samba shares. Connection to the XP file server is still working. But connection from, especially Windows XP clients, to the old Samba file servers are not possible. It always ends up with: System error 1351 http://serverfault.com/questions/762927/windows-xp-network-drive-error-1351 has occurred. Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied. From Windows 7 it works sometimes. When I use IP it seems to work always. But only from Windows 7. XP - no chance. Whats the matter? I don't see a problem with the name resolution, also tried different DNS aliases for the machines or also hacks with the hosts-file. Are there any securityrelated settings with Windows XP in a Samba domain? Feel free to give me any hints... Still groping in the dark :( active-directory windows-xp samba zentyal share|improve this question asked Mar 10 at 15:19 user333163 186 add a comment| active oldest votes Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook. Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Browse other questions tagged active-directory windows-xp samba zentyal or ask your own question. asked 7 months ago viewed 55 times Related 0Samba server error message in Windows XP2Windows 7 Client attached to a domain connecting to a Samba 3.5.2 Server3How to debug the integration of a Windows 7 machine into a Samba 3 domain?1An Active Directory Do
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen
I started getting reports from clients/users having issues logging into virtual servers running Windows Server 2008 R2 and Windows Server 2012 operating systems via RDP. This logon issue seems to be affecting virtual machines in private datacenters as well as in Azure Cloud. Before signing off on a project, you test everything out using dev/admin/test accounts and pass all checks. The moment users try to access the server for the first time, they immediately report problems… Symptom On a Windows Server 2008 R2, a user may be prompted to change his/her password when logging on for the first time: The user's password must be changed before logging on the first time This error message is expected and is a good feature from the security standpoint - however, it indirectly causes the next issue: Configuration information could not be read from the domain controller This error, "Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied", is not making a lot of sense especially in Azure Cloud deployment scenario, when you just created your first server and do not have any integration with any of the existing on-prem Active Directories. This error happens on a stand-alone, workgroup-joined server, brand new installation right out of the box. On the Windows Server 2012 virtual server running in Azure Cloud, the error is the same but of course looks a bit different in line with the UI changes: The user's password must be changed before signing in Once you type in the new password, you get the same error: Configuration information could not be read from the domain controller Again, the same scenario - brand new server installation, never joined to any AD environments, brand new user account that is set to change password on the first logon. Cause The issue is caused by the RDP client, more specifically by the user providing incorrect DOMAIN information in the RDP logon dialog box. The lates