Im troubleshooting different Workstation slowness scenarios, and one of the conserning event ID is 3210 which indicates some authorization issues between Client Computer and Domain. Also group policy errors (lack of connectivity to domain controller) follows this error.

Im tryng to solve this event ID 3210 issue without succsess, so far Ive done:

- Ports are opened between Client and DC (I ran portQui tests)
- Computer is patched 100%, also KB2958122 included.
- Computer account deleted, Computer re-joined to domain

• Edited by yannara Friday, May 22, 2015 8:06 AM

Hello,

How is your DNS configured on client machine & on DOmain controller. Check your Sites & Subents are configured correctly.

If possible enable debug logs for netlogon on client machine.

Enable : nltest /dbflag:0x2080ffff

Disabled: nltest /dbflag:0x0Ref: https://support.microsoft.com/en-us/kb/109626

enable the debug log then reboot the computer and you can ask user to login to machine. Once user is loged on to machine you can see there is log file %systemroot%\Debug. Upload the log file here

Hello,

How is your DNS configured on client machine & on DOmain controller. Check your Sites & Subents are configured correctly.

If possible enable debug logs for netlogon on client machine.

Enable : nltest /dbflag:0x2080ffff

Disabled: nltest /dbflag:0x0Ref: https://support.microsoft.com/en-us/kb/109626

enable the debug log then reboot the computer and you can ask user to login to machine. Once user is loged on to machine you can see there is log file %systemroot%\Debug. Upload the log file here

I forgot to mention, that our sites and services are up to date, every subnet is binded to a site and DC. Client gets DNS settings from DHCP scope, DNS servers veries depending on site, closest DC acts as DNS.

I'll get this logs and get back to this, thanks!

Hi,

 Try to take Wiresharke and filter any NTLM authentication method is coming out. If so, you should be add your nearest domain controller ip address on the "Exception list" in network device. It could be either riverbed, etc...and let me know.

Please share your answers.

Hi,

You are gettting envetid 3210 on machine. This is typically secure channel broken issue on lcient machine.

Try resetting the password for computer from below command. 

netdom resetpwd /server:server_name /userd:domain_name\administrator /passwordd:administrator_password

http://blogs.technet.com/b/asiasupp/archive/2007/01/18/typical-symptoms-when-secure-channel-is-broken.aspx

http://blogs.technet.com/b/heyscriptingguy/archive/2012/03/02/use-powershell-to-reset-the-secure-channel-on-a-desktop.aspx

Try resetting the password for computer from below command. 

netdom resetpwd /server:server_name /userd:domain_name\administrator /passwordd:administrator_password

As stated from the article,

netdom resetpwd /server:server_name /userd:domain_name\administrator /passwordd:administrator_password

Where server_name is the name of the server that is the PDC Emulator operations master role holder.

Note: This method only works for DC. If its member server, we have to disjoin and rejoin domain.

So, should I still try this command on a Client machine?

For client machine you can directly do it from ADUC.

Go to Active Directory Users and Computers MMC (DSA), you can right-click the computer object in the Computers or appropriate container and then click Reset Account. Reboot the client machine.

For client machine you can directly do it from ADUC.

Go to Active Directory Users and Computers MMC (DSA), you can right-click the computer object in the Computers or appropriate container and then click Reset Account. Reboot the client machine.

Hi,

What OS version did you talk about?

Please check the similar thread that has been discussed:

Event ID 3210

https://social.technet.microsoft.com/Forums/windowsserver/en-US/6aa6d977-03d6-4e73-9ff4-51cc2275903b/event-id-3210?forum=winserverDS

Regards.

Windows 7, SP1 patched up-to-date.

Okay I got one case here with extended logs, I renamed domain name and netbios name to domain.dom, not to reveal our Customer. Site is named as HKI.

Tracing started right after reboot, when the failure occured. Time stamp for 3210 is at 10:08:09. Are you able to view the file?

https://onedrive.live.com/redir?resid=87193aa6c859dc4e!120392&authkey=!AKD9Ul-lkuj_eh0&ithint=file%2ctxt

Thanks for all the help :)

• Edited by yannara 22 hours 29 minutes ago

Hi,

Can you check the setting of maximum machine account passowrd age is configurable through group policy:

Computer Configuration\windows Settings\Security settings\Local Policies\Security Options
Domain member: Maximum machine account Password age

make sure it is NOT disable machine password changes for security reasons. Maybe you can increase the maximum password age for Machines like laptops etc

Also from net logon log I can see  

05/25 10:08:09 [SESSION] DOMAIN: NlSetStatusClientSession: Unbind from server \\dc1.domain.dom (TCP) 0.

05/25 10:08:09 [SESSION] DOMAIN: NlSessionSetup: Session setup Failed

• Edited by Purvesh Adua 21 hours 40 minutes ago

Windows 7, SP1 patched up-to-date.

Okay I got one case here with extended logs, I renamed domain name and netbios name to domain.dom, not to reveal our Customer. Site is named as HKI.

Tracing started right after reboot, when the failure occured. Time stamp for 3210 is at 10:08:09. Are you able to view the file?

https://onedrive.live.com/redir?resid=87193aa6c859dc4e!120392&authkey=!AKD9Ul-lkuj_eh0&ithint=file%2ctxt

Thanks for all the help :)

• Edited by yannara Monday, May 25, 2015 8:31 AM

Hi,

Can you check the setting of maximum machine account passowrd age is configurable through group policy:

Computer Configuration\windows Settings\Security settings\Local Policies\Security Options
Domain member: Maximum machine account Password age

make sure it is NOT disable machine password changes for security reasons. Maybe you can increase the maximum password age for Machines like laptops etc

Also from net logon log I can see  

05/25 10:08:09 [SESSION] DOMAIN: NlSetStatusClientSession: Unbind from server \\dc1.domain.dom (TCP) 0.

05/25 10:08:09 [SESSION] DOMAIN: NlSessionSetup: Session setup Failed

• Edited by Purvesh Adua Monday, May 25, 2015 9:19 AM

IT seems there is an issue from client machine to Domain controller. Possible can you check the Switch port or network port for both Client PC & Domain controller.

I can see there were Error check the below article.

05/25 10:08:41 [MISC] NetpDcGetName: dc domain.dom similar query failed recently 10249

https://support.microsoft.com/en-in/kb/904943

• Edited by Purvesh Adua 13 hours 56 minutes ago

IT seems there is an issue from client machine to Domain controller. Possible can you check the Switch port or network port for both Client PC & Domain controller.

I can see there were Error check the below article.

05/25 10:08:41 [MISC] NetpDcGetName: dc domain.dom similar query failed recently 10249

https://support.microsoft.com/en-in/kb/904943

• Edited by Purvesh Adua Monday, May 25, 2015 5:04 PM

I gone through netlogon.log myself, and I picked up most intresting errors during startup and netlogon events:

05/26 08:49:01 [INIT]    DnsFailedDeregisterTimeout = 172800 (0x2a300)
05/26 08:49:01 [CRITICAL] DOMAIN: NlSessionSetup: Session setup: cannot I_NetServerReqChallenge 0xc0000022
05/26 08:49:01 [SESSION] DOMAIN: NlSetStatusClientSession: Set connection status to c0000022
05/26 08:49:01 [SESSION] DOMAIN: NlSessionSetup: Session setup Failed
05/26 08:49:06 [MISC] LoadBalanceDebug (Flags: FORCE DSP AVOIDSELF ): DC=DC1, SrvCount=1, FailedAQueryCount=0, DcsPinged=1, LoopIndex=0
05/26 08:49:06 [CRITICAL] NlPrintRpcDebug: Dumping extended error for I_NetServerReqChallenge with 0xc0000022
05/26 08:49:06 [MISC] Eventlog: 3210 (1) "DOMAIN" "\\DC1.domain.dom" 2f8270f1 5bc8d5e7 34c3e164 6665df64   .p./...[d..4d.ef

I dont wonder why you guys advice me to reset Computer account or password, because 0xc0000022 referes as accecc_denied to Domain (as I see it).

I have a plan what to do next - I will take a Client machine, locate if it has 3210 event, I then will remove that machine to a same subnet with DC and start to reboot it like crazy. This way I should see, if routing has something to do with that. Do you agree this testing should be done? Any other ideas? 

• Edited by yannara 36 minutes ago

Hi 

You said earlier you tried a fresh machine ( newly built) and added to domain still get the error ?.  You can try your plan however just wondering didn't you try the connectivity between client and server ?  port requirements ?

I gone through netlogon.log myself, and I picked up most intresting errors during startup and netlogon events:

05/26 08:49:01 [INIT]    DnsFailedDeregisterTimeout = 172800 (0x2a300)
05/26 08:49:01 [CRITICAL] DOMAIN: NlSessionSetup: Session setup: cannot I_NetServerReqChallenge 0xc0000022
05/26 08:49:01 [SESSION] DOMAIN: NlSetStatusClientSession: Set connection status to c0000022
05/26 08:49:01 [SESSION] DOMAIN: NlSessionSetup: Session setup Failed
05/26 08:49:06 [MISC] LoadBalanceDebug (Flags: FORCE DSP AVOIDSELF ): DC=DC1, SrvCount=1, FailedAQueryCount=0, DcsPinged=1, LoopIndex=0
05/26 08:49:06 [CRITICAL] NlPrintRpcDebug: Dumping extended error for I_NetServerReqChallenge with 0xc0000022
05/26 08:49:06 [MISC] Eventlog: 3210 (1) "DOMAIN" "\\DC1.domain.dom" 2f8270f1 5bc8d5e7 34c3e164 6665df64   .p./...[d..4d.ef

I dont wonder why you guys advice me to reset Computer account or password, because 0xc0000022 referes as accecc_denied to Domain (as I see it).

I have a plan what to do next - I will take a Client machine, locate if it has 3210 event, I then will remove that machine to a same subnet with DC and start to reboot it like crazy. This way I should see, if routing has something to do with that. Do you agree this testing should be done? Any other ideas? 

• Edited by yannara Tuesday, May 26, 2015 6:23 AM

Hi,

Yes based on your inputs and log provided by you we suggested to reset the machine. nothing else. If you have plan to do next please go ahead and once issue is resolved do update us.

Hi 

You said earlier you tried a fresh machine ( newly built) and added to domain still get the error ?.  You can try your plan however just wondering didn't you try the connectivity between client and server ?  port requirements ?

I ran portqui, but probably it wasnt enough, since yes, there is a difference between being in the same or different subnet with DC. At the same subnet, I never get 3210. At different subnet, I do get it 50/50.

I also found out, that some Computers and DC are erroring of Event ID 8003, believing a Computer being master browser. I started piloting a Computer Browser Service shutdown, will it have any improvement at all, or not.

I started piloting a Computer Browser Service shutdown, will it have any improvement at all, or not.

You can disabled the computer browser service on client machine.

hi,

Any updates on above?

hi,

Any updates on above?

Computer Browser Service has been disabled everywhere, but I dont believe it will effect AD authentification issues. It should deminish Event ID 8003 from DCs.

Im goint to test onsite tomorrow with Network guys, will they see anything during logon between different subnets. Because, when logging on from the same subnet with DC, 3210 does not appear ever.

I also notice event ID 5719 and winlogon 6005 and 6006, but I believe these are more common events which are not so dramatic as 3210. 

We suspect delay/timeout issues in routing. The thing is, that all other subnets are routed via remote location point (kind a data canter) back to the same site. Only clients in same subnet with DC are not routed. Our Network guys will probably fix this routing thingy. If this will be fixed with that, next thing will be to think, what to do with sites which are far, and without local DC (which are routed to the same datacenter).

There must be a some Group Policy which could control the timout times for netlogons and processing other GPOs. Or is there a demand specifications for remote site networking?

There must be a some Group Policy which could control the timout times for netlogons and processing other GPOs. Or is there a demand specifications for remote site networking?

You can check the below setting for Specifies the additional time that the Net Logon service waits for a response from a domain controller. If the domain controller does not respond before the total time allowed elapses, Net Logon assumes that the domain controller is not available, and it proceeds accordingly.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

• On the Edit menu, click Add Value. Value Name: ExpectedDialupDelay

https://technet.microsoft.com/en-us/library/cc957332.aspx?f=255&MSPPError=-2147217396

You can check the below setting for Specifies the additional time that the Net Logon service waits for a response from a domain controller. If the domain controller does not respond before the total time allowed elapses, Net Logon assumes that the domain controller is not available, and it proceeds accordingly.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

• On the Edit menu, click Add Value. Value Name: ExpectedDialupDelay

https://technet.microsoft.com/en-us/library/cc957332.aspx?f=255&MSPPError=-2147217396

Today I witnessed event ID 3210 where local DC is added propertly to a site with a valid subnet (meaning: AD sites and services config is correctly). The issue Im wondering (very much), is that this Workstation is trying to establish connection to a wrong DC (ID 3210 refers to a wrong DC). Anyway, I ran systeminfo and some nltest commands on this computer to make sure which DC is connection is established, and its the RIGHT one! After this, Im starting to thing, how important/valid this  ID 3210 is? Can I skip it?

Hi,

This is important error basically each member maintains such an LSA secret which is used by the Netlogon service to establish a secure channel. If, for some reason, the computer account's password and the LSA secret are not synchronized, the Netlogon service logs the event id 3210. You cannot skip this.

Can you also verify that valid subnet is configured in AD for computer or client machine IP.

Can you also verify that valid subnet is configured in AD for computer or client machine IP.

Hello 

IF the issue is not resolved, at this point what i would suggest or do is capture network traffic from both client and server .   From the out put you should be able to find out how the client queries the DNS , reply , KRB traffic and there you will get a clue where to troubleshoot further. 

I got an update from providers Network guys, that communication should now be established directly on a site (previously we were suspecting, that a client does hook to a datacenter and comes back to the local site, which is pure Network technology level, nothing to do with AD sites and services). Anyway, the issue isnt solved, I just witnessed today another events of 3210.

I just wonder, what happends if I set netlogon service startup to Automatic Delayed....

You can try that, But I would suggest do the network trace from both the client site & DC site. Once it is done provide us or upload the network capture to one drive or central location.

Hi,

You have to capture using the net Mon. It is tool for network monitoring. You have to installed the same on domain controller and on the client machine.

https://www.microsoft.com/en-in/download/details.aspx?id=4865

Hi,

You have to capture using the net Mon. It is tool for network monitoring. You have to installed the same on domain controller and on the client machine.

https://www.microsoft.com/en-in/download/details.aspx?id=4865

you can schedule or run the command without installing anything on client machine and capture the data.

netsh trace start persistent=yes capture=yes tracefile=c:\temp\nettrace-boot.etl

http://blogs.msdn.com/b/canberrapfe/archive/2012/03/31/capture-a-network-trace-without-installing-anything-works-for-shutdown-and-restart-too.aspx

Please upload the file once you have capture the data using above command.

Or

Using NETMON Capturing a Trace at Boot Up

http://blogs.technet.com/b/netmon/archive/2010/01/04/capturing-a-trace-a-boot-up.aspx

• Edited by Purvesh Adua 1 hour 8 minutes ago

you can schedule or run the command without installing anything on client machine and capture the data.

netsh trace start persistent=yes capture=yes tracefile=c:\temp\nettrace-boot.etl

http://blogs.msdn.com/b/canberrapfe/archive/2012/03/31/capture-a-network-trace-without-installing-anything-works-for-shutdown-and-restart-too.aspx

Please upload the file once you have capture the data using above command.

Or

Using NETMON Capturing a Trace at Boot Up

http://blogs.technet.com/b/netmon/archive/2010/01/04/capturing-a-trace-a-boot-up.aspx

• Edited by Purvesh Adua Thursday, June 25, 2015 5:52 AM

Hi,

Any updates on above?

I have closer looked the network trace and found that you are having many MSRPC error on your network. I advice you need to thoroughly check with network guy for ports and trace the RPC request from client machine  to server or DC IP address.

I have closer looked the network trace and found that you are having many MSRPC error on your network. I advice you need to thoroughly check with network guy for ports and trace the RPC request from client machine  to server or DC IP address.

• Marked as answer by yannara Wednesday, July 22, 2015 5:26 PM
• Unmarked as answer by yannara 13 hours 39 minutes ago

I have closer looked the network trace and found that you are having many MSRPC error on your network. I advice you need to thoroughly check with network guy for ports and trace the RPC request from client machine  to server or DC IP address.

• Marked as answer by yannara Wednesday, July 22, 2015 5:26 PM
• Unmarked as answer by yannara Tuesday, July 28, 2015 5:22 PM

Hi,

One of the client machine I need you to enable the following. then reboot the machine once you login back and netlogon file is created you need to disabled the settings using another command given below. Please upload the log file with   log on & log off time.

nltest /dbflag:0x2fffffff

Disabled: nltest /dbflag

Thank you for your help. I havent done the latest action you asked, but I posted netlogon.log results here earlier. I could do this next week maybe.

I also arranged some Network guy to work on this, he will troubleshoot that machine as an example with his own tools. I did take a look at another customer enviroment today, and aknowledged, that there is no similar 3210 events anywhere at 5-6 Computers there, so this 3210 isnt "By design". Though, I see lot of 5719 events everywhere I go, so that looks By design to me :)

I just sent latest logs to Adua. It contains Customer info, so I will not publish them here. Anyway, here are some relevant netlogon failures:

Failed to find domain cache entry with quality 0/5

Failed to find exact domain cache entry with quality 0/5

NlDiscoverDc: Cannot find DC.

NetpDcGetName: DOMAIN similar query failed recently 16

Hi,

I am not able to Download the file can you please past the URL or link here to download the same.

Hi,

I can see you are getting error  code 0xC0000022 which says below

There have been a lot of good suggestions, however I have seen issues similar to trust relationships / group policy errors when workstations are NOT properly syspreped. Can you ensure that they are syspreped properly?

Might be a long short but worth mentioning.

Will.

Hi,

I can see you are getting error  code 0xC0000022 which says below

• Marked as answer by yannara Wednesday, July 22, 2015 5:27 PM
• Unmarked as answer by yannara 13 hours 39 minutes ago

Hi,

I can see you are getting error  code 0xC0000022 which says below

• Marked as answer by yannara Wednesday, July 22, 2015 5:27 PM
• Unmarked as answer by yannara Tuesday, July 28, 2015 5:22 PM

There have been a lot of good suggestions, however I have seen issues similar to trust relationships / group policy errors when workstations are NOT properly syspreped. Can you ensure that they are syspreped properly?

Might be a long short but worth mentioning.

Will.

Yes, there was a discussion about sysprep in other forums etc concering similar issue. However, keep in mind, that this netlogon failure occures only between different subnets. A client being in same subnet with DC will NEVER get this failure. So I doubt image in sysprep be the issue here.

But if still the sysprep is suspected, and I was building those images with ConfMgr 2012, what I could do is, to install one Computer with Customers image, drop it to workgroup and add this Computer to my own LAB AD. I also have multiple subnets. Will this confirm, that image and syspreping is not the reason here?

• Edited by yannara 11 hours 38 minutes ago

Something like the is very sporatic when it comes to Syspreping. There are times where you can re-image a machine without syspreping and it continue to work (how i do not know). Then there are other times where some machines will be affected and not others. This is really a random scenario, which is why i stated this might be a long shot in my original post.

If i were you I would just take a machine use the internal sysprep.exe /generalize > reboot > add to the domain and see if you get the same issue. I am not aware of any specific way to do this the SCCM. However, you can do this right from the workstation itself.

Will.

There have been a lot of good suggestions, however I have seen issues similar to trust relationships / group policy errors when workstations are NOT properly syspreped. Can you ensure that they are syspreped properly?

Might be a long short but worth mentioning.

Will.

Yes, there was a discussion about sysprep in other forums etc concering similar issue. However, keep in mind, that this netlogon failure occures only between different subnets. A client being in same subnet with DC will NEVER get this failure. So I doubt image in sysprep be the issue here.

But if still the sysprep is suspected, and I was building those images with ConfMgr 2012, what I could do is, to install one Computer with Customers image, drop it to workgroup and add this Computer to my own LAB AD. I also have multiple subnets. Will this confirm, that image and syspreping is not the reason here?

• Edited by yannara Monday, July 20, 2015 7:23 PM

If i were you I would just take a machine use the internal sysprep.exe /generalize > reboot > add to the domain and see if you get the same issue. I am not aware of any specific way to do this the SCCM. However, you can do this right from the workstation itself.

Will.

Thank you! I will defenetly do that! Sysprep is something which is fully automatizated in Windows7/SCCM structure, so image builders do not have to worry about it.

Additional question, do I need to drop this machine to workgroup and delete AD account before syspreping?

Greetings,

                  As we see that network is the backbone of computing, netlogon errors usually occur in failing RPC binds with the DC, Please check for issues in firewalls or anyother network entities like riverbed etc.

"

Additional question, do I need to drop this machine to workgroup and delete AD account before syspreping?

"

It would probably be in your best interest to ensure that the computer account is also deleted. This ensure that the SID of the computer object is not being used over again.

Will.

Greetings,

                  As we see that network is the backbone of computing, netlogon errors usually occur in failing RPC binds with the DC, Please check for issues in firewalls or anyother network entities like riverbed etc.

Every communication between the domain client and the controller is carried out with a RPC Bind. If there are issues in a network device (say the RPC is getting dropped by a router) between the client and the server, the communication would not succeed. so we request you to do he following.

1. tracert to the DC from the client and check what is the network path of the communication.

2. As requested by others in the forum, to capture a network trace to check why the RPC is failing to create netlogon issues.

3. normally we have stick to the network part of the troubleshooting as netlogon issues are majorly generated in the network layer and not in the application layer of the OSI layers.

Thanks

Eric

2. As requested by others in the forum, to capture a network trace to check why the RPC is failing to create netlogon issues.

Well, from the start I did this portQui test to DC, and it didnt show me any errors. Isnt this enough?

The problem is, that Im not familiar with Network tracing and sniffering tools, and would be happy to leave this job to our networking guys :)

I got some new test results!

1. Sysprep /generilize broke the Windows OS. After doing that, OS does not start anymore because of some .sys file.

2. I ran portqui again, and took careful look at the results. HAH! There is a failure to LDAP 389 port, when running Active Directory testing! I dont know why we didint noticed that last time, when looking through with my callegue. I even did this test 2 times, and then confirmed in my LAB without any firewalls, that portqui shows my LDAP being opened.

Ok,

Glade to hear that you find out an issue. if everything is fine please propose this as answer.

Our Network engineer is uncapable to find or trace anything which would releate to this.

Another of our Customer enviroment, where there is absolute no 3210 error, portqui is clean from errors too.

Hi,

you can ask Network engineer or yourself for what all required port it should listen to and then use port query Command to see if it is listening to both TCP or UDP.

portqry -n 10.6.11.5 -e 3269 -p both

 3268

53

88

389

135

137

123 etc are the few ports you can query and see the result from client machine, based on that he can check on network if it is allowed or not.

• Edited by yannara 13 hours 37 minutes ago

• Edited by yannara Tuesday, July 28, 2015 5:23 PM

In LAB by default all standard ports were allowed and works fine. If LDAP port on production network is not working in that case it has to be some block by network on this. Please speak to network team. As earlier viewing the network monitor trace uploaded by you & debug log it was clear that it is an issue from network end.

Please feel free to update us with your testing results with network and get back to us.

In LAB by default all standard ports were allowed and works fine. If LDAP port on production network is not working in that case it has to be some block by network on this. Please speak to network team. As earlier viewing the network monitor trace uploaded by you & debug log it was clear that it is an issue from network end.

Please feel free to update us with your testing results with network and get back to us.

hi,

Following were the few error in your log file. Anyway Once you identify with your local network team do update us.

05/25 10:08:09 [SESSION] DOMAIN: NlSetStatusClientSession: Unbind from server

05/25 10:08:09 [SESSION] DOMAIN: NlSessionSetup: Session setup Failed

05/25 10:08:41 [MISC] NetpDcGetName: dc domain.dom similar query failed recently

Hi,

Any updates on above?

Hi,

Any updates on above?

As I wrote before, I cannot ping port 389 UDP locally from UDP. This needs to be solved first. This 2008 R2 production DC doesnt reply on itself. My 2012 DC in lab does reply with portqui.

Network team will not do anything.

Hi,

You can download the tool. from below link download the Command line tool.

http://nmap.org/download.html

Make sure you run this tool from any machine in domain

Extract the tool in C drive and then go to command prompt run as administrator and run the below command

nmap -sU IPaddressofdomaincontroller >>output.log

Upload the log file here.

Sample Log file below

Nmap scan report for 101.187.12.178
Host is up (0.0025s latency).
Not shown: 999 open|filtered ports
PORT    STATE SERVICE
137/udp open  netbios-ns

Nmap done: 1 IP address (1 host up) scanned in 23.48 seconds

Hi,

Any updates on above?

Sorry, Ive been busy with W10 :)

I haventt got time for ran that thingy you suggest, but our Network experts found one possible reason, that W2008 box might not reply on UDP 389 because IPv6 is not enabled. Our server production team will probably do this change.

Hi,

Any updates on this else we can close this case when you have time open the fresh case for the same and give this case reference.

Hi,

Any updates on this else we can close this case when you have time open the fresh case for the same and give this case reference.

• Edited by yannara 8 hours 19 minutes ago

Hi,

Any updates on this else we can close this case when you have time open the fresh case for the same and give this case reference.

• Edited by yannara Friday, August 14, 2015 10:42 PM

Hi,

Any updates on issue?