xp sp2 with server 2000 3

[deik313]

Hi, can anyone tell me if it is recommended to install SP2 on XP machines that are logging into a 2000 server? I have done this, but have heard now that there can be many problems due to different architectures. I'm having problems, but don't know for sure if it is because of SP2.

Is anyone else out there running XP clients with SP2 installed, logging into a 2000 SP4 server?

 

[cyberspace]

Hi there,

The company I work for has exactly that.

When I started many of the pc's were way behind with windows updates, as was the Primary Domain Controller.

I fully updated all PC's and the PDC, and have had no isses reported at all as a result.

What issues are you having?

 

[beerhunter2]

Many companies are running with that exact network configuration with no issues.

If you are having issues, please let this forum know, and they'll help you out.

Help! I've fallen and I can't reach my beer.

 

[deik313]

I'm having many problems with user profiles not unloading properly, or getting corrupted! The user logs in and everything is fine with his profile, then he logs off, logs back in the next day, and his profile can't be loaded and it creates a backup. I'm getting event errors such as 1511, 1517, 1515, etc... about roaming profiles not unloading correctly, or not finding the local copy. This is with roaming profiles AND local profiles. I made some of them local to see if it would correct the problem, but it is still happening.

This is a huge problem for us because currently the MyDocuments is part of the profile, so the user is losing all of his files (or so it seems to him). I am currently converting everyone to folder redirection, but I'm taking it slowly because of all the other problems we are having. ANY help on this would be soooooo appreciated!

 

[karmic]

I take care of many networks, mixed bag of NT (yes, nt), 2000 and 2003. Can't get away from xp sp2 now, comes streamlined into any new cd.

It sounds more like a DNS issue... when you run ipconfig from a workstation, what's the first dns server in the list? It should be your PDC ip address. Run nslookup on a workstation as well, what's the result? if this is all good, then next step.

I've taken to shutting down the xp firewall, it's not very intuitive for windows networking in a domain environment. Try disabling the firewall in services.msc, take the machine off the domain, reboot and re-add it again to see if results change.

Do you have any errors or warnings in your event viewer on the workstations?

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[deik313]

aHHH! I think you've got something. I did nslookup and it gives me the "non-existen domain" can't find server name error. It lists the IP address, but says it can't find it! Why would this be? The machine can join the domain, using the server name, why can't it find it in DNS?

 

[karmic]

check the options under dhcp for one, post back what you have there. nameservers, domain name, router etc. That's the place to start.

I find the vast majority of network problems lie with a problematic dns server and dhcp options... do you have wins installed too?

Lemme guess, you have userenv errors on the workstation too?

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[deik313]

In DHCP,do you mean scope options? I actually have 2 scopes defined, one is inactive. For the 2nd scope, which is the one we are using, I have:

Router: points to IP of my firewall
DNS Server: point first to IP of server, then IP's of ISP
DNS Domain name: says name of server-"schoolname.local"

I did notice that in DNS the top level says "SERVER" and my forward lookup zone has the domain name "schoolname.local" underneath it.

On DHCP though, the top level for scope says "server.schoolname.local", and underneath that is the scope options.

Don't have WINS installed, that I know of.

 

[karmic]

Sorry, scope options is what I meant, my bad... The options you list are good You really should install WINS and add it to your scope options, every network should have a WINS server...

Under the tcp/ip options on the server network card, you should have your DC IP address first in the list, preferred DNS server.

Did you try the option of disabling the firewall and re-add one computer to the domain?

As well, on one computer, add the "Domain user" group to the local administrator on a workstation to see if there's a difference. Service pack 2 does some weird things to domain workstations... (computer management, local users and groups, groups, administrator then add user.) Maybe the computer doesn't have the rights to the profiles. If this is the case, you can assign rights thru group policies...

Isn't troubleshooting fun?!?

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[deik313]

Wow...I just checked and I DON'T have my domain server as the preferred DNS server. I have my ISP. Why? I don't know. I seem to remember some problem occurring where we changed this to resolve some problem. I will change it back and see what happens.

I did try disabling the firewall, removing the computer from the domain and then joining again, and it didn't change anything (assuming I disabled the right thing...I disabled the service Windows Firewall/ICS? I also disabled automatic updates while I was there).

I will try adding the domain user to the local administrator. Thank you sooooooooo much for your help!

 

[deik313]

Well, I changed the preferred server to our DC, but it still is not reflected in nslookup. Still shows the ISP server. Why could this be? something still configured wrong in DNS?
This is frustrating! Everything was working fine on this server for 3 years, and suddenly everything is a mess.

 

[zigcoors]

Sounds like your DHCP scope is issuing the ISP's DNS server to your work stations .

Also you might want to check that you have an rDNS Zone set up. ie IP address to name. This helps speed up resolution in AD. If you already have one - make sure there is a PTR record for your DNS server(s)

Ian

 

[beerhunter2]

You might also check your workstations TCP/IP properties to make sure you don't have the DNS settings pre-set. It should be set to get DNS automatically.

Help! I've fallen and I can't reach my beer.

 

[deik313]

Thank you so much for your replies! Can anyone tell me how to set up the reverse zone and PTR record? I set up the forward but I do not remember how I did it. Sorry to be so clueless, I'm kind of learning as I go.

 

[deik313]

Also, just wondering, why would DHCP be pushing my ISP's address? I have the server IP as the first DNS addy listed. This is sooooo confusing!

 

[karmic]

Also, just wondering, why would DHCP be pushing my ISP's address? "

It's under your scope options, or at least it should be...

To set up reverse dns, open dns, under reverse dns create a new primary zone.

Under your forward zones, there should be a ptr record that shows "server.schoolname.local" or whatever your server/network is called.

Have you ever figured out the roaming profiles??

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[deik313]

Here is what I've done to try to resolve the roaming profile issue:

-reinstalled SP4 & SP4 rollup 1 on server (will do v2 tonight)
-installed all updates to XP-SP2 on the desktops
-configured clients with "Add Administrator group" policy
-configured clients with "Do no check for security" policy
-confiured server with "delete cached copies" of profile
-disabled Automatic Updates and Windows Firewall in services
-installed UPHClean on all clients
-uninstalled Spector, Vision5 and VNC from machines (thought they might be hanging onto the profile)
-gave Everyone modify privs on "All Users" folder on client (was getting USRENV errors referring to this)
-recreated Roaming Profile folders using the "Copy To"
-redirected Home folders & Pictures to different share

I think that's all. The problem has gotten much better, but it still happens at least 5 times a day. I'm pursuing the DNS settings because I know that there is something configured incorrectly there, since the workstations show my ISP server when I do nslookup.

The scope options DOES show my DC as the first DNS, then my ISP servers. I will try to add the reverse zone in DNS...my forward zone looks good.

I'm beginning to think I need to bring up a Windows 2003 server and just move everything over. I'm thinking part of the problem is just that my server is not able to keep up with the amount of traffic that we are putting through it every day. It is a school, so we have about 50 students logging off and on at exactly the same time every day. Could that be creating a bottleneck?

Thank you all for all the help with this!

 

[deik313]

I created the reverse zone. Do I want to enable DNS forwarding? Also, the Allow Dynamic Update check box is set to "Only Secure Updates" on the forward, and "No" on the reverse. Is this correct, or should they both be "yes"?

 

[deik313]

Sorry, one more thing...I tried to add the group "Domain User" to the Administrator user on a local workstation, and it is not there. "Domain User" is not listed as one of the groups on the local machine. Should it be?

 

[technome]

Yes, place your two ISP's DNS servers IP addresses in the list, place one more DNS server's IP address in the list from a different ISP, in case your ISP decides to play with the servers without notice, or if your ISPs DNS servers fail. Mark the "do not use recursion on this Domain" check box in the forwarders tabs ( do NOT uncheck "disable recursion" in the advanced tab). You should not have an external DNS server's address in the TCP/IP properties alternate DNS server entry or in the workstations TCP/IP properties.
This forces your DNS request to go the the DNS servers on the list, if the internal DNS servers cache can not answer the query, versus using the root servers. Generally this is faster as the query is likely to cached on the ISPs server. If the query go to root servers, the root servers do not have query answers (no cache), but supply referrals to servers which do..and added step. Also, recursion on the Internet via the root hint servers, is less secure, as there is more of a possibility of a query to an virus infected DNS server.

Only secure updates, on both

Has your cabling been tested with a cat 5 cable certification tester.

Run DcDiag /v
Run NetDiag /v
Repair any errors,or post the errors here.

With 50 uses, hope you have a managed switches, as they can supply you with details of your network health.
One bad wire or NIC can really affect a network, bad wires are the major problem, especially patch cords or mis wired cable pairs.

On the server NIC, there is a setting called flow control, try toggling it. Some times it is needed other times it causes big delays.

........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm