![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Hi All,
I have just started a new role as sole IT in a small company. The guy I replaced was not really into documentation so I am having to do a lot of digging to sort out small issues.
anyway the infrastructure consists of a Server 2008 DC which was also servs DNS and is used as a file and print server. It's working fine for the most part but a lot of the users are taking a long time to logon in the mornings which seems to be getting worse. There have been a couple of users and renaming their local profile seems to have temporarily solved the problems.
But today it's getting worse, I just built a new windows PC, added it to the domain but when I tried to logon to the network it took about 15 minutes for the network selections box to drop down.
So I have done some digging on the DC (company info changed):
ipconfig on local machines:
So on the local machines the DNS server is pointing to the DC but on the DC the dns server is pointing to a server than doesn't exist (192.253.168.13) as far as I can tell. Could this be causing the issues?
Where would the DNS on the DC usually point? I am going a bit mad on this one, I just can work out the answer.
I have this batch script which I would normally run on 2k3 DC's:
But I don't think this will make any difference on this server as the rogue DNS server is manually entered on the DC.
Any ideas? Sorry if these are pretty stupid questions but I am having a dumb day when it comes to my knowledge of Server 2008.
I have just started a new role as sole IT in a small company. The guy I replaced was not really into documentation so I am having to do a lot of digging to sort out small issues.
anyway the infrastructure consists of a Server 2008 DC which was also servs DNS and is used as a file and print server. It's working fine for the most part but a lot of the users are taking a long time to logon in the mornings which seems to be getting worse. There have been a couple of users and renaming their local profile seems to have temporarily solved the problems.
But today it's getting worse, I just built a new windows PC, added it to the domain but when I tried to logon to the network it took about 15 minutes for the network selections box to drop down.
So I have done some digging on the DC (company info changed):
Code:
C:\Windows\System32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : blablabla
Primary Dns Suffix . . . . . . . : asabove.co.uk
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : asabove.co.uk
co.uk
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-10-18-3D-5C-66
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::81ac:db54:3b5b:9d9b%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.253.7(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.253.1
DNS Servers . . . . . . . . . . . : ::1
192.168.253.13
127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabledipconfig on local machines:
Code:
Windows IP Configuration
Host Name . . . . . . . . . . . . : blablabla
Primary Dns Suffix . . . . . . . : asabove.co.uk
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : asabove.co.uk
asabove.co.uk
co.uk
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :asabove.co.uk
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Co
roller
Physical Address. . . . . . . . . : 00-1D-09-2F-73-5F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.253.117
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.253.1
DHCP Server . . . . . . . . . . . : 192.168.253.7
DNS Servers . . . . . . . . . . . : 192.168.253.7
Primary WINS Server . . . . . . . : 192.168.253.7
Lease Obtained. . . . . . . . . . : 10 October 2009 15:11:25
Lease Expires . . . . . . . . . . : 18 October 2009 15:11:25
Ethernet adapter Local Area Connection 3:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-A6-31-02-42So on the local machines the DNS server is pointing to the DC but on the DC the dns server is pointing to a server than doesn't exist (192.253.168.13) as far as I can tell. Could this be causing the issues?
Where would the DNS on the DC usually point? I am going a bit mad on this one, I just can work out the answer.
I have this batch script which I would normally run on 2k3 DC's:
Code:
net stop netlogon
net stop dns
net start dns
net start netlogon
ipconfig /flushdns
ipconfig /registerdns
nbtstat -R
nbtstat -RR
pauseBut I don't think this will make any difference on this server as the rogue DNS server is manually entered on the DC.
Any ideas? Sorry if these are pretty stupid questions but I am having a dumb day when it comes to my knowledge of Server 2008.
