Slow logon and browsing from XP to a win2000 domain usually indicate a DNS misconfiguration issue. While the following is not a fix-all for all AD-domain problems, it is an absolute requirement that DNS is set up correctly before it will work properly. If your DNS is not set up like this, then you will experience problems like you describe. XP differs from previous versions of windows in that it uses DNS as it's primary name resolution method for finding domain controllers:
How Domain Controllers Are Located in Windows XP
If DNS is misconfigured, XP will spend a lot of time waiting for it to timeout before it tries using legacy NT4 sytle NetBIOS. (Which may or may not work.)
1. Ensure that the XP clients are all configured to point to the local DNS server which hosts the AD domain. That will probably be the win2k server itself. They should NOT be pointing an an ISP's DNS server. An 'ipconfig /all' on the XP box should reveal ONLY the domain's DNS server. You should use the DHCP server to push out the local DNS server address.
2. Ensure DNS server on win2k is configured to permit dynamic updates. Ensure the win2k server points to itself as a DNS server.
3. For external (internet) name resolution, specify your ISP's DNS server not on the clients, but in the forwarders tab of the local win2k DNS server. On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints' tabs because they are greyed out, that is because there is a root zone ("."

present on the DNS server. You MUST delete this root zone to permit the server to forward unresolved queries to yout ISP or the root servers. Accept any nags etc, and let it delete any corresponding reverse lookuop zones if it asks.
The following articles may assist you in setting up DNS correctly:
Setting Up the Domain Name System for Active Directory
HOW TO: Configure DNS for Internet Access in Windows 2000