Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Author Topic: Network Discovery  (Read 1364 times)

g3uiss

  • Kitizen
  • ****
  • Posts: 1151
  • You never too old to learn but soon I may be
    • Midas Solutions
Network Discovery
« on: December 05, 2019, 10:54:12 PM »

Sorry not sure if right section.

Quite a specialist question. I have just added a Server 2019 to an existing domain as a DC. I’ve made it the PDC. However since doing so, non of the clients or other DC can see a NAS in the Network area of explorer EXCEPT the 2019 Server. The NAS is not a domain member but was always visible before. It’s still accessible by unc path. I can’t see why the PDC can see it but no clients W10 or Servers on the domain.

Must be something to do with network discovery but I can’t find what

Perplexed Tony
Logged
Cerebus FTTP 500/70 Draytec 2927 VOXI 4G fallback.

d2d4j

  • Kitizen
  • ****
  • Posts: 1103
Re: Network Discovery
« Reply #1 on: December 05, 2019, 11:00:18 PM »

Hi guise

Could it by smb version difference or possibly GPO

It’s late so guessing I’m wrong but once on a network scanner we had an issue with ntml between scanner and PDC

Many thanks

John
Logged

tiffy

  • Kitizen
  • ****
  • Posts: 1319
Re: Network Discovery
« Reply #2 on: December 05, 2019, 11:56:24 PM »

Not sure if this could be relevent to your issue, otherwise ignore:

Network Devices Display in Explorer

It's a long post which I have had occasion to follow with respect to non-visibility of my LAN devices on Win 10 (Home in my case) explorer.
In my case, appears to be finally resolved with Win 10 update V.1909 which I have just implemented, others still report not.

Logged
BT FTTP 150/30, BT Smart Hub 2

g3uiss

  • Kitizen
  • ****
  • Posts: 1151
  • You never too old to learn but soon I may be
    • Midas Solutions
Re: Network Discovery
« Reply #3 on: December 06, 2019, 08:47:41 AM »

Thanks for suggestions. It’s not a W10 issue as there are other clients not seeing the device but I think GPO is possible I need to look in the Domain GPO as that’s possibly different now with the new DC.

Tony
Logged
Cerebus FTTP 500/70 Draytec 2927 VOXI 4G fallback.

g3uiss

  • Kitizen
  • ****
  • Posts: 1151
  • You never too old to learn but soon I may be
    • Midas Solutions
Re: Network Discovery
« Reply #4 on: December 09, 2019, 08:14:17 PM »

Guys

Just in case anyone runs into the same problem, I solved the issue by disabling the computer browser service on the 2019 PDC. I enabled it on a member server and behold all clients can now see devices in the network area. I know it’s standard practice to have the Master Browser on the PDC but something is different in 2019. So solved, can’t see any downside to the solution.

Netbios is very outdated but it’s still used fr legacy devices. Domain members get broadcast by Network Discover service nowerdays. Hope this info useful

Tony
Logged
Cerebus FTTP 500/70 Draytec 2927 VOXI 4G fallback.

dee.jay

  • ISP Rep
  • Reg Member
  • *
  • Posts: 953
Re: Network Discovery
« Reply #5 on: December 10, 2019, 08:02:14 AM »

Netbios is also very dangerous and should be turned off, particularly NBT-NS.

For a home environment I probably wouldn't be too worried, but in an any corporate setting, this setting can be disastrous if you get any nefarious actors in your network.
Logged
Starlink and AAISP L2TP combo routed by opnSense on proxmox