tgrizzel
asked on
Exchange Management Console is very slow and eventually gets an "End Snap-in" error. Beleive its related to WINS
here is the quick layout:
Have had Exchange server 2007 up and running for about 2 months. Recently I put new Domain Controllers up and demoted the the old ones. In addition to being DC's, 1 was a WINS server. About this same time it started taking a very long time to open the EMC and EMS for exchange 2007 (upwards of 2 minutes). Finally you will recieve a "end snap in" error, however if you press cancel, you can do what you need to do.
By searching around, I have already tried lowering the amount of users that are "preloaded" upon opening, however this did not help...additionally we only have 300 objects.
The reason I believe it is WINS is because we ran into this error when we first started setting up exchange is a test environment. We found that by turning on the "enable netbios over tcp/ip" within the network adapters settings that this problem stopped. However now that I have brought down the old WINS, and now even brought up a new WINS and pointed this to the correct IP, this is still happening.
I would like to phase netbios/wins out all together, however it seems as though some things are still relying on it. I have also looked at the binding settings for the network cards and NETBIOS is not even listed as a protocol to place lower in the chain....
Any thoughts?
Travis
Have had Exchange server 2007 up and running for about 2 months. Recently I put new Domain Controllers up and demoted the the old ones. In addition to being DC's, 1 was a WINS server. About this same time it started taking a very long time to open the EMC and EMS for exchange 2007 (upwards of 2 minutes). Finally you will recieve a "end snap in" error, however if you press cancel, you can do what you need to do.
By searching around, I have already tried lowering the amount of users that are "preloaded" upon opening, however this did not help...additionally we only have 300 objects.
The reason I believe it is WINS is because we ran into this error when we first started setting up exchange is a test environment. We found that by turning on the "enable netbios over tcp/ip" within the network adapters settings that this problem stopped. However now that I have brought down the old WINS, and now even brought up a new WINS and pointed this to the correct IP, this is still happening.
I would like to phase netbios/wins out all together, however it seems as though some things are still relying on it. I have also looked at the binding settings for the network cards and NETBIOS is not even listed as a protocol to place lower in the chain....
Any thoughts?
Travis
It's probably a DNS issue. Is your Exchange server IP stack pointed at the new DNS server? Do you have multiple sites and is the DC to site coverage mapped correctly. Had this same problem and it was related to the stand-up of a new DC that went off-site.
did you transfer all the FSMO roles when you changed the DC? http://support.microsoft.com/kb/324801
Also if you did transfer the FSMO then the server that held the roles should be removed from the network (disconnected)
eb
Also if you did transfer the FSMO then the server that held the roles should be removed from the network (disconnected)
eb
ASKER
we only have one site....
the dns settings are entered as static addresses (correctly) in the tcp/ip properties as well as in the emc.
DNS is a deffinete possibility, however this should have replicated just fine from the old DNS.
Is there somewhere I could be missing?
the dns settings are entered as static addresses (correctly) in the tcp/ip properties as well as in the emc.
DNS is a deffinete possibility, however this should have replicated just fine from the old DNS.
Is there somewhere I could be missing?
ASKER
Thank you EBJERS, however I did transfer all FSMO succesfully and then promoted the other DC's.
however when I do a dcdiag on the new DC's, I do get an error:
Starting Test: Machine Account
Warning : Attribute userAccountControl of "DC" is: 0x82020 = blah blah blah.......
This may be affecting replication?
I assumed this is a different problem.... maybe not though?
however when I do a dcdiag on the new DC's, I do get an error:
Starting Test: Machine Account
Warning : Attribute userAccountControl of "DC" is: 0x82020 = blah blah blah.......
This may be affecting replication?
I assumed this is a different problem.... maybe not though?
I too am having the same issue. Management console takes a long time to load and when it does, end snap-in message pops up. Has anyone found out why this is so?
ASKER
I looked at these sites and did make the recomended change, however this did not fix the original problem which is the snap-in taking a very long time to load...upwards of 5 minutes. Eventually I too get the "end snap-in" however if i press cancel I am able to work within the console.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I ran that command, but again everything was working fine till this recent issue, where we fixed some wrong dns enteries and also transfered the fsmo roles to this 2nd server, although both servers are online, but the management console is veeeeery slow to load even if i go into shell mode its faster but still slow to load when it says connecting to (servername)
command.jpg
command.jpg