I am actually looking for an answer to the same problem..... I just replaced 6 computers here at work with new dimension 2400 systems running xp pro. We log into our domain controlling server which is running advanced server 2000. It takes an insanely long amount of time for it to get logged in, and then once we are in it is almost like it logs us out after a certain amount of time of inactivity to the point that we actually have to log back out and in again. Major pain in an office environment since we have our main printer conected to a printserving computer on the network, so if we dont realize we have lost our conection to the server and try to print it lags for a long time trying to find a printer that it cant connect too. If anyone has any idea on how to fix this I would appriciate it. Thanks in advance.
they boot up just fine and get to the loggin screen, after entering user name and password that is when it takes a long time to get logged in and everything. They are using the onboard network controller, Broadcom 440x, to connect. It all runs through a switch, so for the complete network it is setup DSL MODEM~~~>ROUGHTER~~~>SWITCH, with all the systems, including the server, conecting directly to the switch. It is a cat5 network, not wireless or anything like that. The computers perform normally for everything, untill they get absolutely horrible as they lag whenever a program loads that uses the printer and obviously anything on the server doesnt work> As for an IT team, I am the IT team along with the husband of one of our employees I do know a lot, but I am a rooky when it comes to the server versions of windows. Thanks for your help.
To start helping you resolve this problem as I said above - Alas more info is needed ......please respond to questions below :
Why do you think client PC's are slow, are they booting up , are you using a switched network with spanning tree turned on per host port ?
What NIC cards are you using - what type of network do you have ?
What are you seeing in the event & security log of your server - are there failed authentications ?
Once the XP pc's are logged in - do they behave normally for all other purposes and applications
Do you have a IT Network team who can capture the "log in"process of a PC onto a Sniffer to see what's going on at packet level ?
The computers perform normally for everything, untill they get absolutely horrible as they lag whenever a program loads that uses the printer and obviously anything on the server doesnt work
OK - don't panic - this is perfectly resolvable - but need to check a few things and info from the server/pc's to understand your statement -and get to the heart of technical detail.
(1) Check Server IP network communication to PC hosts , open a DOS shell on Server ......Start->Run->cmd and type ipconfig/all. From this window try pinging a couple of PC hosts , "ping ip-address-1" , ping ip-address-2" where these are know IP address of your host PC's
Are these successful ?.....do you get "Reply in x ms"
If not is the Ip address of the server in the same subnet of PC's - check output of ipconfig/all
(2) On the server can you get an extract of the Event Log for Applications/Security - so that we can see if there any immediate log warnings about login failures or failed processes on server. Event Viewer is in the Program/Accessories of XP or WIn2k.
paste a snippit of any error or warning messages here
We use DELL PRECITION 350 as clients - we also use DELL standard network card. The network consists of One server and four 24 port swiches. Beetween the switches there is fibre connections. We have spanning tree enabled in the switches.
The delay comes after I pressed the CTRL-alt del in the welcome screen and waiting for my account to appear.
The XP behave normally - somtimemes Word and Excel looks up.
According to poor power supply. We have two power shortages during each day. (We are an UN mission in the middle of Congo). But almost all equipment have UPS.
Can you check on your 24port LAN switches - that the copper ports you plug your PC's into have "portfast" enabled.
Since network switches run spanning tree - when a PC boots up - the switch will wait for the link to come active - and go thorugh 3 stages - - Listening, Learning & Forwarding..........no traffic from your PC will get onto the network until the switch has moved your PC port to "Forwarding" - this can take up to 50 seconds....which might be what your seeing
This is standard spannign tree - since the network has no way of knowing if you just plugged two switch ports together and has to ensure stability and topology of the network remains "loop free"....so is first Listening for BPDU's in case its another switch.
Action :
Check if you move you PC ports on the switch into Portfast "Cisco term", other switches has similiar terms, but basically it skips the listenign . learning phases and jumps straight to Forwarding. Note do no use such a command on network to network port - this is only intended for dumb PC/Host/Server.............dumb meaning they do not participate in networking topology protocols.
Its seems to work a little bit faster after your suggestions but it still takes a lot of time loading profile settinging (2-3 minutes) in some accounts.
I had a similar problem on my Win2k server after the MS Blaster worm. Are you running Active Directory with DNS enabled? If the DNS is not set up correctly logon will take 15 mins or so. Your clients should point to your server for DNS and that box should use DNS forwarding outbound to the internet.
sentinel-master
345 Posts
0
October 7th, 2003 10:00
Alas more info is needed
Why do you think client PC's are slow, are they booting up , are you using a switched network with spanning tree turned on per host port ?
What NIC cards are you using - what type of network do you have ?
What are you seeing in the event & security log of your server - are there failed authentications ?
Once the XP pc's are logged in - do they behave normally for all other purposes and applications
eternalphoenix
2 Posts
0
October 10th, 2003 16:00
sentinel-master
345 Posts
0
October 10th, 2003 16:00
To start helping you resolve this problem as I said above - Alas more info is needed
......please respond to questions below :
Why do you think client PC's are slow, are they booting up , are you using a switched network with spanning tree turned on per host port ?
What NIC cards are you using - what type of network do you have ?
What are you seeing in the event & security log of your server - are there failed authentications ?
Once the XP pc's are logged in - do they behave normally for all other purposes and applications
Do you have a IT Network team who can capture the "log in"process of a PC onto a Sniffer to see what's going on at packet level ?
eternalphoenix
2 Posts
0
October 10th, 2003 17:00
they boot up just fine and get to the loggin screen, after entering user name and password that is when it takes a long time to get logged in and everything. They are using the onboard network controller, Broadcom 440x, to connect. It all runs through a switch, so for the complete network it is setup DSL MODEM~~~>ROUGHTER~~~>SWITCH, with all the systems, including the server, conecting directly to the switch. It is a cat5 network, not wireless or anything like that. The computers perform normally for everything, untill they get absolutely horrible as they lag whenever a program loads that uses the printer and obviously anything on the server doesnt work> As for an IT team, I am the IT team along with the husband of one of our employees I do know a lot, but I am a rooky when it comes to the server versions of windows. Thanks for your help.
To start helping you resolve this problem as I said above - Alas more info is needed
......please respond to questions below :
Why do you think client PC's are slow, are they booting up , are you using a switched network with spanning tree turned on per host port ?
What NIC cards are you using - what type of network do you have ?
What are you seeing in the event & security log of your server - are there failed authentications ?
Once the XP pc's are logged in - do they behave normally for all other purposes and applications
Do you have a IT Network team who can capture the "log in"process of a PC onto a Sniffer to see what's going on at packet level ?
Sentinel Master
sentinel-master
345 Posts
0
October 10th, 2003 19:00
The computers perform normally for everything, untill they get absolutely horrible as they lag whenever a program loads that uses the printer and obviously anything on the server doesnt work
OK - don't panic
- this is perfectly resolvable - but need to check a few things and info from the server/pc's to understand your statement -and get to the heart of technical detail.
(1) Check Server IP network communication to PC hosts , open a DOS shell on Server ......Start->Run->cmd and type ipconfig/all. From this window try pinging a couple of PC hosts , "ping ip-address-1" , ping ip-address-2" where these are know IP address of your host PC's
Are these successful ?.....do you get "Reply in x ms"
If not is the Ip address of the server in the same subnet of PC's - check output of ipconfig/all
(2) On the server can you get an extract of the Event Log for Applications/Security - so that we can see if there any immediate log warnings about login failures or failed processes on server. Event Viewer is in the Program/Accessories of XP or WIn2k.
paste a snippit of any error or warning messages here
kallby
3 Posts
0
October 11th, 2003 08:00
We use DELL PRECITION 350 as clients - we also use DELL standard network card. The network consists of One server and four 24 port swiches. Beetween the switches there is fibre connections. We have spanning tree enabled in the switches.
The delay comes after I pressed the CTRL-alt del in the welcome screen and waiting for my account to appear.
The XP behave normally - somtimemes Word and Excel looks up.
According to poor power supply. We have two power shortages during each day. (We are an UN mission in the middle of Congo). But almost all equipment have UPS.
sentinel-master
345 Posts
0
October 12th, 2003 12:00
Can you check on your 24port LAN switches - that the copper ports you plug your PC's into have "portfast" enabled.
Since network switches run spanning tree - when a PC boots up - the switch will wait for the link to come active - and go thorugh 3 stages - - Listening, Learning & Forwarding..........no traffic from your PC will get onto the network until the switch has moved your PC port to "Forwarding" - this can take up to 50 seconds....which might be what your seeing
This is standard spannign tree - since the network has no way of knowing if you just plugged two switch ports together and has to ensure stability and topology of the network remains "loop free"....so is first Listening for BPDU's in case its another switch.
Action :
Check if you move you PC ports on the switch into Portfast "Cisco term", other switches has similiar terms, but basically it skips the listenign . learning phases and jumps straight to Forwarding. Note do no use such a command on network to network port - this is only intended for dumb PC/Host/Server.............dumb meaning they do not participate in networking topology protocols.
kallby
3 Posts
0
October 13th, 2003 05:00
Thanks for the help
frankmarra
1 Message
0
October 15th, 2003 16:00
johnchen8
1 Message
0
November 7th, 2003 04:00
LePhantom
6 Posts
0
November 25th, 2003 02:00
I had a similar problem on my Win2k server after the MS Blaster worm. Are you running Active Directory with DNS enabled? If the DNS is not set up correctly logon will take 15 mins or so. Your clients should point to your server for DNS and that box should use DNS forwarding outbound to the internet.
Dave