XP problem joining 2k domain RPC not available

[Elton Seng Yan Thung]

Dear all,
We have problem here that our windows XP professional PC(new
purchased)have problem joining 2k domain. The error message is RPC server
not available. Some time we have to join twice (reboot) before we can make
it successful. Some machine just can't join in until today. W2k
professional machine doesn't have any problem.
Some of the users here login to different domain (merging from other
company that login to NT4). We are tring to join all the machine to our new
2k domain while users still login to old domain ( both domain are trusted).
We have tested joining those XP PC to 2k domain, which few time of attempt
managed to join in, ask user to login and works fine. However after 2nd day,
they claimed that they are not able to login to their own domain, and the
error message is Domain not available.
I wish to get help from you.

thanks

 

[Cary Shultz [A.D. MVP]]

Elton,

Let's look at DNS! For the problem client, how is it receiving its IP
information: statically set or via DHCP? If via DHCP, is DHCP also giving it
the internal DNS Server's IP Address?

Can you run an ipconfig /all on the problem client and post the results?

HTH,

Cary

 

[Elton Seng Yan Thung]

Thanks Cary! I will do that once I return to office! By the way they we use
everything Static IP here and DCs also our DNSs.
thanks

 

[Cary Shultz [A.D. MVP]]

Elton,

Static will work. I do not know how many machines you have to manage. I
might suggest that if possible you consider running DHCP. If you do not
want to run this on a WIN2000 Server then consider your FireWall. My boss
is a big fan of running DHCP on the SonicWall Firewalls.

You can configure DHCP to give the client workstations all of the necessary
information, such as Domain Name, DNS Server IP Address, WINS info ( if
applicable ), etc.

Also, make sure that no other machine has the same IP Address.

Glad to help,

Cary

 

[Elton Seng Yan Thung]

Dear Cary,
I have suggested DHCP to my boss many time but he just don't get it. Do
you think it problem related to the IP configuration? More information
needed from you. If the problem is DNS, what kind of problem it should be?
Which how should I troubleshoot?
thanks
thanks

 

[Cary Shultz [A.D. MVP]]

Elton,

Too bad that the boss does not get it. Maybe he/she has something in mind
that has not yet come to pass ( can not imagine what that would be ) or
maybe he/she has some bad information or who knows....;-)

run an ipconfig /all at the command prompt. This will verify that you have
all the information correctly entered ( one of the pitfalls of not using
DHCP - human error is more apt to happen ). Also, the DNS Server
information must be that of your internal DNS Server(s) - NOT of your ISPs.

If that turns out okay take a look at nslookup. Simply enter nslookup
yourdomain.com. What does that tell us?

HTH,

Cary