Random DNS Wierdness on 2000 DC

  • Thread starter Thread starter joshd
  • Start date Start date
J

joshd

I have a Windows 2000 Domain Controller that doubles as a Terminal
Server. This box performs file-sharing, print services, DNs for Active
Directory, and the afformentioned Terminal Services. We just got this
box set up around 2 1/2 weeks ago, and the last several days I've
noticed that occasionally we'll have problems resolving WWW addresses
and displaying websites. We are an ISP and perform our own DNS for our
customers on our public network, but this server is an internal box
only designed for employees to use. All I have to do to correct the
problem is to cycle the DNS Server service on this server and
everything is back to "normal". My problem is, I can't always be here
to cycle the service, and I'm not seeing any errors in the Event Viewer
under the DNS group. The only thing I'm seeing (even though it's set
to log all events) is when I am stopping and restarting the service.

Has anyone else had this problem and/or might know how to alleviate it?
Thanks!
 
I have a Windows 2000 Domain Controller that doubles as a Terminal
Server.
Click to expand...

This is a Bad Idea. You should not host terminal services in application
mode on a DC - it should be a separate member server in your domain. TS in
admin mode for admin use only (remote management) is fine....don't let users
log into it, and don't install any desktop applications on it.
This box performs file-sharing, print services, DNs for
Active Directory, and the afformentioned Terminal Services. We just
got this box set up around 2 1/2 weeks ago, and the last several days
I've noticed that occasionally we'll have problems resolving WWW
addresses and displaying websites. We are an ISP and perform our own
DNS for our customers on our public network, but this server is an
internal box only designed for employees to use. All I have to do to
correct the problem is to cycle the DNS Server service on this server
and everything is back to "normal". My problem is, I can't always be
here to cycle the service, and I'm not seeing any errors in the Event
Viewer under the DNS group. The only thing I'm seeing (even though
it's set to log all events) is when I am stopping and restarting the
service.

Has anyone else had this problem and/or might know how to alleviate
it? Thanks!
Click to expand...

What's your AD DNS setup? Run ipconfig /all on this server & report back.
 
I have a Windows 2000 Domain Controller that doubles as a Terminal
Server.
Click to expand...

This is a Bad Idea. You should not host terminal services in
application
mode on a DC - it should be a separate member server in your domain. TS
in admin mode for admin use only (remote management) is fine....don't
let users log into it, and don't install any desktop applications on
it.

- I know, but I have no choice in the matter.

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\Administrator.ABS13>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : abs13
Primary DNS Suffix . . . . . . . : absinc.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : absinc.local

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 S Server
Adapter #3

Physical Address. . . . . . . . . : 00-02-B3-4C-96-F4
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.50.13
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 204.252.61.10
204.252.61.2
Primary WINS Server . . . . . . . : 204.252.61.2

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 S Server
Adapter #2

Physical Address. . . . . . . . . : 00-02-B3-4C-96-AC
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.25.100.13
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.25.100.254
DNS Servers . . . . . . . . . . . : 10.25.100.13
C:\Documents and Settings\Administrator.ABS13>
 
This is a Bad Idea. You should not host terminal services in
application
mode on a DC - it should be a separate member server in your domain.
TS in admin mode for admin use only (remote management) is
fine....don't let users log into it, and don't install any desktop
applications on it.

- I know, but I have no choice in the matter.
Click to expand...

Why not? At the very least, make sure your boss knows that you've
recommended against this - and get it in writing, and save it for future
posterior coverage.
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\Administrator.ABS13>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : abs13
Primary DNS Suffix . . . . . . . : absinc.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : absinc.local

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 S Server
Adapter #3

Physical Address. . . . . . . . . : 00-02-B3-4C-96-F4
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.50.13
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 204.252.61.10
204.252.61.2
Primary WINS Server . . . . . . . : 204.252.61.2

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 S Server
Adapter #2

Physical Address. . . . . . . . . : 00-02-B3-4C-96-AC
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.25.100.13
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.25.100.254
DNS Servers . . . . . . . . . . . : 10.25.100.13
C:\Documents and Settings\Administrator.ABS13>
Click to expand...

Another generally Bad Idea - multihomed DCs. This is not recommended. I'd be
pretty afraid of this server.

Also - your LAN NIC needs to specify *only* the internal DNS server's IP in
its IP config....no external DNS server IPs for any servers or clients on
your LAN. And where is that WINS server located - why is it a public IP? And
why no default gateway on the internal NIC? Are you using ISA on this box as
well?
 
Sorry, but we have limited funds and need certain functionality out of
one box. That's my boss' bottom line.

The box is multi-homed because of a wireless network infrastructure
that is tied to the 172.16.50.X subnet -> this box is used to manage
those devices. I should change DNS for sure. As far as the WINS
server goes, I'm not even sure why that's in there...we're not running
WINS. I'll have to make some changes on that for sure. Do you suppose
the DNS settings on that NIC might be causing my problems?

I set this DC up w/ DNS and so forth with Microsoft on the phone and
they told me how to do it to make it work right, except that they
probably neglected to tell me to change the DNS and WINS settings on
that 172... card.
 
Back
Top