Question Locked

Need assistance: unable to join workstations to win 2003 domain: DNS Issue

0 helpful
74 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Not sure if this is a domain controller issue or a DNS issue, but for some reason I cannot get my workstations to join my domain. My DC and my Exchange server are the same, and I have DNS running on this server as well. I can get email perfectly (though outlook 2007 cannot seem to find the server for the out of office assistant) and can access any and all shares on the server, ping by name and by IP.
Below is what I get when I do a DCDIAG on the server ( sorry its long):

C:\Documents and Settings\jason.LIGHTHOUSE>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\MAIL
Starting test: Connectivity
The host d7656a0c-ec8f-431b-a213-0d7659a7521d._msdcs.lighthouse.local c
ould not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(d7656a0c-ec8f-431b-a213-0d7659a7521d._msdcs.lighthouse.local)
couldn't be resolved, the server name (Mail.lighthouse.local) resolved
to the IP address (192.168.2.51) and was pingable. Check that the IP
address is registered correctly with the DNS server.
......................... MAIL failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\MAIL
Skipping all tests, because server MAIL is
not responding to directory service requests

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : lighthouse
Starting test: CrossRefValidation
......................... lighthouse passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... lighthouse passed test CheckSDRefDom

Running enterprise tests on : lighthouse.local
Starting test: Intersite
......................... lighthouse.local passed test Intersite
Starting test: FsmoCheck
......................... lighthouse.local passed test FsmoCheck

C:\Documents and Settings\jason.LIGHTHOUSE>

I am guessing that its that first part that is killing me but for the life of e I cant figure out how to resolve it. Any ideas?

74 replies

by shasca

Yep the error says it's a DNS problem. Any possibility it's an IP Conflict? How big of a network, number of other PC's etc.? Do you static everything? You didn't say if you have DHCP enabled? Any other clients not communicating with the Domain?

by jason.helm

workstations are running dhcp from our router, and they server ips are not included with the DHCP scope. Server IPs ( it has 2) are static and dns points back to itself. None of my workstations can join the domain, have about 35

Thank you for the prompt reply.

by shasca

What type error at the workstations when attempting to join?

Any possibility the DNS has an IP conflict? The error says "unreachable".

This would cause the workstations to fail joining, as they would not be able to find the comain controller through DNS.

by pshiflet-24

The router that is running DHCP: is it issuing your internal DNS servers to clients or the ISP DNS servers?

by jason.helm

Error i am getting is this, AFTER it prompts me for the user name/password authorized to add computers to the domain:
The following error occurred while attempting to join the domain "lighthouse":
The specified domain either does not exist or could not be contacted

by shasca

Do you have any other DNS issues? can you browse the internet etc.?

You did say you checked the DNS entry for the DC?

by jason.helm

No other DNS issues that I know of. all machines can browse the internet just fine. I checked the DNS entry, and looks fine to me. though i will admit that i am not a DNS expert at all. Kinda teaching my self as i go along. What information would you need to see to know if i have it set properly or missing something?

by jason.helm

Router is providing the internal DNS server address, which is running on the same server as the Domain.

Good to hear from you sir, I was wondering if you would have any thoughts on this! Thank you!

by pshiflet-24

Ya, I haven't been around much. As for your issue, check CG IT's response below. I think it will point you in the right direction.

by cg it

This is your problem.

lighthouse.local
could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc

you need to go into your DNS MMC and test your DNS server with simple query and recursive query tests for your domain lighthouse.local

Also check that DNS service is actually running and that your SOA records reflect the correct domain and A records. Verify that your DC server A record has the the same IP address as the DC server NIC address [static address]and that they are all on the same subnet [IP address and subnet mask].

Can not resolve the domain name typically means that the workstation DNS server address isn't the correct one or that DNS records have a different IP address for the DC or that there is no record for it.

Example: If your DC server for the domain lighthouse.local is named Mail and has an IP address 192.168.2.1 then there should be a record in DNS that say Mail = 192.168.2.1

Workstations then would have for the first listed DNS server as 192.168.2.1.

make sure that you use the entire domain name when trying to join the workstation to the domain. if the domain name is lighthouse.local you type that in the domain box.

by jason.helm

All dns seems to be working except for adding workstations to the domain. DHCP is running from the router, DNS, Domain controller and the Exchange server are all one server. All workstations and the server can get to the internet etc as they are supposed to. I have done the query tests and they both pass fine.

by cg it

run an ipconfig/all from the command prompt then make sure DNS 1 is your DNS/DC. DNS 2 can be the ISP DNS server should DNS 1 is unavailable [your DNS/DC].

When you type in the domain name lighthouse.local and DNS says it can not resolve the name then DNS doesn't have a record for it. If your DNS server does have a record for lighthouse.local, then clients aren't quering it or it would resolve.

I'll bet that if you have a consumer level router running or even a SMB router handing out addresses, that it's giving clients your ISP DNS server which wouldn't be able to answer the query.

note: DNS servers are processed in the order listed so that queries for lighthouse.local would be sent to the first listed DNS server. If that server can not resolve the name, then what happens is that server sends the query to root hint servers [forwarders] out the default gateway.

Should DNS 1 be unavailable, then and only then is DNS 2 used.

by jason.helm

so are you saying that at the start of authority, the primary server needs to be msdcs.lighthouse.local?

by cg it

Here's what you wrote in a previous post.

Re: mail....
i am using 'lighthouse' as the domain to join and that is when i get prompted for username/password. if i use lighthouse.local i get "An Active Directory Domain Controller for the domain lighthouse.local could not be contacted. Ensure that the domain name is typed correctly"
I did check yesterday for previous computer name and did find one and removed it. I am checking the reverse lookup zone now, i did not include that in the screen i posted a few minutes ago.

Thank you all again for the help!

so, you can join the domain ff you use lighthouse because you get prompted for user name and credentials. but if you use the .local extension you can't?

by netman1958

It looks like your forward lookup zone is .com and not .local although the machine names show .local. Not sure how that happened. Also, under your forward looup zones you should have one named "_msdcs.lighthouse.local"
and one named "lighthouse.local"

I don't even see the one that starts with "_msdcs". I would delete all the zones and start over. Be sure to create a forward zone for lighthouse.local not lighthouse.com.

If you have enabled PM's, I can send you a screen shot of what a proper config looks like.

by jason.helm

yes lighthouse.local is listed there, and yes mail is listed as the only domain controller.

At this point i am happy to humor anyone, just would love to avoid wiping out all of dns and putting it back. if possible of course

by jason.helm

and yes it is listed under active directory domains and trusts.

by jason.helm

I understand on the SBS but had to go with what had already been paid for on that ground

As for the email domain, the domain name is actually hosted externally, but when learning/building the email server, Microsoft were the ones who assisted in setting that part up. Hope that in getting to the resolution on this doesn't end up breaking the email system.

Am i answering your questions with the information you all are looking for?

by jason.helm

ok so i am getting lost on the aliases you all are mentioning, if the lhe-tulsa.com domain is only being used by the email side, and is working properly, how is that affecting the local network domain? just want to understand this part.

by netman1958

I may be making some false assumptions so let me ask a few questions.
(1) Was this server already an Active directory controller when you took over?
(2) If it wasn't, did you run DCPROMO on it?
(3) If the answer to number 2 is yes, did you select the option to configure DNS during DCPROMO?
(4) In the TCP/IP settings for this server, does it point to it's own IP for DNS server?

by cg it

but that happens when you create user accounts. If exchange is present, AD will prompt you for creating a mail box for the user. I assume that current users are not members of a domain and their Outlook is configured to use Exchange.

when you create the domain lighthouse.local and create user accounts, their email accounts aren't intergrated with their Active Directory user accounts. while not a big deal, lots more administrative work.

Typically Exchange is intergrated with Active Directory for a single management interface. You can manage both their AD accounts as well as their email accounts from the AD users properties page.

the way your doing it is similar to a 3rd party hosting your email. That 3rd party being tulsa.com. I was thinking distribution groups in Active Directory which if you need the distribution group to work with Exchange, you'll need an alias. But you don't have to.

by jason.helm

ok you are getting the tulsa.com from the dns entry of lhe-tulsa.com correct?

that is the only place that that has been used. that is the domain that exchange uses for our email addresses. that domain we have purchased and paid for. am i wrong in thinking that that has to be present in the dns for the email to work? our web access to the exchange server is mail.lhe-tulsa.com/owa. I was led to believe that i needed entries in dns for this to work.

I am sorry if i am confusing the issue here. I am really greatful for all the help, I just dont want to provide the wrong information and make it more complicated...?

by jason.helm

ok i just tested what you are talking about and yes you are right, if i create a user in Active Directory Users and Computers, i have to go in and manually add the user mailbox to exchange. if you go straight to exchange and add a mailbox, it automatically adds the user to active directory users and computers.

by cg it

that are not contiguous name spaces.

I guess I didn't ask the right question way back when and that is in Active Directory Domains and Trusts is Tulsa.com present as well as lighthouse.local?

Because if Exchange is tulsa.com and you create mailboxes on Exchange for users in the domain Tulsa.com, that should not automatically create a user account in Active Directory in the domain lighthouse.local.

It's 2 seperate domains namespaces.

by jason.helm

only DNS server listed is my internal dns server. My router is a cisco 1841 so not enterprise level but not the low end of the stick either. At what record should Lighthouse.local be in DNS. I look through and see the fqdn of the server but no entry for just lighthouse.local. i have mail.lighthouse.local and the entries for my email server domain. I had the router using dsn2 as the isp dns but removed that part for testing of this. I will add that back once i get this part working. Here is ipconfig /all from my ws:

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : lighthouse.local
Description . . . . . . . . . . . : Intel(R) 82567LM Gigabit Network Connect
on
Physical Address. . . . . . . . . : 00-22-64-74-EC-0C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.2.129(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, July 08, 2009 8:52:49 AM
Lease Expires . . . . . . . . . . : Saturday, August 14, 2145 7:51:06 PM
Default Gateway . . . . . . . . . : 192.168.2.50
DHCP Server . . . . . . . . . . . : 192.168.2.50
DNS Servers . . . . . . . . . . . : 192.168.2.90
Primary WINS Server . . . . . . . : 192.168.2.90
NetBIOS over Tcpip. . . . . . . . : Enabled

by cg it

the FQDN mail.lighthouse.local is a child domain of the domain lighthouse.local. so are you trying to join the workstations to the child domain? or the top level domain?

if you don't have a record for lighthouse.local then DNS can't resolve it to an address. If you put in mail.lighthouse.local for the domain you wish to join and DNS has a record for it, it will then resolve the query to the server that handles the domain mail.lighthouse.local.

If you want to join the domain lighthouse.local, then DNS needs to have a record for the DC that handles the domain lighthouse.local. What DC handles the domain lighthouse.local?

by pshiflet-24

I believe that the DC's name is actually MAIL. So, in his DNS reverse lookup zones he should see the IP address with a PTR record pointing to mail.lighthouse.local. Under the forward lookup zones there needs to be an A record for "mail" that points to the IP address of the DC, as well. Please correct me if I am wrong.

Also, when you attempt to join the domain, are you typing in "lighthouse" or "lighthouse.local" when prompted for the domain to join? And is there, by chance, an old computer account in Active Directory with the same name as the computer you are trying to add? Please let me know.

by jason.helm

ok Im sorry if i am causing frustration and just not getting it. I really appreciate everyones help. here is a screen of the dns settings i think you are talking about.

Photobucket

if that doesn't work here is a direct link:
http://i171.photobucket.com/albums/u314/jhelm25/dns.jpg

that fqdn is what shows as the Full computer name. with a domain name of lighthouse.local

by shasca

I relearning some troubleshooting steps right along with you. Been so long since we set everything up around here I can't believe all that I have forgotten. Glad CG, ans CS joined in as I'm not sure I would have been as helpful as they have turned out to be. Much fresher minds too I suspect.

by shasca

Did you intentionally set the lease rate 130 years

by cg it

msdcs.lighthouse.local

his domains under msdcs should be a unique identifier # XXXXXXX.domains._msdcs.lighthouse.local with the host mail.lighthouse.local [where mail means the server hosting the service]

in gc he should have an A record indicating Host with his server address 192.168.X.90

by jason.helm

i am using 'lighthouse' as the domain to join and that is when i get prompted for username/password. if i use lighthouse.local i get "An Active Directory Domain Controller for the domain lighthouse.local could not be contacted. Ensure that the domain name is typed correctly"
I did check yesterday for previous computer name and did find one and removed it. I am checking the reverse lookup zone now, i did not include that in the screen i posted a few minutes ago.

Thank you all again for the help!

by cg it

if he has a record for mail.lighthouse.local and the server hosing the domain [ a DC] is named mail then workstations should be able to authenticate to the domain controller [named mail] and join the domain.

by cg it

One for Tulsa and one for lighthouse so I have to ask just what are you trying to do?

You have a domain named Tulsa is that just a domain for email? or what is it?

and what is lighthouse for?

It's possible your just missing records which are easily recreated.

Tell us what you did when you created lighthouse.local domain? is it a new forest new domain?

blah blah

by jason.helm

walked int o a company with this server already built. this is the only server we are running off of aside from 2 dedicated file servers that hold various databases. I was tasked with creating a domain controller out of this server and hosting the email server on it as well. the domain of lhe-tulsa.com is our external email domain. and the lighthouse was supposed to be the internal network domain name we used. At one point i was able to add workstation to the domain, now i cannot. i am starting to feel pretty stupid on this as it seems that i am just not grasping the concept properly.

by jason.helm

i put in lighthouse, it prompts for the username/password which i enter, the then get the response of "The following error occurred while attempting to join the domain "lighthouse":
The specified domain either does not exist or could not be contacted "

by jason.helm

well i do appreciate your efforts as well, glad you were able to relearn some stuff.

by cg it

open up Active Directory users and computer mmc by going to start programs administrative tools active directory users and computer.

with the MMC open, you should see in the left pane saved queries and then the domain. it should say lighthouse.local. if it does expand lighthouse.local in the left pane, then click on domain controllers. in the right pane you should see what server hosts the domain lighthouse.local. it should be a server named mail.

by netman1958

Jason,
(1) Microsoft doesn't recommend running Exchange on a domain controller unless you are running the Small Business Server version of Windows.
(2) They also don't recommend hosting your external DNS(i.e. your .com domain) on the same server as your Active Directory domain. The best method is what is called "split-brain" DNS where you would host lighthouse.local on the ADC server and
lhe-tulsa.com on a different DNS server - you can usually get your ISP to host this for you.

by cg it

lighthousel.local should also be listed.

by cg it

the server named mail is the domain controller for lighthouse.local domain.

DNS should have a forward lookup zone for the domain lighthouse.local just as netman showed you in his screen shot [haven't seen it but I'll assume its good].

However, one thing troubles me, I was from your photobucket screen shot the server mail had to IP addresses. one 192.168.2.90 and 192.168.2.51

why is that?

by jason.helm

primarily for a redundant path to the server. the .90 address started out as a the connection used for RDC. The exchange server is bound to the .51 address so clients are using that one only.
As for the forward lookup zone for lighthouse.local, what needs to be below it? I can create that with no problem, does it need the same entries as the zones that are already there? same SOA, Name server and A records?

by cg it

redundant path?

ok so recap here.... you've got only 1 server there that hosts DNS, Exchange email and Active Directory Services.

That 1 server's DNS service hosts 2 DNS zones. 1 for Tulsa and 1 for Lighthouse.

What is Exchange? Tulsa? or lighthouse? if it's Tulsa then lighthouse isn't a good domain for you to use.... you should have stuck with tulsa.local for the domain.

But that later...

That server has 2 network cards? bad idea.

you don't want redundant paths which in reality ends up being loops and also confusing hosts. do they go to the interface 192.168.2.51? or do they go to interface 192.168.2.90? which interface accepts host traffic?

by netman1958

Here is an excerpt from your first post:
The host d7656a0c-ec8f-431b-a213-0d7659a7521d._msdcs.lighthouse.local c
ould not be resolved to an
IP address. Check the DNS server, DHCP, server name

You are getting that error because you don't even have the "_msdcs.lighthouse.local" section under your forward lookup zones. AD is never going to work until you correct this. It doesn't take much time or effort to re-create your DNS config.

by cg it

however, he hosts mail under the tulsa domain as well so that zone in DNS can't be deleted.

I'm wondering how he is going to do all this with only 1 main server?

by jason.helm

Sounds like i may not be able to. Please understand gentlemen, i appreciate all of this help. I am just trying to learn as much as i can and get this all done correctly. If i do have to recreate it all then I will.

by netman1958

I've only run Exchange on an ADC with Small Business Server. Also, I always use AD integrated zones. The strange thing is, that if he chose the option to configure DNS during DCPROMO, and entered lighthouse.local for the domain name, all of this should be correctly configured. Not sure how he arrived where he is. He might end up re-running DCPROMO to demote it and then start over again and get it right.

by jason.helm

again, creating this zone, it will need to have all the same information in it as well? If i am beginning to understand correctly, when all said and done, i need to have 3 entries in my forward lookup zones:
_msdcs.lighthouse.local
lighthouse.local
lhe-tulsa.com (for the email side)

Am I starting to find the correct path?

by cg it

your going to have to create aliases for email and then not sure that's going to work ok. Mail will be seen as originating from lighthouse.local but with an alias of Tulsa.com.

Don't manually create individual records.

run through the wizard which will populate DNS with the right records. All you do is imput the domain name and server address

and see other post about redundant links. Not good idea.

by netman1958

via email with my "_msdcs.domain.local" zone completely expanded so you can see just how complex that zone is. I don't think you want to try to create it manually.

by jason.helm

Exchange is the lhe-tulsa domain yes.
And yes server has 2 cards. Exchange traffic is coming to the .51 connection and DNS traffic is set to the .90 connection.

by cg it

since email on Exchange is with the Tulsa.com domain name, his AD domain should be Tulsa.local.... not lighthouse....Requires and alias and it's just not going to work well.

by jason.helm

1 - yes it had already been setup as a controller when i got to it.

2 - No see above

3-

4 - yes it does point to itself for dns

by netman1958

You may not know the answer to this one but if it was already an ADC, why weren't any of the workstations joined to the domain already?

Any way, I have an idea. Run "netdiag /fix" the run "ipconfig /registerdns" then restart the netlogon service.

See if that adds the missing info to your DNS config.

by jason.helm

basically old IT person built server and then left company, so it sat shelved and unused for a while. I came in and was given a very fast time table to get it operational and get the email system working. basically the domain stuff wasn't important at the time. I am running those commands now.

by jason.helm

Saw alot of things fail, and after the second command and the netlogon restart it still didnt add in the entries. here is the output from the first command:

C:\Documents and Settings\jason.LIGHTHOUSE>netdiag /fix

..........................................

Computer Name: MAIL
DNS Host Name: Mail.lighthouse.local
System info : Microsoft Windows Server 2003 (Build 3790)
Processor : EM64T Family 6 Model 23 Stepping 6, GenuineIntel
List of installed hotfixes :
Q147222

Netcard queries test . . . . . . . : Passed

Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : Mail.lighthouse.local
IP Address . . . . . . . . : 192.168.2.51
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.2.50
Primary WINS Server. . . . : 192.168.2.90
Dns Servers. . . . . . . . : 192.168.2.90

AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
No names have been found.

WINS service test. . . . . : Passed

Adapter : Local Area Connection 2

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : Mail.lighthouse.local
IP Address . . . . . . . . : 192.168.2.90
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.2.50
Primary WINS Server. . . . : 192.168.2.90
Dns Servers. . . . . . . . : 192.168.2.90

AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
No names have been found.

WINS service test. . . . . : Passed

Global results:

Domain membership test . . . . . . : Passed

NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{7549B657-765F-4150-AB7E-6FD3765ECE17}
NetBT_Tcpip_{8F9971AC-383C-4CA8-A5C2-F3BFF58922A9}
2 NetBt transports currently configured.

Autonet address test . . . . . . . : Passed

IP loopback ping test. . . . . . . : Passed

Default gateway test . . . . . . . : Passed

NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.

Winsock test . . . . . . . . . . . : Passed

DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for the name
'Mail.lighthouse.local.'. [RCODE_SERVER_FAILURE]
The name 'Mail.lighthouse.local.' may not be registered in DNS.
[WARNING] Cannot find a primary authoritative DNS server for the name
'Mail.lighthouse.local.'. [RCODE_SERVER_FAILURE]
The name 'Mail.lighthouse.local.' may not be registered in DNS.
[FATAL] Could not open file C:\WINDOWS\system32\config\netlogon.dns for read
ing.
[FATAL] No DNS servers have the DNS records for this DC registered.

Redir and Browser test . . . . . . : Failed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{7549B657-765F-4150-AB7E-6FD3765ECE17}
NetBT_Tcpip_{8F9971AC-383C-4CA8-A5C2-F3BFF58922A9}
The redir is bound to 2 NetBt transports.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{7549B657-765F-4150-AB7E-6FD3765ECE17}
NetBT_Tcpip_{8F9971AC-383C-4CA8-A5C2-F3BFF58922A9}
The browser is bound to 2 NetBt transports.
[FATAL] Cannot send mailslot message to 'LIGHTHOUSE*' via browser. [ERROR_IN
VALID_FUNCTION]

DC discovery test. . . . . . . . . : Passed

DC list test . . . . . . . . . . . : Passed

Trust relationship test. . . . . . : Skipped

Kerberos test. . . . . . . . . . . : Failed
[FATAL] Cannot lookup package Kerberos.
The error occurred was: (null)

LDAP test. . . . . . . . . . . . . : Passed

Bindings test. . . . . . . . . . . : Passed

WAN configuration test . . . . . . : Skipped
No active remote access connections.

Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information

The command completed successfully

by jason.helm

when i add mailboxes, it automatically adds to the active directory. So basically, if i goto my exchange console and create a mailbox for CG.IT@lhe-tulsa.com, it will create a user in active directory with domain user rights with the name of CG and whatever password i assign it.

by cg it

when you use Active Directory Users and Computer MMC and create a new user account, AD users and computers will also create an Exchange mailbox in Exchange.

the way your doing it, you have to create a mail box on Exchange for the user.

Their Active Directory user account isn't intergrated with the Exchange account. They are in 2 Different domains. So you create a mailbox in Exchange and have to have a user account as well [which is NOT their domain user account]. So an alias is nothing more than lighthouse.local is also is known as tulsa.com [a.k.a.]

by jason.helm

I understand what you are saying. I have not tried adding accounts through the Active directory users and computers MMC. but all the mailboxes that i have created under exchange, HAVE been created in Active directory users and computers MMC. And i can use them to login to the server directly.

by cg it

we are talking about 2 different domains here. Tulsa.com and lighthouse.local.

the domains are not contiguous namespaces.

Ok not much of all this makes sense to me.

by netman1958

In ADUC, does it have the Exchange tabs for each user in addition to the usual tabs?

by jason.helm

as in under properties of a specific user? no there is no exchange tab

by netman1958

For each user, in addition to the tabs you would have if no Exchange server existed in your domain, you should also have the following tabs:
Exchange General
Exchange Advanced
Exchange Features
E-mail Addresses

Did you run the Exchange installation yourself or had that already been done?

by jason.helm

No tulsa.com is NOT in there.

And i just did something to break a portion of it and i dont know what i did. It has to do with that part of the dns for LHE-tulsa.com, because thats the only place i was in but now the mail.lhe-tulsa.com doesnt resolve any more

by netman1958

Which version of Exchange are you using? For instance is it Exchange version 5.5, or Exchange 2000 or Exchange 2003 or 2007?

I think at the very least, you are going to have to delete every zone in DNS and re-create them with the proper names. Worst case, you may have to run DCPROMO and demote the server and then re-run it. If it get's to that point, I would rename the local domain to lhe-tulsa.local as CG IT has suggested. Doing that, may require re-installing Exchange, I'm not sure.

Let us know how you wish to proceed.

by cg it

is not going to break anything. Neither is going in and looking at DNS records. running queries against DNS and even netdiag/fix or dcdiag.

I think that the simplest solution would be to use the add new forware lookup zone wizard which will create a new forward lookup zone for the domain lighthouse.local.

Use the wizard by opening up DNS from admin tools on the server hosting the DNS service and is also the DC for lighthouse.local. Right click on the server name and choose new zone.

While this doesn't fix some fundamental problems such as having Exchange server in a different domain than users, it should allow you to join workstations to the domain lighthouse.local.

I would caution you though that user profiles will change once you join the workstations to the domain and users log in to the domain the first time. Further, because the profiles change, Outlook configuration will change. you can migrate profiles over using the corrupt profile to new profile method, but I strongly, strongly caution that users backup everything associated with their outlook account to pst files. This includes contacts, calendars, etc. I wouldn't do it unless users backed up everything and they knew that if they didn't there is a good chance they will lose it.

I wish to stress that these are suggestions of course of action to take to fix your DNS problems. The errors you receive all point to records not exisitng on your DNS server for the zone lighthousel.local While your screen shot show there are records there fore it.

I also highly recommend that you check your interfaces where DNS listens for DNS queries on the DNS server property page/interfaces. If the right interface is not listed, change it to the correct one and then try joining a workstation to the domain.

Also before you make any drastic changes you backup your server. backups are standard ops before changes as well as documenting any changes.

Again

by jason.helm

thank you for all the help today. I need to run on home now i will read over all of this along with some other literature that i have and decide what to do in the morning. agaon thank you all again.

by jason.helm

Sorry for the long delay is responding again and Thank you guys VERY VERY much for the assistance. The route i chose to take was to follow through the wizard and create the 2 zones: lighthouse.local and _msdcs.lighthouse.local. Once these were in place again i was able to go in and add my workstation to the active directory domain. This of course did not fix the issues you all brought to light with exchange tabs not being there for domain users etc but hopefully over time i will be able to find a point where i can reinstall exchange properly and get all that back where it should be and also fix the domain issues with the 2 domains as you pointed out. Thank you all again for the extensive assistance you have provided!

by shasca

I learned alot too. I didn't know how much I didn't know.

This discussion is closed to new replies.