Re: Windows Server 2003 Cannot Access Network Shares
Numbers Slyter
I just installed (and activated) Windows Server 2019 Standard. It is set up in a workgroup and has the same workgroup name as all other PC's. All other PCs can access each other's shares (even the servers shares) but the server cannot see any shares. Given the server's IP address of 192.168.0.3, whenever I try to access another PC's share from the server using
The only things I can find when searching this issue are questions about not being able to access the server's shares. That's not my issue. The issue is that the server can't access the other shares on the network.
Figured it out and fixed it. The answer was found here and here. Basically, Windows Server 2019 disables guest access in SMB2 by default. Had to enable insecure guest logons in the group policy editor.
I run a Windows 2008 server with SP2. This server acts as a desktop alone. Recently, I switched between two networks (corporate and other) using this system. Ever since, I am unable to access any network share on the original network from where I installed and configured the desktop. The message I get is "Network path was not found". Note that I am able to access the internet and my corporate mail server.
I am told this is a Vista and Windows 2008 specific problem and I have done everything I could think of:a) Deleted the second network settings from the desktopb) Installed a patch from MS that supposed took care of this problem (with MS clearly saying they had not tested this enough)c) The SP2 install was after the problem occurred and I went ahead with it in the hope that SP2 may have something that would fix this
a) A system admin can log into this system from a remote terminalb) I cannot get into my own system using the hidden share C$ - for instance \mymachine\C$ gives me the same message as above - Network path not foundc) I can log into my system remotely using mstscd) I cannot create shares on this system - as an extension network printers are not detected
Apparently 'File and printer Sharing for Microsoft Networks' is not installed for the network adapter by default. This is independent on whether or not file sharing is actually installed.I'm not sure if this is a Windows 2008 default or the network card's default.
You are not crazy I have this issue too and can replicate the following oddies that only seem to happen with win2k8 sp2 and vista sp2 clients whom are not joined to the domain but try to access a domain joined server. They will get prompted for cred's but even when the creds are correct will not be allowed access. Interestingly enough however if you attempt to connect via \ip\ or \ip\share you are prompted for creds and they work and access is granted but if you use the standard \machinename or \FQDN while you get prompted, it will never let you in.
This seems to have started with SP2.I have found no solution to this other than rolling back to SP1 or using the IP.Also interesting is once you have connected via IP successfully you can then use the \machinename etc methods and they work fine. If you then say remove all connections to the box via net use /del on all connections then try the \machinename again the problem will return. - Almost hilarious
This seems to have started with SP2. I have found no solution to this other than rolling back to SP1 or using the IP. Also interesting is once you have connected via IP successfully you can then use the \machinename etc methods and they work fine. If you then say remove all connections to the box via net use /del on all connections then try the \machinename again the problem will return. - Almost hilarious
I want you to know that for me solving this problem wat to tick Client for Microsoft Networks on the right NIC on my DC. Looks like when messing arround with Hyper-V this was disabled for some reason.
I didn't try to this (Did the winsock and tcpip resets (via Thomas). This was scary, because it deleted all my NIC settings. But, lo and behold, restoring them yielded the long sought "Welcome to the ... domain!") because of the warning in there. I would have done this as a last resort. If you have a another server, compare the settings between the two.
Thanks in advanced for reading the post. So few issues I am running into. I have a Windows 2016 local servers and all other windows 10 are also local and not a domain PCs. Some PCs can access the \server without any issue but some will give me variety of issues such as:
However, on some PCs the \server connects without any issue so the share has been successfully shared to specific users. In some the trick I did was instead of searching \server or \IPAddress I typed \server\share_path or \IPAddress\Share Path and I was able to connect. But just from file explorer going to \server or the IP address it encountered the above mentioned error.
From a client computer, assuming has joint the domain and running with the domain user, open the command prompt and issue the command net view \SEERVERNAME, does it show the shared resources in the server?
I am having an odd issue that I hope someone can help with. I have an older 32bit Windows Server 2003SP2 server that cannot access any shares on our 64bit Windows Server 2012R2 domain controller. The 2003 server can access shares on other 2012R2 servers fine, it is just the one server it has problems with. Also, the 2012R2 server can access shares on the 2003 server fine. There is no firewall or AV on the 2003 server but the 2012R2 server has both the firewall and Symantec Endpoint Protection installed on it. No other clients have problems access the 2012R2 server (although all the other machines access it are Win10/Win2012R2).
I have checked the event log on both machines and there are no messages. If I try and access a share with Windows Explorer, I get the error "Windows cannot find '\win2012R2\sharename'. Check the spelling and try again, or try searching for the item by clicking the Start button and then clicking search." If I try from the command line using NET USE, I get the error "System error 64 has occurred. The specified network name is no longer available". I can ping the 2012R2 server from the 2003 server fine. DNS lookups also work fine.
This does sound like a possible SMB issue. Yes there is SMB logging. You want to look in Event Viewer on both file servers and filter by Event ID. There are five Event IDs related to SMB. The Event IDs are 2011 2022 2504 2505 and 2506.
You can change the version of SMB the server uses in HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters by setting the value data to "0" (disable) or "1" (enable) for the value name SMB1 or SMB2.
I had a similar problem, except a Win10 client could not access a Win2003 server. I did not have event log messages either. However, executing NET USE \\\ from an admin command window from the client resulted in an informative error message stating SMBv1 is required but not available. SMB will auto-negotiate to a compatible level, but SMBv1 has security flaws, so has been disabled on some Windows versions, and not available in others. Windows Server 2003 only goes up to SMBv1, so if the the other machine doesn't have SMBv1 then the connection will fail. The accesser of the share, the client, only needs the client protocol, and the host only needs the server protocol. It can be enabled/disabled through Control Panel Programs and Features Turn Windows features on or off SMB 1.0/CIFS File Sharing Support, if it is installed. It can also be enabled/disabled through a GPO, which might override Windows feature changes.
Just to close out this question with what ended up happening. I never could get it working but we ended up disabling SMBv1 across the enterprise and decommissioning the 2003 server shortly there after.
I cannot access shared folders on a private network, even from the server computer with an administrator account.
This is going on for about 2 days, and I have searched many similar issues online without any progress on solving the problem.
I will list bellow what I have found so far that seems to be the most relevant.
You show the share permissions, but not the folder permissions on D:\share_test. Have you reviewed them? In the Security tab for that folder click on the Advanced button, and then select the Effective Permissions tab. Pick a user account and see what access it reports.
I don't have access to a 2012 server, but in eventvwr, check in Applications and Services Logs, Microsoft, Windows, SMBServer. See if any related events are in those logs. (I don't know which version of the OS introduced those logs.)
Go to Control Panel > System ans Security > Windows Defender Firewall > Advance Settings > Inbound Rules. Right click on File and Printer Sharing (SMB-In) from the list and select Enable Rule`. Normally, there are two File and Printer Sharing (SMB-In), one is for Domain profile and one is for Public & Private profile. I'm not sure which profile should be applied, Domain or Public or Private. For me, it's Domain profile.
Go to C:\windows and right-click --> Properties
Hit advance sharing
Click the check box Share this folder
Enter the name admin$ and hit Permissions
I would recommend removing 'Everyone' and adding just the users that the PsExec command will use to execute.
I don't know how it disappeared to begin with. Coincidentally in the same day that this issue with shared folders started the Bitdefender was giving false positives to a software used in the company, no clue if it is related.
d3342ee215