Re: W2K3 Trust Issues

Tech-Archive recommends: Fix windows errors by optimizing your registry



I don't have an answer for you. I'm stumped

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

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


"Big Daddy" <caddo65590@xxxxxxxxxxx> wrote in message
news:OSTSzQApFHA.3960@xxxxxxxxxxxxxxxxxxxxxxx
> Yes, they are all point to the same WINS server.
> Why is it that the XP boxes have no problems and the W2K pro boxes have?
> It just does not make sense.
> Help
> "Paul Bergson" <pbergson@xxxxxxxxxxxxxxxxx> wrote in message
> news:uBeoue3oFHA.2580@xxxxxxxxxxxxxxxxxxxxxxx
>> Alright how about WINS. NetBIOS names use WINS names not DNS. Do you
> have
>> a WINS Server defined that can refer to the machine in the w2k3 domain?
>>
>> --
>>
>>
>> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
>>
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>>
>> "Big Daddy" <caddo65590@xxxxxxxxxxx> wrote in message
>> news:ex2qk$yoFHA.708@xxxxxxxxxxxxxxxxxxxxxxx
>> > Hi Paul, I did the nslookup on both pc's and they are the same yet the
> w2k
>> > pro clients are still having issues in mapping drives with netbios
>> > names
>> > while the XP pro clients have no problems at all.
>> > The time sync is exactly the same on all the pc's but what I did not
>> > understand is the dupe name issue you mentioned.
>> > This pc's are pc's that have not been migrated yet but are trying to
>> > connect
>> > to shares on servers that have already been migrated.
>> > This same users are also unable to connect to their home drives on
> servers
>> > that have been migrated to the w2k3 domain with the users still in the
> w2k
>> > domain.
>> > Need help.
>> > thanks
>> > "Paul Bergson" <pbergson@xxxxxxxxxxxxxxxxx> wrote in message
>> > news:eCx8htpoFHA.2080@xxxxxxxxxxxxxxxxxxxxxxx
>> >> Recheck the dns setup and make sure the w2k setup is the same as the
> xp.
>> > Do
>> >> an nslookup on a machine that is able to connect and note the ip
> address.
>> >> Do another nslookup on a failing machine and again note the ip address
> to
>> >> see if the address is the same.
>> >>
>> >> How about time sync is that correct? Could you have a dupe name issue
>> >> between the two domains?
>> >>
>> >> --
>> >>
>> >>
>> >> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >>
>> >>
>> >> "Big Daddy" <caddo65590@xxxxxxxxxxx> wrote in message
>> >> news:ewckNnmoFHA.2904@xxxxxxxxxxxxxxxxxxxxxxx
>> >> > The error is "Logon Failure: The target account name is incorrect".
>> >> > The clients are w2k pro and XP pro clients.
>> >> > I realise that the w2k pro clients are the only ones having the
>> >> > problem.
>> >> > They are all pointing to the same dns servers.
>> >> >
>> >> > "Paul Bergson" <pbergson@xxxxxxxxxx> wrote in message
>> >> > news:%23uK73mloFHA.572@xxxxxxxxxxxxxxxxxxxxxxx
>> >> >> Resolving names simply involves dns lookup so there isn't much of a
>> >> >> big
>> >> > deal
>> >> >> there. What kind if erors? What are the clients? If they are
> win98
>> > and
>> >> >> the w2k3 domain is in w2k3 native mode then the nodes will have
>> > trouble.
>> >> >>
>> >> >> Post the errors and the clients.
>> >> >>
>> >> >> --
>> >> >>
>> >> >>
>> >> >> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
>> >> >>
>> >> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> > rights.
>> >> >>
>> >> >>
>> >> >> "Big Daddy" <caddo65590@xxxxxxxxxxx> wrote in message
>> >> >> news:%23$4Re7boFHA.1088@xxxxxxxxxxxxxxxxxxxxxxx
>> >> >> > I am currently migrating from w2k to w2k3 domain. Both domains
> have
>> >> > trust
>> >> >> > configured. I have migrated about half of my users and servers to
>> >> >> > the
>> >> > w2k3
>> >> >> > domain.
>> >> >> > The users still on the w2k domain are getting authentication
> errors
>> >> >> > when
>> >> >> > connecting to shares on the servers currently in the w2k3 domain
>> >> >> > even
>> >> >> though
>> >> >> > they can resolve the server names.
>> >> >> > Any ideas?
>> >> >> > Thanks
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>


.



Relevant Pages

  • Re: active directory unavaliable after upgrade and plenty more
    ... >> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA ... since then we introduced another mailserver with 2003 server ... >>> not, stop all the Microsoft Exchange services, add the local computer ...
    (microsoft.public.windows.server.active_directory)
  • Re: Domain computers not visible on network
    ... Bring up a WINS server and point all ... >>> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA ... >>> rights. ...
    (microsoft.public.windows.server.active_directory)
  • Re: 2003 AD design for county government/public safety
    ... >> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA ...
    (microsoft.public.windows.server.active_directory)
  • Re: network service account?
    ... This posting is provided "AS IS" with no warranties, and confers no rights. ... > not tried it with the local server name preceding it, ... >> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA ...
    (microsoft.public.win2000.active_directory)
  • Re: AD not openening from local server
    ... >I did your command on the server and the server is itself. ... >> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA ...
    (microsoft.public.win2000.active_directory)