How do I get Server 2012R2 to see NAS and and PCs (only shows 3 PCs in the network out of 15+ devices.)
I have a DELL T630 with WINDOWS Server 2012R2 running AD, DNS, WINS. It has been working fine for over a year. All of a sudden it will not show anything but 3 of the PCs on my network (including itself). I have a second 2012R2 running as my 2nd AD with AD and DNS - it sees all. I am using Trend Micro WFBS (all systems) and Malwarebytes (only on this Server - I HAVE tested with these turned off AND then with both programs uninstalled) . The NIC is teamed and mapped through the VM NIC (Images NIC 1 & NIC 2)
Change adapter settings window:
I have checked Network discovery and followed a bunch of suggestions I found on the internet, but most of them were how to get a PC to see the DC, mine is the opposite. I noticed this two days ago when I tried to access one of the NASes from this server. It shows the WD NAS, no problem and connects OK, it will NOT allow access to the NetGear NAS either using either the UNC or IP address.
Using the UNC I get an error (see attached image 1).
Get the same error when using IP address, however It DOES show up in my network folder (both methods) as a "Media Device" (Image 2).
And it is accessible via IE (Image 3 & 4)
After providing credentials:
All PCs on this network and the other DC see everything and access all with no problems. We can all access both the NASs. I am lost on what is causing this and how to resolve it.
I need assistance on getting the PCs to show up in network and to access this NAS please.
Change adapter settings window:
I have checked Network discovery and followed a bunch of suggestions I found on the internet, but most of them were how to get a PC to see the DC, mine is the opposite. I noticed this two days ago when I tried to access one of the NASes from this server. It shows the WD NAS, no problem and connects OK, it will NOT allow access to the NetGear NAS either using either the UNC or IP address.
Using the UNC I get an error (see attached image 1).
Get the same error when using IP address, however It DOES show up in my network folder (both methods) as a "Media Device" (Image 2).
And it is accessible via IE (Image 3 & 4)
After providing credentials:
All PCs on this network and the other DC see everything and access all with no problems. We can all access both the NASs. I am lost on what is causing this and how to resolve it.
I need assistance on getting the PCs to show up in network and to access this NAS please.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I added the SMBv1 feature back on the AD2 server and also ran the following commands:
Powershell:
Set-SmbServerConfiguration
Command Line:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/n
sc.exe config mrxsmb10 start= auto
I rebooted and now I see everyone and can access the NAS.
So SMBv1 is the protocol that Windows uses to see other devices on the network too? I know it is the original file sharing transport, but how do I work around the protection vs. functionality issue? If I can update the Protocol that this NAS uses to SMBv/3 that would be fine, however if I cannot see any network devices and computers, that would be very difficult.
Powershell:
Set-SmbServerConfiguration
Command Line:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/n
sc.exe config mrxsmb10 start= auto
I rebooted and now I see everyone and can access the NAS.
So SMBv1 is the protocol that Windows uses to see other devices on the network too? I know it is the original file sharing transport, but how do I work around the protection vs. functionality issue? If I can update the Protocol that this NAS uses to SMBv/3 that would be fine, however if I cannot see any network devices and computers, that would be very difficult.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
To clarify:
I have two NASs on the network, the WD worked fine with SMBv1 disabled/uninstalled
I am running SERVER 2012R2 & Win7 or Win10 exclusively in this network (2 Mac Airs also connect when in the office)
The T630 IS a file server - this NAS was being used as additional storage for data I do now want to clutter the server. I have GBs of Microsoft, Adobe, etc. ISO's and installations that I use it for. Well over 1TB.
.
I am still curious as to why disabling the SMBv1 would cause my server to not see the rest of the network. Even each other (we know they are both SMBv2/3 compliant). Any thoughts?
I have two NASs on the network, the WD worked fine with SMBv1 disabled/uninstalled
I am running SERVER 2012R2 & Win7 or Win10 exclusively in this network (2 Mac Airs also connect when in the office)
The T630 IS a file server - this NAS was being used as additional storage for data I do now want to clutter the server. I have GBs of Microsoft, Adobe, etc. ISO's and installations that I use it for. Well over 1TB.
.
I am still curious as to why disabling the SMBv1 would cause my server to not see the rest of the network. Even each other (we know they are both SMBv2/3 compliant). Any thoughts?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm going to wait a little and see if anyone else chimes in on this, but I think you have helped resolve the NAS issue! Thank you for that. I will award points shortly.
I am glad to help. Have a great weekend!
ASKER
Although we did not resolve the repair, we did get to the bottom of the "Why". Thank you
ASKER
Both Servers have SMBv1 turned off (I just did this a week ago). I was able to see other PCs in the network folder from AD2, but now I cannot .
Yesterday when I was playing with the servers, I was able to see the NAS and all the PCs in the network from AD2, and access the NAS too. Now I cannot.
I was just checking on your observations when I discovered this.
I am going to enable the SMBv1 to see what happens. I do not quite understand why I would lose the other PCs even with SMBv1 turned off.
The NAS uses CIFS as the interface and they define: CIFS, or Common Internet File System, used predominantly by Windows. Mac OS X also supports this protocol though it may be referred to as SMB.
I will see if there is an update to SMBv2/3 from NetGear.
Thank you for this insight - I will see if turning it back on (2nd server) allows it to see other PCs and the NAS. I'll update you shortly.