Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 402
  • Last Modified:

Why does Windows need UDP connection from workstation UPD 138 and 389 to domain server it doesn't authenticate to?

Our workstations authenticate to a local DC.  From analyzing network traffic, they also seem to connect to UDP 138 and 389.  I'm not sure why.  Can anyone provide good solid explinations?  The stations don't seem to work otherwise.
0
awakenings
Asked:
awakenings
  • 3
1 Solution
 
awakeningsAuthor Commented:
UDP 138 is just NetBIOS.  The UDP 389 is LDAP ping.  Why is that needed?  There are ACL's blocking.  Any reason why these serves provent the station from functioning?
0
 
NJComputerNetworksCommented:
not sure... maybe this other server is providing other services like GC.  Can you better explain your environment and setup.....

Need more details...
0
 
awakeningsAuthor Commented:
The other server was the first DC.  It is at another site.  The local server is at our site.  Both are the same domain.  Both are DCs.  The stations log in to the local DC as they should.  They have the UDP connection attempts to the far DC.  I'm trying to determine why.  There are denies on network syslog for those services and probably prevent some things like changing passwords, etc.  Any idea why?

Awakenings
0
 
awakeningsAuthor Commented:
I've got everything worked out.  I'll give you points anyway.
0
 
emaudCommented:
Hi awakenings
we are curious to know what was the problem?
Thanks
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now