Authenticate between workgroup servers

I have 2 2003 servers that sit in my DMZ. I want to have
one of those servers be the backup server and backup the
other.

I cannot get access from server 1 to server 2. I am
prompted for authentication, I put in the admin account
and info and get rejected, or locks the account.

However, from server 2 accessing server 1, I am prompted,
put in the admin authentication info and it works.

Why? We do have complex passwords enabled on server 2 (a
requirement), so that password has upper case, lower
case, a number and a special character. Server 1 does
not, and its admin password is just lowercase letters and
numbers. Could this be any part of the problem?

Hi Dave,

are username and password same on both servers?

When accessing server 2 from server 1 when you are prompted for username
enter

server2\username

in username box.

Replace server2 with name of your remote server and enter correct username
that is created on server 2.

I hope this helps,

Mike

"Dave Clark" <(E-Mail Removed)> wrote in message
news:c3b201c47a2a$275714d0$(E-Mail Removed)...
> I have 2 2003 servers that sit in my DMZ. I want to have
> one of those servers be the backup server and backup the
> other.
>
> I cannot get access from server 1 to server 2. I am
> prompted for authentication, I put in the admin account
> and info and get rejected, or locks the account.
>
> However, from server 2 accessing server 1, I am prompted,
> put in the admin authentication info and it works.
>
> Why? We do have complex passwords enabled on server 2 (a
> requirement), so that password has upper case, lower
> case, a number and a special character. Server 1 does
> not, and its admin password is just lowercase letters and
> numbers. Could this be any part of the problem?
>

I did try it that way as a test, and it locks the account
of the same name on the destination server immediately.
>-----Original Message-----
>Hi Dave,
>
>are username and password same on both servers?
>
>When accessing server 2 from server 1 when you are
prompted for username
>enter
>
>server2\username
>
>in username box.
>
>Replace server2 with name of your remote server and
enter correct username
>that is created on server 2.
>
>I hope this helps,
>
>Mike
>
>"Dave Clark" <(E-Mail Removed)> wrote in message
>news:c3b201c47a2a$275714d0$(E-Mail Removed)...
>> I have 2 2003 servers that sit in my DMZ. I want to
have
>> one of those servers be the backup server and backup
the
>> other.
>>
>> I cannot get access from server 1 to server 2. I am
>> prompted for authentication, I put in the admin account
>> and info and get rejected, or locks the account.
>>
>> However, from server 2 accessing server 1, I am
prompted,
>> put in the admin authentication info and it works.
>>
>> Why? We do have complex passwords enabled on server 2
(a
>> requirement), so that password has upper case, lower
>> case, a number and a special character. Server 1 does
>> not, and its admin password is just lowercase letters
and
>> numbers. Could this be any part of the problem?
>>
>
>
>.
>

You're using the wrong credentials. You have to use the credentials that
match the machine asking for them, not for the machine you are comming from.
You could also just make the machines match in both name and password
although that is considered less secure.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"Dave Clark" <(E-Mail Removed)> wrote in message
news:c3b201c47a2a$275714d0$(E-Mail Removed)...
> I have 2 2003 servers that sit in my DMZ. I want to have
> one of those servers be the backup server and backup the
> other.
>
> I cannot get access from server 1 to server 2. I am
> prompted for authentication, I put in the admin account
> and info and get rejected, or locks the account.
>
> However, from server 2 accessing server 1, I am prompted,
> put in the admin authentication info and it works.
>
> Why? We do have complex passwords enabled on server 2 (a
> requirement), so that password has upper case, lower
> case, a number and a special character. Server 1 does
> not, and its admin password is just lowercase letters and
> numbers. Could this be any part of the problem?
>

Make sure you entered the right password. It has to be the password of
account created on server 2!

Mike

"Dave Clark" <(E-Mail Removed)> wrote in message
news:c43301c47a2e$c9d5e8e0$(E-Mail Removed)...
> I did try it that way as a test, and it locks the account
> of the same name on the destination server immediately.
> >-----Original Message-----
> >Hi Dave,
> >
> >are username and password same on both servers?
> >
> >When accessing server 2 from server 1 when you are
> prompted for username
> >enter
> >
> >server2\username
> >
> >in username box.
> >
> >Replace server2 with name of your remote server and
> enter correct username
> >that is created on server 2.
> >
> >I hope this helps,
> >
> >Mike
> >
> >"Dave Clark" <(E-Mail Removed)> wrote in message
> >news:c3b201c47a2a$275714d0$(E-Mail Removed)...
> >> I have 2 2003 servers that sit in my DMZ. I want to
> have
> >> one of those servers be the backup server and backup
> the
> >> other.
> >>
> >> I cannot get access from server 1 to server 2. I am
> >> prompted for authentication, I put in the admin account
> >> and info and get rejected, or locks the account.
> >>
> >> However, from server 2 accessing server 1, I am
> prompted,
> >> put in the admin authentication info and it works.
> >>
> >> Why? We do have complex passwords enabled on server 2
> (a
> >> requirement), so that password has upper case, lower
> >> case, a number and a special character. Server 1 does
> >> not, and its admin password is just lowercase letters
> and
> >> numbers. Could this be any part of the problem?
> >>
> >
> >
> >.
> >

Problem fixed. Turned out to be a NTLM level problem.
The server I was trying to access had the LAN Manager
Authentication level set to Send NTLMv2 responses
only/refuse LM and NTLM. While server making the request
was set to Send LM & NTLM responses only.

Changed it, and then I could access/authenticate properly.

Thanks for posting back the solution. It's good to know ...

:-)

Mike

"Dave Clark" <(E-Mail Removed)> wrote in message
news:c5d001c47a3c$f46f0740$(E-Mail Removed)...
> Problem fixed. Turned out to be a NTLM level problem.
> The server I was trying to access had the LAN Manager
> Authentication level set to Send NTLMv2 responses
> only/refuse LM and NTLM. While server making the request
> was set to Send LM & NTLM responses only.
>
> Changed it, and then I could access/authenticate properly.
>