DNS Server Problems

[mbtransport]

Hello All,
I am trying to get my network moved over from the old school "Workgroup" to a domain. I have been messing around with everything for some time now and I guess I sorta figured out what i've been doing. I am having some problems getting my DNS settings to allow for the DC and Clients to access the internet. I have already googled and googled and googled as well as searched all over. Can someone help me? I am sure that it is a simple fix but i'm a little confused on getting it all setup and setup correctly DNS wise.

Thank You
P.S. Please keep the heckling to a minimum, its friday.

 

[hairlessupportmonkey]

explain how you have configured DNS now and what is happeneing? can the server browse the web? Have you added external DNS servers in your DNS settings to allow for external browsing? does local machine browsing (SMB etc) work ok? \\<machinename>.<domain>

ACSS - SME
General Geek

 

[hairlessupportmonkey]

found this little guide:

http://www.google.co.uk/url?sa=t&rc...sg=AFQjCNHVa3CPxUSGkiJF9Q8SSf4d20j3dA&cad=rja

ACSS - SME
General Geek

 

[hairlessupportmonkey]

Also, Im guessing you have run DC Promo on the server to install and configure AD and you are using DHCP server on the server rather than the router?

ACSS - SME
General Geek

 

[ShackDaddy]

The server should point ONLY to itself for DNS in the NIC properties.

The server can point to the ISP or external DNS servers in the Forwarders tab (in DNS Admin, get Props on the server name).

The clients should ONLY point to the internal domain controller for DNS. Do not configure them to point to outside DNS servers.

If you follow these three rules, you should be ok.

Dave Shackelford
ThirdTier.net
TrainSignal.com

 

[kmcferrin]

The server should point ONLY to itself for DNS in the NIC properties.

Err...not quite. If you only have a single DC/DNS server then it should point to itself. If you have multiple DCs/DNS Servers then they should put to the other DCs/DNS Servers for primary and secondary DNS (and so on), and then list the loopback address (127.0.0.1) for the very last DNS server on the list.

________________________________________
CompTIA A+, Network+, Server+, Security+
MCTS:Windows 7
MCSE:Security 2003
MCITP:Server Administrator
MCITP:Enterprise Administrator
MCITP:Virtualization Administrator 2008 R2
Certified Quest vWorkspace Administrator

 

[ShackDaddy]

Are we writing universal rules in each thread, or are we responding to the OP's described environment? My rules are given in the context of the OP's referring to "the DC". Obviously the OP needs to have things laid out as clearly and simply as possible.

Dave Shackelford
ThirdTier.net
TrainSignal.com

 

[kmcferrin]

The OP may have only a single DC (not a recommended configuration), or they may not. But even if they do, it's important to at least qualify your statement to say that the DC should point to itself ONLY in a situation where it is the sole DC/DNS server. Otherwise, the OP (or someone else) may see this statement:

The server should point ONLY to itself for DNS in the NIC properties.

...and because it has no context erroneously assume that this is always the case. It's not. In fact, having the DC point ONLY to itself is applicable ONLY in single-DC cases.

________________________________________
CompTIA A+, Network+, Server+, Security+
MCTS:Windows 7
MCSE:Security 2003
MCITP:Server Administrator
MCITP:Enterprise Administrator
MCITP:Virtualization Administrator 2008 R2
Certified Quest vWorkspace Administrator

 

[mbtransport]

Yes I only have one server running. Sorry I haven't been back on in sometime. I have everything going smooth until today. I had a workstation kick off the network and I can't get it back to join or anything at all. The user was using it and just went off. I'm thinking everything is fine server wise because other users are not having any problems but it very well could be some setting somewhere that is causing all this mess.

On the workstation it is saying network cable unplugged. Then I finally satisfy that error and it only connects for a short time then goes off again.

 

[cmeagan656]

...it is saying network cable unplugged.

Bad NIC on the client or bad port on the switch. I've had both cause the same issue. Try changing the client to another port on the switch first.

Also, on one client when the caps were starting to go I got a similar error except in that case it was non-stop dropping from and connecting to the network.

Hope this helps.

Please help us help you. Read Tek-Tips posting polices before posting.
Canadian members check out Tek-Tips in Canada for socializing, networking, and anything non-technical.

 

[mbtransport]

Thanks for that. After jacking with it for a few hours I went to the control room and literally hit the switch and it straightend it out!

Now my problem is off topic but hopefully someone has a solution.

When I'm trying to login to this computer(vista) using username and passwords it says "username or password is incorrect"

I know the passwords and usernames are correct. And can ping the DC. and don't show any errors. Any ideas?

 

[cmeagan656]

Make sure that you are logging on to the domain, not as a local account.

Try domain\username for the the username.

Make sure that your scroll lock or caps lock isn't stuck. Open notepad and type some uppercase/lowercase/numerical garbage and check that it displays as expected.

Hope this helps.

Please help us help you. Read Tek-Tips posting polices before posting.
Canadian members check out Tek-Tips in Canada for socializing, networking, and anything non-technical.