Administration of Active Directory does not have to be hard. Too often what should be a simple task is made more difficult than it needs to be.The solution? Hyena from SystemTools Software. With ease-of-use as well as powerful importing and bulk updating capabilities.
Windows UNC / File Sharing / Browsing (Can Ping, RDP but no UNC)
Hey guys,
I have a bit of a strange quirk here. I have a few different subnets (each a different office) in my network and I am coming across an issue where I cannot browse network shares on a few servers from 3 of my 6 subnets. I can ping, tracert, rdp into the server in question.
Here's a gist of what I've looked into so far with no avail.
- Checked Network Sharing settings and profiles.
- Checked DNS settings (WINS is not configured)
- Checked hosts files
- Checked Advanced Binding settings on the NIC
- Checked OS level Firewall (currently off)
- Checked specific services (such as Computer Browser)
- Re-IP'd the server in question
- Verified that Windows Updates have been applied
- Checked Local Security Policies revolving around File Sharing, Auditing etc.
- Checked the hardware firewall for any port blocks or restrictions.
Im sure I am missing a few other bullets. Also, a little more about the environment. The server in question is on a Windows Server 2012 R2 on a Citrix XenServer 6.1 platform (I know its outdated). But I have another server in the same XenServer Pool with no issues.
I bet it's something so simple that I may have overlooked but I am dropping this post here to see if any of you guys can lend your opinions and help me out or trigger a spark on my end to getting me back on track.
If you feel its networking (Cisco ASA/Router) related, could you provide details as to where to check and configure the setting on the running configuration so that I can relay it to my network engineer? If you feel its Win OS related, please share as well.
Thanks fellas!
I have a bit of a strange quirk here. I have a few different subnets (each a different office) in my network and I am coming across an issue where I cannot browse network shares on a few servers from 3 of my 6 subnets. I can ping, tracert, rdp into the server in question.
Here's a gist of what I've looked into so far with no avail.
- Checked Network Sharing settings and profiles.
- Checked DNS settings (WINS is not configured)
- Checked hosts files
- Checked Advanced Binding settings on the NIC
- Checked OS level Firewall (currently off)
- Checked specific services (such as Computer Browser)
- Re-IP'd the server in question
- Verified that Windows Updates have been applied
- Checked Local Security Policies revolving around File Sharing, Auditing etc.
- Checked the hardware firewall for any port blocks or restrictions.
Im sure I am missing a few other bullets. Also, a little more about the environment. The server in question is on a Windows Server 2012 R2 on a Citrix XenServer 6.1 platform (I know its outdated). But I have another server in the same XenServer Pool with no issues.
I bet it's something so simple that I may have overlooked but I am dropping this post here to see if any of you guys can lend your opinions and help me out or trigger a spark on my end to getting me back on track.
If you feel its networking (Cisco ASA/Router) related, could you provide details as to where to check and configure the setting on the running configuration so that I can relay it to my network engineer? If you feel its Win OS related, please share as well.
Thanks fellas!
Asked:
-
9
-
6
-
5
1 Solution
Hey guys! Thanks for the reply.
Unfortunately via IP, FQDN or server name. It will not establish a connection to view the shares available. I can ping or do just about anything else to it just not UNC or map drives for that matter.
The server is a fresh build, has no AV and Windows OS firewall is completely off.
Unfortunately via IP, FQDN or server name. It will not establish a connection to view the shares available. I can ping or do just about anything else to it just not UNC or map drives for that matter.
The server is a fresh build, has no AV and Windows OS firewall is completely off.
On the server in question do you have network discovery turned on?
ref link: https://support.microsoft.com/en-us/kb/2722035
ref link: https://support.microsoft.com/en-us/kb/2722035
Correct. It is enabled.
3 of the 6 main subnets and offices can browse to the shares on the server in question error free.
I keep leaning towards networking or routing issues. Any thoughts on how to test or view or troubleshoot connectivity between two addresses via Cisco appliances ? I don't think this is a Windows configuration error.
3 of the 6 main subnets and offices can browse to the shares on the server in question error free.
I keep leaning towards networking or routing issues. Any thoughts on how to test or view or troubleshoot connectivity between two addresses via Cisco appliances ? I don't think this is a Windows configuration error.
Foxluv, that's a negative. It's using a Realtek driver. Not the VMXNet3 drivers.
Bryant, I am not familiar with the nmap utility. Could you elaborate a bit more on what command I should run and what I am looking for?
Bryant, I am not familiar with the nmap utility. Could you elaborate a bit more on what command I should run and what I am looking for?
Use the vmxnet3 drivers and test. I assume you have already installed the vmtools as well on that server, if not install those as well.
you will have to download, maybe get the zenmap gui, port scanning tool
we are looking for 137 138 139 and maybe 445
command
we are looking for 137 138 139 and maybe 445
command
nmap -p 1-65535 -T4 -A -v serverip
Foxluv, thanks for the input. I am only familiar on using that driver on ESXi. I'll loop back into that as a last resort.
Bryant, I downloaded the utility and your command crashes the program. However, I ran a similar command "intense" scan and the results are as follows.
Ports 137 and 138 do not show up on the server in question. Neither did they show up on servers that are healthy and error free.
Thoughts?
Bryant, I downloaded the utility and your command crashes the program. However, I ran a similar command "intense" scan and the results are as follows.
135/tcp unknown msrpc
139/tcp unknown netbios-ssn
445/tcp unknown microsoft-ds
Ports 137 and 138 do not show up on the server in question. Neither did they show up on servers that are healthy and error free.
Thoughts?
that would fine, 445 will be the important one, so it is open. And you confirmed they can ping/dns resolve the server? Are firewalls running on any of them? If so can you shut them down just to confirm
Bryant, yes. Firewall is fully disabled.
Im afraid I am still unable to connect. Going to look into enabling WINS but i dont think that will help much.
Im afraid I am still unable to connect. Going to look into enabling WINS but i dont think that will help much.
I've figured out my issue. By Disabling SMB 2 or modifying my Riverbed appliance for SMB 2 corrected my issues.
Thank you.
Thank you.
so the firewalls were not disabled, where did the riverbed come from? Happy you found the solution as it should have been working after everything we checked.
Bryant, I was led to believe by the Network Engineer before he left on vacation that the Riverbed appliance had been configured to work with all versions of SMB. Unfortunately, due to bad information it took me along for a ride of useless troubleshooting. Skipping the SMB protocols, for that I apologize.
However, Thank you for being helpful. I did learn new tools to work with (Nmap). At least something useful came out of this post.
However, Thank you for being helpful. I did learn new tools to work with (Nmap). At least something useful came out of this post.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now