Re: Please Help: Windows XP Professional In Windows 2000 Domain Based network.

From: Steven L Umbach (n9rou_at_n0-spam-for-me-comcast.net)
Date: 08/12/04


Date: Thu, 12 Aug 2004 00:55:36 GMT

You mentioned that dns is correctly configured, just be sure that the XP computers do
NOT have any ISP dns servers listed as a preferred dns server even down the list as
shown by ipconfig /all on those computers. Also run netdiag on a couple of XP
computers looking for any failed tests/errors/warnings that relate to dns, dc
discovery, kerberos, or trust relationship/secure channel. If any templates have been
applied to those computers or the domain controllers, there could be a problem with
security option incompatibilities. Smb signing, as configured via security options
for digitally sign communications, can cause problems if required in a W2K domain
with XP Pro computers. Using a packet sniffer like the free Ethereal on the XP Pro
computers to capture a packet exchange sequence while trying to perform an operation
that is denied could be very helpful. --- Steve

"Adam" <adam@myhome.address> wrote in message
news:94dlh0dripvd87ke5paj5l6vibfqpe00ar@4ax.com...
> A fresh installation of Windows XP Professional (few workstations) have
> been added to our Windows 2000 domain based network.
>
> All servers and workstations have all the up to date patches and
> updates.
>
> I checked local admin group and the domain admin group is a member of
> that on the workstations as expected.
>
> DNS Servers are properly defined in both Windows 2000 and XP
> workstations,
>
>
> No errors can be seen in any event log.
> No custom or third party security packages are installed.
>
>
> Windows 2000 server hosts also DNS.
>
> Windows 2000 clients have no such problems.
>
> The problem:
> Windows XP clients, when used by members of the domain administrator
> group, cannot access folders that are assigned to domain administrators,
> access denied.
>
> Cannot read security event log or clear even logs for Application and
> System.
> Access denied.
>
> Any network or IP address discovery package running from the Windows XP
> get access denied.
>
> No such thing happens on Windows 2000 workstations.
>
> I even tried fresh user profile to separate the profile on Windows XP
> from Windows 200 profiles.
> No luck.
>
> Any suggestions?
>
> I cannot see anything in the event logs.
>
> Any pointers would be appreciated.
>
> Thank you from a confused user.
>



Relevant Pages

  • Re: Please Help: Windows XP Professional In Windows 2000 Domain Based network.
    ... You mentioned that dns is correctly configured, just be sure that the XP computers do ... NOT have any ISP dns servers listed as a preferred dns server even down the list as ... > A fresh installation of Windows XP Professional (few workstations) have ... > been added to our Windows 2000 domain based network. ...
    (microsoft.public.windowsxp.general)
  • Re: Please Help: Windows XP Professional In Windows 2000 Domain Based network.
    ... You mentioned that dns is correctly configured, just be sure that the XP computers do ... NOT have any ISP dns servers listed as a preferred dns server even down the list as ... > A fresh installation of Windows XP Professional (few workstations) have ... > been added to our Windows 2000 domain based network. ...
    (microsoft.public.win2000.networking)
  • Re: Vant see pcs in domain
    ... (server name: RM1SRV1) ... and the workstations name is. ... i was able to see the computers again. ... MCSA: Messaging on Windows 2003 ...
    (microsoft.public.cert.exam.mcse)
  • Re: Domain not reachable via DNS-name
    ... Sounds very wired that they are listed as NT4.0 Computers in the directory, ... Forest and domain are working in Windows 2003 native mode. ... all workstations are using the local DNS Server ...
    (microsoft.public.win2000.active_directory)
  • Domain name
    ... I am creating a new domain in Windows 2003. ... formed only by a word bur when I am going to do it I get a warning ... only is going to "see" the computers in the domain and it is going to use ... only the DNS servers in the domain. ...
    (microsoft.public.win2000.active_directory)