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

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

Windows 7 64-bit logon to Windows 2008 DC slow.

Hello;

I just read some articles to mention that why the Windows 7 slow logon to Windows 2K8 DC, some articles said that if the DC is a multi-home server, it will cause this problem.

I am not sure if it is 100% apply to my case but my DC is a multi-home server because it is running as a file server too and this server has 3 network interfaces, one for LAN and 2 for iSCSI SAN.  The ip address for iSCSI SAN is different from LAN.

This server is the first DC in my domain and I have another 2 DCs in LAN as backup.   My current DNS is pointing to there

IP address : 192.168.1.55
Subnet mask : 255.255.255.0
Gateway : 192.168.1.254
DNS Server: 192.168.1.3, 192.168.2.1, 192.168.1.2

The ip 192.168.1.2 is my first DC.  

Based on this information, how can I improve the user's logon speed?
0
KANEWONG
Asked:
KANEWONG
  • 2
  • 2
2 Solutions
 
kevinhsiehCommented:
On the interfaces being used for iSCSI, disable all protocols and services except for TCP/IP. Under TCP/IP, tell it not to register the connection in DNS (under TCP/IP advanced tab).

run "ipconfig /registerdns" from an elevated command prompt on the DC. If you check DNS, you should see only the main IP address of the DC listed in DNS. Delete all references to the IP addresses used for iSCSI.
0
 
KANEWONGAuthor Commented:
I checked the DNS tab of TCP/IP on network interface for iSCSI, they have been disable for DNS since setup.  When I looked at the DNS server, even though I removed the one I don't need but it come back automatically.   I am not sure if because the DNS for DC and this iSCSI are on the same box.
0
 
kevinhsiehCommented:
Add a static DNS entry for your DC, and clear "Allow any authenticated user to update DNS records...".  Delete all of the dynamic entries for your DC. This should prevent the DC from registering additional IP addresses into DNS.
0
 
Darius GhassemCommented:
First you need to go into DNS make sure DNS is listening on only one IP address.

http://technet.microsoft.com/en-us/library/cc759481(WS.10).aspx

You should not be running a multihomed server as a Domain Controller.


0
 
Darius GhassemCommented:
One more thing as well. Go to your Network Connections click Advance Settings make sure your primary NIC is listed first
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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