Lost Credentials...

OK, My Exchange server (Server2003) died. It was running DNS, but not the
only server. I rebuilt the box, with a little handholdeing from PSS... and
now my local machines are having problems finding my servers. I was logged
in as an admin, tried to access a directory on my GC controller, and it
wouldn't let me. It gave me a login dialog box?!? When I put in the info I
got a message (without an error code) saying I was already logged in as that
user, try again . I checked the share, and I (as that user) have full
controll of the directory and share.

Also, occasionally when I use Outlook to go into Exchange it is making me
give credentials

My thoughts... I need to install DNS on my Exchange Server and have it
replicate with the GC.
I also remember something about flushing the DNS,
Scavenging Wins (it may have some old entries we missed)

Is there anything else I need to do?
Can you give me the steps I need to do to do the above (I have support tools
loaded...

I do have an incident that I can go back and reference if it is really
complicated, but I would like to get this fixed without the call to Active
Directory...

Thanks,
In Advance,
David Bock

Hi David,

I would like to confirm my understanding with you that the clients cannot
access the shares on the Domain controller. If I am off base, please let me
know.

Based on my experience, troubleshooting this issue could be time-consuming.
If this is an urgent issue in your network, you may consider contacting
Microsoft phone support engineer by using your incident to resolve this
issue in a timely manner.

In order to isolate this issue, I have a couple of questions regarding to
this issue:

1. How many Domain Controllers are in the network? How many GCs are in the
network?

2. Is there any DNS server installed and where is the DNS server installed,
such as on DC?

3. Where was the original Exchange server installed, on a DC or a member
server? Has the original Exchange server ever held the FSMO role? Before
you rebuild the Exchange server, have you run Dcpromo to demote the server?

4. Do you encounter some problems when logon to the domain? Can you
successfully ping though the DC?


If there is no DNS server in the network, please use the following steps to
check the status:

Step 1: Install DNS
===================
Install AD-integrated DNS on the DC:
1. Go to Control Panel->Add/Remove Programs->Add/Remove Windows components
2. Select Network service->Hit Details button to choose Domain Name System
3. Follow the wizard to install DNS and choose AD-integrated.

With regards to flush the DNS, do you mean "ipconfig /flushdns" command?
This command is used to flush client's DNS cache, you can issue the command
on the client without installing the resource kits or support tools.


Step 2:
============
Is the error you have encountered described in the following article?
According to the following article, I suggest you disconnect all
connections on the shares by using the following steps:
1. On the DC which holds the network share you want to access, right click
My computer to choose Manager
2. Extend Share folders and click Shares, you can see how many connections
on this share.
3. Right click the share and choose Stop Sharing will disconnect all shares.
4. Try to access the share again by using UNC, such as \\192.168.0.1
instead of the computer name, if you are promoted to input the credentials,
please input the credential like this "domain\username" and the password,
this issue re-occur?

Err Msg: The Credentials Supplied Conflict with an Existing...
http://support.microsoft.com/?kbid=106211

Step 3: Net Use
============
Please map drive to network share, establish proper credentials on either
the server or the client -- i.e., create accounts with usernames and
passwords that match on both ends. Can you successfully map the drive?


Another method is to use the NET USE command to map the connection by using
the IP address of the remote machine rather than its NetBIOS name. For
example:

NET USE <drivename> \\xx.xx.xx.xx\share <password>
/user:<remote_machine>\<username>

where <drivename> is the drive letter to be mapped, \\xx.xx.xx.xx\share is
the IP address and share name, <password> the password for the alternate
credentials, and <remote_machine> and <username> the name of the remote
machine and the user account on that machine to log in as.

The following third party link has addressed this issue:

http://searchwinsystems.techtarget.c...040172,00.html

This response contains a reference to a third party World Wide Web site.
Microsoft can make no representation concerning the content of these sites.
Microsoft is providing this information only as a convenience to you: this
is to inform you that Microsoft has not tested any software or information
found on these sites and therefore cannot make any representations
regarding the quality, safety, or suitability of any software or
information found there. There are inherent dangers in the use of any
software found on the Internet, and Microsoft cautions you to make sure
that you completely understand the risk before retrieving any software on
the Internet.

With regards to the outlook access Exchange server, I suggest you post all
exchange related question to microsoft.public.exchange.general newsgroup
since the Exchange expert will provide the accurate information on it.

Thank you for your understanding.

Any update, let's get in touch!

Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA


Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

================================================== ===

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Thank you, I installed DNS on the other server last night. I Scavenged the
WINS, and waited for the DNS to replicate the Forward Zones.
This appeared to work. I will, however flush the DNS...

Thanks for the help...
David Bock
""Rebecca Chen [MSFT]"" <v-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi David,
>
> I would like to confirm my understanding with you that the clients cannot
> access the shares on the Domain controller. If I am off base, please let
me
> know.
>
> Based on my experience, troubleshooting this issue could be
time-consuming.
> If this is an urgent issue in your network, you may consider contacting
> Microsoft phone support engineer by using your incident to resolve this
> issue in a timely manner.
>
> In order to isolate this issue, I have a couple of questions regarding to
> this issue:
>
> 1. How many Domain Controllers are in the network? How many GCs are in the
> network?
>
> 2. Is there any DNS server installed and where is the DNS server
installed,
> such as on DC?
>
> 3. Where was the original Exchange server installed, on a DC or a member
> server? Has the original Exchange server ever held the FSMO role? Before
> you rebuild the Exchange server, have you run Dcpromo to demote the
server?
>
> 4. Do you encounter some problems when logon to the domain? Can you
> successfully ping though the DC?
>
>
> If there is no DNS server in the network, please use the following steps
to
> check the status:
>
> Step 1: Install DNS
> ===================
> Install AD-integrated DNS on the DC:
> 1. Go to Control Panel->Add/Remove Programs->Add/Remove Windows components
> 2. Select Network service->Hit Details button to choose Domain Name System
> 3. Follow the wizard to install DNS and choose AD-integrated.
>
> With regards to flush the DNS, do you mean "ipconfig /flushdns" command?
> This command is used to flush client's DNS cache, you can issue the
command
> on the client without installing the resource kits or support tools.
>
>
> Step 2:
> ============
> Is the error you have encountered described in the following article?
> According to the following article, I suggest you disconnect all
> connections on the shares by using the following steps:
> 1. On the DC which holds the network share you want to access, right click
> My computer to choose Manager
> 2. Extend Share folders and click Shares, you can see how many connections
> on this share.
> 3. Right click the share and choose Stop Sharing will disconnect all
shares.
> 4. Try to access the share again by using UNC, such as \\192.168.0.1
> instead of the computer name, if you are promoted to input the
credentials,
> please input the credential like this "domain\username" and the password,
> this issue re-occur?
>
> Err Msg: The Credentials Supplied Conflict with an Existing...
> http://support.microsoft.com/?kbid=106211
>
> Step 3: Net Use
> ============
> Please map drive to network share, establish proper credentials on either
> the server or the client -- i.e., create accounts with usernames and
> passwords that match on both ends. Can you successfully map the drive?
>
>
> Another method is to use the NET USE command to map the connection by
using
> the IP address of the remote machine rather than its NetBIOS name. For
> example:
>
> NET USE <drivename> \\xx.xx.xx.xx\share <password>
> /user:<remote_machine>\<username>
>
> where <drivename> is the drive letter to be mapped, \\xx.xx.xx.xx\share is
> the IP address and share name, <password> the password for the alternate
> credentials, and <remote_machine> and <username> the name of the remote
> machine and the user account on that machine to log in as.
>
> The following third party link has addressed this issue:
>
>
http://searchwinsystems.techtarget.c...040172,00.html
>
> This response contains a reference to a third party World Wide Web site.
> Microsoft can make no representation concerning the content of these
sites.
> Microsoft is providing this information only as a convenience to you: this
> is to inform you that Microsoft has not tested any software or information
> found on these sites and therefore cannot make any representations
> regarding the quality, safety, or suitability of any software or
> information found there. There are inherent dangers in the use of any
> software found on the Internet, and Microsoft cautions you to make sure
> that you completely understand the risk before retrieving any software on
> the Internet.
>
> With regards to the outlook access Exchange server, I suggest you post all
> exchange related question to microsoft.public.exchange.general newsgroup
> since the Exchange expert will provide the accurate information on it.
>
> Thank you for your understanding.
>
> Any update, let's get in touch!
>
> Best regards,
>
> Rebecca Chen
>
> MCSE2000 MCDBA CCNA
>
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> ================================================== ===
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>

Hi David,

Thanks for the update!

I am glad to hear installing DNS has cured the problem. I believe the
Exchange/client has not pointed to the correct DNS server, for example, the
Exchange server has pointed itself to as a DNS server without the DNS
installed.

If there is anything we can help, please feel free to post back.

Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA


Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

================================================== ===

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.