[windows2000] SV: Re: Problem with workstation not seeing the domain
- To: <windows2000@xxxxxxxxxxxxx>
- Date: Tue, 14 Oct 2003 20:01:50 +0200
also verify connection with pings.
Order to ping:
ip adress of another host on same subnet = if ok, connectivity/dhcp ok
ip address of another host on different subnet = if ok, routing (default
gateway) ok, if not, verify that there is no custom gateway defined on the
computer.
hostname of another host = verify the looked up address, if ok, naming services
ok., if not, verify wins/dns.
Mvh
Svein Arild
-----Opprinnelig melding-----
Fra: Jeff Stockard [mailto:JStockard@xxxxxxxxxxxxxxx]
Sendt: 14. oktober 2003 19:39
Til: windows2000@xxxxxxxxxxxxx
Emne: [windows2000] Re: Problem with workstation not seeing the domain
Did you test the cable from end to end (pull the end out of the switch
or hub and pull the other end out of the PC and check from the switch to
the PC)? Are any of the patch cables, crossover cables?
-----Original Message-----
From: Martin, Eddie [mailto:EMartin@xxxxxxxxxxxxx]
Sent: Tuesday, October 14, 2003 12:55 PM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Problem with workstation not seeing the domain
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?
Eddie Martin
********************************************************
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
********************************************************
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:
