Re: Client worksation not resolving domain controller
- From: "Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 17 Mar 2006 17:14:50 -0600
Try to ping the computer by it's IP address also. If the domain computer has
it's Windows Firewall enabled then disable it [assuming it does not put the
computer at undue risk from the internet/untrusted networks] or enable the
exception for file and print sharing. Why is the domain controller the
default gateway?? You can use the support tool netdiag on both the domain
controller and domain workstation to check for network connectivity and
domain configuration issues such as DNS. Make sure that your domain
workstations use ONLY the domain controller as their preferred DNS server in
their tcp/ip properties and as shown via Ipconfig /all. --- Steve
"Rob D." <RobD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5BCA03CA-9687-4E94-ABDC-D05D5AF9D18E@xxxxxxxxxxxxxxxx
Hi,
My domain controller is configure as follows:
IP address: 192.168.0.102
Subnet:255.255.255.0
Default Gateway: 192.168.0.102
DNS Server 192.168.0.102
I'm able to ping a client workstation from the Server 2003 box, but when I
try to ping from client to server 2003 it just 'time out'
What needs to be configure? Please advise. Thanks!
Rob
.
- Prev by Date: Re: Group Policy Editor fails to initialize
- Next by Date: Re: Spy Falcon
- Previous by thread: Re: Group Policy Editor fails to initialize
- Next by thread: Re: Spy Falcon
- Index(es):
Relevant Pages
|
