xpP slow after 2003 Server upgrade

[Guest]

We recently upgraded to 2003 Server and now all the workstations that have XP
Pro all have dramatically increased the startup time versus those that have
XP home edition. Before the upgrade mine was up in about 20 seconds max after
I put in my password, now it is 5 minutes. I have run Spybot/Adaware many
times with neither finding much, due to Internet use and am used to running
these. Others under the same operating sytem as mine have complained about
this also. The only thing I've really found is to take Norton out of startup,
but have not tried this. Hard to believe it would increase the time this
much. We don't have a full time IT person on staff. I've pretty much do the
troubleshooting on all network, software, etc. problems and am at quite a
loss here and did not find anything yet in 2003 Server newgroups. If anyone
has any idea, it would be greatly appreciated.

 

[Richard G. Harper]

How are your DNS settings? Any time I see a slow client logging onto a
domain I wonder if DNS is correctly configured. You should have one DNS
server on your domain resolving all address requests inside the domain and
all client PCs should be pointing only to that DNS server.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Guest]

Thanks for responding so quickly. As I am not at work now, I will check this
out in the morning and try to research this some more and will report back.

How are your DNS settings? Any time I see a slow client logging onto a
domain I wonder if DNS is correctly configured. You should have one DNS
server on your domain resolving all address requests inside the domain and
all client PCs should be pointing only to that DNS server.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

We recently upgraded to 2003 Server and now all the workstations that have
XP
Pro all have dramatically increased the startup time versus those that
have
XP home edition. Before the upgrade mine was up in about 20 seconds max
after
I put in my password, now it is 5 minutes. I have run Spybot/Adaware many
times with neither finding much, due to Internet use and am used to
running
these. Others under the same operating sytem as mine have complained about
this also. The only thing I've really found is to take Norton out of
startup,
but have not tried this. Hard to believe it would increase the time this
much. We don't have a full time IT person on staff. I've pretty much do
the
troubleshooting on all network, software, etc. problems and am at quite a
loss here and did not find anything yet in 2003 Server newgroups. If
anyone
has any idea, it would be greatly appreciated.

 

[Richard G. Harper]

No problem - we'll be here.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Thanks for responding so quickly. As I am not at work now, I will check
this
out in the morning and try to research this some more and will report
back.

How are your DNS settings? Any time I see a slow client logging onto a
domain I wonder if DNS is correctly configured. You should have one DNS
server on your domain resolving all address requests inside the domain
and
all client PCs should be pointing only to that DNS server.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

We recently upgraded to 2003 Server and now all the workstations that
have
XP
Pro all have dramatically increased the startup time versus those that
have
XP home edition. Before the upgrade mine was up in about 20 seconds max
after
I put in my password, now it is 5 minutes. I have run Spybot/Adaware
many
times with neither finding much, due to Internet use and am used to
running
these. Others under the same operating sytem as mine have complained
about
this also. The only thing I've really found is to take Norton out of
startup,
but have not tried this. Hard to believe it would increase the time
this
much. We don't have a full time IT person on staff. I've pretty much do
the
troubleshooting on all network, software, etc. problems and am at quite
a
loss here and did not find anything yet in 2003 Server newgroups. If
anyone
has any idea, it would be greatly appreciated.

 

[Interrogative]

We recently upgraded to 2003 Server and now all the workstations that have
XP
Pro all have dramatically increased the startup time versus those that
have
XP home edition. Before the upgrade mine was up in about 20 seconds max
after
I put in my password, now it is 5 minutes. I have run Spybot/Adaware many

It is simply a well known issue with XP. It is NOTORIOUSLY slow left on auto
assign IP to attain the network. 20 seconds is unbelievably slow so 5
minutes is not on!

You HAVE to manually assign each IP for each XP machine and then you get
about 2 seconds to get on to the network.

 

[Richard G. Harper]

You keep repeating this "fact" - where may we find some proof? Your
repeated "It just is so!" statements, by the way, are not proof;
documentation would be proof.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Interrogative]

You keep repeating this "fact" - where may we find some proof? Your
repeated "It just is so!" statements, by the way, are not proof;
documentation would be proof.

Sheesh you are damned lazy! You cant get off your arse to check the facts
for yourself and want someone else to do it for you? Hire a bloody
secretary!

It is well known. The fact that YOU don't know it is proof enough about your
side of the argument. I don't have to provide proof. You can do that by
yourself. Set your network to ALL auto assign (for XP machine I mean) and
reboot the lot and wait. Now make assign manually and do the same.

 

[Richard G. Harper]

Son, I run a network with 220+ PCs, Windows 2000 and Windows XP Pro mixed.
Every one of my clients uses DHCP and auto-assigned IP addresses. Not a one
of them has the "problem" you insist exists. The WinXP clients get their IP
addresses and log on as fast as, if not faster than, their Win2K cousins.

It is well known that the Easter Bunny brings baskets of goodies to good
girls and boys on Easter morning ... SO SHOW ME THE BUNNY!?!



--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm



<crap clippage>

 

[Leythos]

We recently upgraded to 2003 Server and now all the workstations that have XP
Pro all have dramatically increased the startup time versus those that have
XP home edition. Before the upgrade mine was up in about 20 seconds max after
I put in my password, now it is 5 minutes.

You don't have DNS and/or DHCP setup properly on the 2003 Server. In
addition, unless you have the XP stations setup for DHCP they won't see
all the changes.

If you setup DHCP, make sure that your properly configure the scope
options - you can verify that the XP machines get all the scope info by
doing an IPCONFIG /ALL and checking the domain, ip, dns server, dhcp
server, etc... are all working correctly.

You may also be running a single name domain instead of a proper
company.local or company.lan name (or, even worse, running a company.com
or company.net where there is already a public name that's the same).

You do have all your workstations pointed to the server IP for their DNS
server?

Do an IPCONFIG /ALL and post the entire results here.

XP systems logon using a Dynamic IP faster than 2000 machines do.

 

[Guest]

I will try to do below in the morning at work. I do know that we let the
server automatically assign our addresses versus static on our workstations.
Pre Server 2003, no problem and was set up the same, but will try to get
infor posted because I've even noticed hesitation opening, saving files,
delays in words being shown that have been typed with documents on the
server. Others with same startup problems have indicated the same. The other
users are on XPhome and are logging into a workgroup. We are logging into a
domain. Not only is the sofware new, but the server itself is new too. I log
in to a like CRS-nt2 domain, but there is a local. something also in my
network information. Anyway, I will try to get to this in the morning, but am
due out of the office after 11:00 on, but have to move forward on this soon.
Am going to reboot the server first thing in the morning to see if any
difference once connected. Thanks for your assistance.

 

[Guest]

The results are below for the ipconfig /all. The shut down and then to start
back up did nothing. I retimed my machine and it was 5:05 minutes applying
computer settings, then went into personal quickly, then immediately to
desktop.



Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

P:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DARRYLK
Primary Dns Suffix . . . . . . . : jmc.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : jmc.local
jmc.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : jmc.local
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connect
ion
Physical Address. . . . . . . . . : 00-0B-DB-54-E7-E3
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.1.1.40
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.1.1.1
DHCP Server . . . . . . . . . . . : 192.1.1.3
DNS Servers . . . . . . . . . . . : 127.0.0.1
192.1.1.3
Primary WINS Server . . . . . . . : 192.1.1.3

P:\>

 

[Leythos]

P:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DARRYLK
Primary Dns Suffix . . . . . . . : jmc.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : jmc.local
jmc.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : jmc.local
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connect
ion
Physical Address. . . . . . . . . : 00-0B-DB-54-E7-E3
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.1.1.40
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.1.1.1
DHCP Server . . . . . . . . . . . : 192.1.1.3
DNS Servers . . . . . . . . . . . : 127.0.0.1
192.1.1.3
Primary WINS Server . . . . . . . : 192.1.1.3

Why the heck do you have 127.0.0.1 as your primary DNS? That's asking
your system to point to itself for DSN - assuming that the IP Config
listing that you posted is for your workstation and not the server.

You need to setup your DHCP scope to issue DNS as the server IP
(provided that your 2003 server is running DNS).

The server TCP/IP settings should show it's DNS setting as it's IP
address. Configure forwarders in DNS to resolve external IP's for the
LAN users.

 

[Guest]

Thanks for your quick response again. I will get this information to our tech
who set up our system as much of this is "over my head". What I printed was
from my workstation, but I did notice as I went to the server that it looked
like we had static IP addresses because I was the third computer logged on,
but the address did not look like the third one issued, but that and printing
the other out is as far as I got this morning. I will try to "educate myself"
more this weekend on what you have described and will get with our tech guy
Monday. Thanks so much and if there is any specific web sites you think I
could go to, it would be appreciated.

 

[Interrogative]

Gee you want proof off me and then wont do the work I said but you expect
everyone to believe what you have said below. If you are too lazy to try or
possibly don't want to be proven correct, sit back and enjoy your mistake.
It is able to be proven by doing what I said that XP is slower on auto
assign than manual assign but as YOU wont attempt it, you wont ever know
will you? You must LOVE the taste of sand in your mouth the way you have
your head in that hole!