you didn't say wether or not your running active directory services or just
domain controler funnctions, also
well outside the obvious like making sure the nic is set corectly (line
speed half or full duplex instead fo auto or carddefault netbios over tcp/ip
is on and not the obtain netbios information from dhcp server) I have
noticed switching from an onboard nic to an add on nic like the 3com
3c905-tx-nm series will increase performance dramaticaly. I'm such a firm
believer in it that i automatically place one in every box i put in a
production enviroment. I would also check the cable and hubs (especially
that it isn't more then 3 tier away from the main routing switch) the last
computer is going thru. It might be easier to just move the workstation to
another spot and see if it helps. Then if it does, you can start with the
cable run and go from thier.
Also there could be another hardware problem causeing an issue look for a
boot log and run a program called bla boot log analizer if it still can be
found (or somethign that will help analize the bootlog if it isn't still
availible). It should tell you wich processes are taking the longest and
might point you into a different direction that your looking in now. (you
may need to add the switch /bootlog to the end of the boot statment of the
boot.ini file. also the bootlog in win2000 should be named ntbtlog.txt)
Another thing to try is conect another computer to a hub (not a switch
because you want to intercept tcp packets from another machine) before the
run goes inot the wall, then run a packet capture program on the other
computer. Somethign like ethereal from
http://www.ethereal.com/ . What you
are looking for is wild* packets that shouldn't be there. Lots of
retransmitted packets or fales destination packets. Compare this with
packets captured form another computer at a different location and see if
somethign sticks out. You may also want to run it on the server or servers
to see if somethign is going on there.
Spyware or somethign along the lines (trojans/virus) could have changed the
hosts file and it is trying to conect to an outside server first. I recently
saw a piece of spycrap that did a passthru on everythign from another server
and set the dns's up for thiers instead of the inhouse dns or the isp's dns
so they could record everything you visited and done. This raised some
serious security concernes for me because it theoreticaly could intercept
and read eveythign being sent from the workstation including creditcard
numbers and password as well as sensative company information.
I'm not sure if i could recomend anythign else at this time because your
probably going to find somethign in the bootlog. but if it is still not
going, then maybe the windows install is borked and should be reinstalled.
Sometimes bad or damaged system files can cause problems likethis but I
would think it would be noticable all along instead of just startup and log
on.
Also somethign like this
http://www.lavalys.com/index.php?page=product&view=2 the home edition is
free and the pro edition has a trial that should give you some insight. it
also had a network speed and performance test with using it as a server on
another machine.
I dno't care for spell checkers and my grammer isn't all that great so i
hope this is readable and offers some help to you. There are alot of other
things youy casn doo too..these are just the eassiest ones that pop off the
top of my head.
Jesus said:
Yes the windows 2000 takes 15 to 20 min to log-on, I've spoken with
several people and they told me that could be a DNS problem, you have any
more advices, thanks.
