Mark Minasi's Tech Forum
Register Calendar Latest Topics Chat
 
 
 


Reply
  Author   Comment  
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 152
Reply with quote  #1 
Some of our users are having a strange problem.  When they start the PC and click on the Explorer icon on the Taskbar Explorer won't start.
But if they right click on that icon and choose one of the (previously opened) folders then Explorer starts fine and opens that folder.  Or if they hit WINDOWS+E Explorer starts normally. Or even if they just wait for 10 to 15 minutes it works fine.
All clients are Win7.

The last thing we changed, and the problem started that same day, is that we upgraded our AD domain.
We have several DC's in multiple sites, all DC's are Win2008R2, single domain.  DFL and FFL is Win2008R. We installed 2 Win2016 servers and promoted them as DC.
We have the problem only in our main site, where we installed the new DC's Win2016.  One of the old DC's Win2008R2 is still online, the other one is demoted and disconnected.

Anyone seen this ? Anyone with a solution or even a hit to a solution ?


__________________
Pieter Demeulemeester
0
wkasdo

Avatar / Picture

Administrator
Registered:
Posts: 188
Reply with quote  #2 
Can't be related to the AD version, but perhaps you have an indirect effect. For instance, this sounds a little like you had DFS-N roots on the old DCs that you did not replace?
__________________
[MSFT]; Blog: https://blogs.technet.microsoft.com/389thoughts/
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 152
Reply with quote  #3 
Hi Willem,
I think you're spot on. Thanks man !
I've added the new DC to the Domain Based Namespace  \\MyDomain.com\MyNamespace and I can't simulate the problem anymore. Tomorrow I'm at the office and I'll check again. 

__________________
Pieter Demeulemeester
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 152
Reply with quote  #4 
No luck. Problem still exists.  :-(


__________________
Pieter Demeulemeester
0
wkasdo

Avatar / Picture

Administrator
Registered:
Posts: 188
Reply with quote  #5 
It's a local thing on those Win7 machines. Question is, how much effort do you want to invest? A new profile is one solution, for real troubleshooting I might try procmon to see what is happening.
__________________
[MSFT]; Blog: https://blogs.technet.microsoft.com/389thoughts/
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 152
Reply with quote  #6 
A new profile on the Win7 machine doesn't solve the problem.
We've - I mean an external consultant has - looked with Procmon, nothing came out.

>> Question is, how much effort do you want to invest ?
Problem is that I'm stuck with my DC rollout as long as I have that problem.

__________________
Pieter Demeulemeester
0
wkasdo

Avatar / Picture

Administrator
Registered:
Posts: 188
Reply with quote  #7 
> Problem is that I'm stuck with my DC rollout as long as I have that problem

You need to start excluding stuff.
- it can't be core AD itself. Authentication and authorization are clearly working.
- IF it is a DC problem, it is probably something missing that was present on the old DC, like
-- DFS root
-- Printers
-- shares
-- NetBIOS Browser service turned off (meaning network neighborhood failing)

If procmon fails, the next step is wireshark/netmon. Explorer waits for something: what exactly?

__________________
[MSFT]; Blog: https://blogs.technet.microsoft.com/389thoughts/
0
lady_mcse

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 83
Reply with quote  #8 
It's been so long since I've had to troubleshoot something like this ... at least 7 years, so I'm sure things have changed drastically with Win7 and Win2016.

However, it does smell a lot like a problem we had at my previous company, where we shut down an old file share and all of a sudden many machines were deathly slow, unresponsive, just not behaving like they should.  Power back up and everything was fine (but we wanted to kill the server, so it wasn't).  

I think we ended up finding a registry key buried deep somewhere that referenced the old server.  Rusty brain says it was something to do with "network browser" perhaps?  In fact I think my very short term workaround was to set up a bogus DNS record pointing DEADSERVERNAME at an IP address for a server that was up and running, so that clients would at least get an "i don't know what you're talking about" from something alive sooner than the client sitting around trying to hear back from a dead server.  Then our full solution was to hit up all the registries (less than 50 machines) and remove the bad entries.

Not sure if that's enough information to be of any assistance, but I guess the summary is that I think I'd be inclined to look for traffic trying to get at the server(s) you've decommissioned.
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 152
Reply with quote  #9 
Thanks for the reply Anne.  We're still searching.

At this moment it has something to do with :
- logonscripts (fewer problems if no logon script)
- redirected Desktop and Favorites folder to Win2008R2 fileserver (recently patched to SP1)
- new Win2016 DC in Win2008R2 AD environment
- speed (fewer problems if connected to 100 Mbit switch)
- roaming profiles (fewer problems without roaming profile)

I let the forum know if we found it.


__________________
Pieter Demeulemeester
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 152
Reply with quote  #10 
I'd like to add this:
When the problem appears (click on Explorer shortcut on the Taskbar gives an error, Win+E works fine) the Network and Sharing Centre shows NO network connection.

NoNetwork.jpg 
(screenshot in Dutch, sorry I have no English screenshot)


__________________
Pieter Demeulemeester
0
wkasdo

Avatar / Picture

Administrator
Registered:
Posts: 188
Reply with quote  #11 
When the machine is in this state, can you troubleshoot network connectivity?
- ipconfig
- ping gateway /t
- ping DC /t
- nslookup some domain names

A problem as obvious as this should be solvable [biggrin]

__________________
[MSFT]; Blog: https://blogs.technet.microsoft.com/389thoughts/
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 152
Reply with quote  #12 
Hi Willem,
Can't test it now, but when the problem happens we have a 'normal' ipconfig and we can ping to another host.
We've brought the new DC's offline and the problem has gone (3 days now). Grrr.

__________________
Pieter Demeulemeester
0
wkasdo

Avatar / Picture

Administrator
Registered:
Posts: 188
Reply with quote  #13 
You are chasing something strange here. Broadcast storm due to bad NIC on one of the new machines, maybe?

No repro, no progress...

__________________
[MSFT]; Blog: https://blogs.technet.microsoft.com/389thoughts/
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 152
Reply with quote  #14 
In the meantime I was able to test it in a second site, same results.

It seems like removing SIDhistory (from a previous NT4 to AD2003 migration) solves my problem. [smile]
And MS released a new hotfix that should solve my problem : https://support.microsoft.com/en-us/help/4022715

"Addressed an issue where users on Windows 7 SP1 clients connecting to a Windows Server 2016 based domain controller cannot run applications such as Internet Explorer for a period of approximately 10 minutes after logging on. This issue occurs after upgrading the enterprise domain controllers to Windows Server 2016."

Many thanks Willem.





__________________
Pieter Demeulemeester
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.