2000 Server, CName records and XP Clients

I have recently replace an old file server with a new one. I couldn't simply
rename the servers for various reasons and rather than repoint all the
clients to the new server, I've used a cname record in dns pointing to the
new server. I have also done the proceedure described in Article 281308, to
allow the server to accept connections via the cname. I also removed the old
server's account from ad.

This works fine for the all of our win2k clients. For some reason however
one xp client seems not to like this returning

System error 1396 has occurred.
Logon Failure: The target account name is incorrect.

Other XP machines seem to be ok

Any thoughts?

So what is different about this one XP machine? Find that out and you have
the answer to your problem. Is it part of the domain? Does it occur with
every one logged onto it (try it with your credentials and not just the
user's).

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights


"Azriphale" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
I have recently replace an old file server with a new one. I couldn't simply
rename the servers for various reasons and rather than repoint all the
clients to the new server, I've used a cname record in dns pointing to the
new server. I have also done the proceedure described in Article 281308, to
allow the server to accept connections via the cname. I also removed the old
server's account from ad.

This works fine for the all of our win2k clients. For some reason however
one xp client seems not to like this returning

System error 1396 has occurred.
Logon Failure: The target account name is incorrect.

Other XP machines seem to be ok

Any thoughts?

Sorry, I didn't mention that the machine can connect using the proper server
name
e.g.
Server1 Cname Server2
Server2 A 192.168.1.2

The XP client can connect to \\server2\share but not \\server1\share
So permissions, etc. are obviously fine.


"Todd J Heron" <(E-Mail Removed)> wrote in message
news:OwsPFZ%(E-Mail Removed)...
> So what is different about this one XP machine? Find that out and you
have
> the answer to your problem. Is it part of the domain? Does it occur with
> every one logged onto it (try it with your credentials and not just the
> user's).
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> --------------------------------------------------------------------------
--
> This posting is provided "as is" with no warranties and confers no rights
>
>
> "Azriphale" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> I have recently replace an old file server with a new one. I couldn't
simply
> rename the servers for various reasons and rather than repoint all the
> clients to the new server, I've used a cname record in dns pointing to the
> new server. I have also done the proceedure described in Article 281308,
to
> allow the server to accept connections via the cname. I also removed the
old
> server's account from ad.
>
> This works fine for the all of our win2k clients. For some reason however
> one xp client seems not to like this returning
>
> System error 1396 has occurred.
> Logon Failure: The target account name is incorrect.
>
> Other XP machines seem to be ok
>
> Any thoughts?
>
>

After attempting to connect to the server, examine the cache on the problem
XP client versus that of a known good working one and compare.

ipconfig /displaydns

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights


"Azriphale" <(E-Mail Removed)> wrote in message
news:ehcbgp$(E-Mail Removed)...
Sorry, I didn't mention that the machine can connect using the proper server
name
e.g.
Server1 Cname Server2
Server2 A 192.168.1.2

The XP client can connect to \\server2\share but not \\server1\share
So permissions, etc. are obviously fine.


"Todd J Heron" <(E-Mail Removed)> wrote in message
news:OwsPFZ%(E-Mail Removed)...
> So what is different about this one XP machine? Find that out and you
have
> the answer to your problem. Is it part of the domain? Does it occur with
> every one logged onto it (try it with your credentials and not just the
> user's).
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> --------------------------------------------------------------------------
--
> This posting is provided "as is" with no warranties and confers no rights
>
>
> "Azriphale" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> I have recently replace an old file server with a new one. I couldn't
simply
> rename the servers for various reasons and rather than repoint all the
> clients to the new server, I've used a cname record in dns pointing to the
> new server. I have also done the proceedure described in Article 281308,
to
> allow the server to accept connections via the cname. I also removed the
old
> server's account from ad.
>
> This works fine for the all of our win2k clients. For some reason however
> one xp client seems not to like this returning
>
> System error 1396 has occurred.
> Logon Failure: The target account name is incorrect.
>
> Other XP machines seem to be ok
>
> Any thoughts?
>
>

I thought of that already, the names are resolving correctly. A ping of
server1 returns pinging server2.

"Todd J Heron" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> After attempting to connect to the server, examine the cache on the
problem
> XP client versus that of a known good working one and compare.
>
> ipconfig /displaydns
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> --------------------------------------------------------------------------
--
> This posting is provided "as is" with no warranties and confers no rights
>
>
> "Azriphale" <(E-Mail Removed)> wrote in message
> news:ehcbgp$(E-Mail Removed)...
> Sorry, I didn't mention that the machine can connect using the proper
server
> name
> e.g.
> Server1 Cname Server2
> Server2 A 192.168.1.2
>
> The XP client can connect to \\server2\share but not \\server1\share
> So permissions, etc. are obviously fine.
>
>
> "Todd J Heron" <(E-Mail Removed)> wrote in message
> news:OwsPFZ%(E-Mail Removed)...
> > So what is different about this one XP machine? Find that out and you
> have
> > the answer to your problem. Is it part of the domain? Does it occur
with
> > every one logged onto it (try it with your credentials and not just the
> > user's).
> >
> > --
> > Todd J Heron, MCSE
> > Windows Server 2003/2000/NT; CCA
>
> --------------------------------------------------------------------------
> --
> > This posting is provided "as is" with no warranties and confers no
rights
> >
> >
> > "Azriphale" <(E-Mail Removed)> wrote in message
> > news:%(E-Mail Removed)...
> > I have recently replace an old file server with a new one. I couldn't
> simply
> > rename the servers for various reasons and rather than repoint all the
> > clients to the new server, I've used a cname record in dns pointing to
the
> > new server. I have also done the proceedure described in Article 281308,
> to
> > allow the server to accept connections via the cname. I also removed the
> old
> > server's account from ad.
> >
> > This works fine for the all of our win2k clients. For some reason
however
> > one xp client seems not to like this returning
> >
> > System error 1396 has occurred.
> > Logon Failure: The target account name is incorrect.
> >
> > Other XP machines seem to be ok
> >
> > Any thoughts?
> >
> >
>
>

"Azriphale" <(E-Mail Removed)> wrote in message...
>I thought of that already, the names are resolving correctly. A ping of
>server1 returns pinging server2.

Are you running DFS on these two servers?

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

Yep. I have checked two shares though; one dfs, one stand alone share - both
work to the non cname record, neither work to the cname. The old server was
removed from the dfs replica prior to removal from the domain - I also made
sure that ad replicated in between (I've checked via 'Adsi Edit' and the ad
replica entries underboth the dfs container and the server container).


"Todd J Heron" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "Azriphale" <(E-Mail Removed)> wrote in message...
> >I thought of that already, the names are resolving correctly. A ping of
> >server1 returns pinging server2.
>
> Are you running DFS on these two servers?
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> --------------------------------------------------------------------------
--
> This posting is provided "as is" with no warranties and confers no rights
>