TCPIP Problem

  • Thread starter Thread starter Danharlan
  • Start date Start date
D

Danharlan

I have a client who has a windows 2000 network with XP
Pro worlstations. One worlstation that is connected
wireles is having IP problems. I rebuilt the PC and was
able to connect wireleessly to the networkj download all
the windows updates and even cpnnect to the domain, but
as soon as I reboot and login inoto the domain I get a
DHCP address from the router but cannot connect to
anything else on the network. I can only ping myself,
not the router or server or anything.

The only thing that happened before it stopped working is
that I logged into the domain. Could this be a problem
with the profile for the account I logged in with and if
so when I log out and even take the machine off the
domain and log in locally I can never get the ip working
correctly. I am sure it is not a wireleess issue becuase
I am connected to the network and getting good signal
strrength and I am getting a dhcp address. I tried hard
coding a static address but the smae thing happens.

Any thoughts?
 
Run ipconfig /all on that computer to make sure it is on the same network as the
domain and that it is configured to use the AD domain controller only as it's
preferred dns server in tcp/ip properties. Running netdiag on it can also help
pinpoint problems by showing failed tests if any and be sure to disable any
personal firewall on that computer which may cause a problem accessing domain
resources and check that time is in synch with domain controller and in right
time zone as kerberos only allows a five minute time skew. Also try pinging by
IP address - not just name to establish connectivity and consider trying in safe
mode with networking to rule out startup service/application conflicts.--- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;321708
 
Thank you for all the suggestions. The first thing I
confirmed was that the ipconfig /all information was
correct. I never heard of the netdiag command and can't
seem to run it on my XP workstation. Is it a builtin
command ort a seperate utility?

I don't think it is a time issue becuase its not an issue
of not getting on the domain its an isue of getting a
dhcp address and then not being able to talk to the rest
of the networl. I will definetley try in safe mode.

Thjanks and I will get back to you once I run the
additional tests.

-----Original Message-----
Run ipconfig /all on that computer to make sure it is on the same network as the
domain and that it is configured to use the AD domain controller only as it's
preferred dns server in tcp/ip properties. Running netdiag on it can also help
pinpoint problems by showing failed tests if any and be sure to disable any
personal firewall on that computer which may cause a problem accessing domain
resources and check that time is in synch with domain controller and in right
time zone as kerberos only allows a five minute time skew. Also try pinging by
IP address - not just name to establish connectivity and consider trying in safe
mode with networking to rule out startup
Click to expand...
service/application conflicts.--- Steve
 
Sorry. It is on the XP install cd under support/tools where you will need to
run the setup program. The W2K version is not compatible with XP
computers. --- Steve
 
Back
Top