[windows2000] Re: Problem with workstation not seeing the domain
- From: "Jeff Stockard" <JStockard@xxxxxxxxxxxxxxx>
- To: <windows2000@xxxxxxxxxxxxx>
- Date: Wed, 15 Oct 2003 06:58:57 -0400
I would think that since he can connect from one network jack, but not
another network jack, that the software and the NIC have been eliminated
from the pool of probable cause.
I could be wrong.
Jeff
-----Original Message-----
From: Chris Berry [mailto:compjma@xxxxxxxxxxx]
Sent: Tuesday, October 14, 2003 6:14 PM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Re: Problem with workstation not seeing the
domain
>From: "Martin, Eddie" <EMartin@xxxxxxxxxxxxx>
>I recently took a computer and moved it from one desk to another. Once
i
>moved the computer, I tried to login to the network. It said that the
>domain was inaccessible. I checked the Cat5 cabling in the back server
>room
>and at the desk and both tested fine. TCP/IP is enabled to obtain an
IP
>automatically along with the DNS. Any reasons why this computer
wouldn't
>be
>able to see the domain? I checked the link light on the NIC card and
it
>seems to be working fine. I guess one step I could take is to try
another
>workstation at that location to see if it gets the same results when
trying
>to access the domain. Does anyone have any other suggestions?
Start with standard troubleshooting techniques, the problem must be
either
physical or software.
If it's physical, these would be good things to check:
1) Check that all cables are plugged in firmly at both ends
2) Use your cat5 tester to verify that the run is good from the nic to
the
switch
3) Try a different switch port
4) Try a different network card
5) Check the network jack
If the problem is software here are some good items to take a look at:
1) Do you get a ping from the loopback address
2) Is the MAC address showing up in the arp cache on the switch
3) Can you ping the server's nic
4) Are you trying to login to the correct domain (not a different one or
the
local machine)
5) Are you part of the correct subnet
6) Are there any routers in between, and if so are they properly
configured
7) Try clearing your DNS cache
8) Are you trying to connect to the correct logon server
9) Have you tried using a staic IP address
Once you've checked all that, if it's still not working come back with
more
info and we'll try to help you some more.
Chris Berry
compjma@xxxxxxxxxxx
Systems Administrator
JM Associates
"We are successful when our bosses wonder what it is we do all day." --
Tim
Mullen
_________________________________________________________________
Add MSN 8 Internet Software to your current Internet access and enjoy
patented spam control and more. Get two months FREE!
http://join.msn.com/?page=dept/byoa
********************************************************
This Week's Sponsor - RTO Software / TScale
What's keeping you from getting more from your terminal servers? Did you
know, in most cases, CPU Utilization IS NOT the single biggest
constraint to scaling up?! Get this free white paper to understand the
real constraints & how to overcome them. SAVE MONEY by scaling-up rather
than buying more servers.
http://www.rtosoft.com/Enter.asp?ID=147
**********************************************************
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
********************************************************
This Week's Sponsor - RTO Software / TScale
What's keeping you from getting more from your terminal servers? Did you know,
in most cases, CPU Utilization IS NOT the single biggest constraint to scaling
up?! Get this free white paper to understand the real constraints & how to
overcome them. SAVE MONEY by scaling-up rather than buying more servers.
http://www.rtosoft.com/Enter.asp?ID=147
**********************************************************
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
Other related posts:
