| Author |
Message |
Greg
Guest
|
 Posted:
Mon Jan 24, 2005 8:55 pm Post subject:
Unable to connect to server 2003 and AD |
|
|
Hi All,
I seem to have this problem. I setup a windows 2003 server and AD. I am
unable to connect to the server on a WinXP client. I cannot not ping the DNS.
However, I can ping it on the server.
Below I have pasted in the ipconfig results of the server and the client.
192.168.1.1 in the Gateway is my router to cable internet access.
The IP addresses are static.
Any help is greatly appreciated.
Greg
SERVER:
Windows IP Configuration
Host Name . . . . . . . . . . . . : server
Primary Dns Suffix . . . . . . . : lcs.local
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : lcs.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0C-76-5D-A4-5D
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.10
CLIENT:
Windows IP Configuration
Host Name . . . . . . . . . . . . : LAPTOP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 10/100 Mini PCI Ethernet
Adapter
Physical Address. . . . . . . . . : 00-00-86-40-19-2D
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.10 |
|
| Back to top |
|
 |
Todd J Heron
Guest
|
| Posted:
Mon Jan 24, 2005 9:05 pm Post subject:
Re: Unable to connect to server 2003 and AD |
|
|
Is ping by IP successful? Is it just ping by name which is failing? I see
that the client is missing it's Primary DNS Suffix which will cause problems
although on single subnet it should resolve the name by broadcast unless
you've disabled NetBIOS over TCP/IP on the server?
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights |
|
| Back to top |
|
|
Greg
Guest
|
| Posted:
Mon Jan 24, 2005 9:29 pm Post subject:
Re: Unable to connect to server 2003 and AD |
|
|
Todd,
"Todd J Heron" wrote:
| Quote: | Is ping by IP successful?
No... |
Is it just ping by name which is failing?
Both are failing...
| Quote: | I see that the client is missing it's Primary DNS Suffix which will cause problems
although on single subnet it should resolve the name by broadcast unless
you've disabled NetBIOS over TCP/IP on the server?
NetBIOS is set to default. |
Here is other results I have just found:
Running the netdiag this was returned...
DNS test . . . . . . . . . . . . . : Failed
[WARNING] The DNS entries for this DC are not registered correctly on
DNS se
rver '192.168.1.10'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.
Also running nslookup this was returned:
*** Can't find server name for address 192.168.1.10: Non-existent domain
Default Server: UnKnown
Address: 192.168.1.10
HTH...Thanks,
Greg |
|
| Back to top |
|
|
Todd J Heron
Guest
|
| Posted:
Mon Jan 24, 2005 9:38 pm Post subject:
Re: Unable to connect to server 2003 and AD |
|
|
You need to fix the physical problem which is causing ping by IP to fail
otherwise ping by name will never work. What are you using here from client
to server - crossover cable, or do you have a hub, switch, or router
connecting them? You said the server can ping itself - but can the client
do so? What errors do you see in their event logs? Look in the Device
Manager of each client and make sure the NIC on both of them do not have a
yellow exclamation mark or red X on it.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights |
|
| Back to top |
|
|
Greg
Guest
|
| Posted:
Mon Jan 24, 2005 10:33 pm Post subject:
Re: Unable to connect to server 2003 and AD |
|
|
Todd,
| Quote: | You need to fix the physical problem which is causing ping by IP to fail
otherwise ping by name will never work. What are you using here from client
to server - crossover cable, or do you have a hub, switch, or router
connecting them?
|
Linksys Router w/DHCP disables
IP: 192.168.1.1
| Quote: | You said the server can ping itself - but can the client do so?
|
No...
| Quote: | What errors do you see in their event logs?
|
There are no errors in the DNS server log. It started ok. However in the
Application log I have the following errors:
first error:
Windows cannot query for the list of Group Policy objects. Check the event
log for possible messages previously logged by the policy engine that
describes the reason for this.
second error:
Windows cannot access the file gpt.ini for GPO
CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=lcs,DC=local.
The file must be present at the location
<\\lcs.local\sysvol\lcs.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.
(The network path was not found. ). Group Policy processing aborted.
I think this is because of the DNS problem.
| Quote: | Look in the Device Manager of each client and make sure the NIC on both of them do not have a yellow exclamation mark or red X on it.
|
The network adapters are working. I have Internet access on the client and
server.
Thanks again for your help...
Greg |
|
| Back to top |
|
|
Todd J Heron
Guest
|
| Posted:
Mon Jan 24, 2005 10:46 pm Post subject:
Re: Unable to connect to server 2003 and AD |
|
|
The client needs to be able to ping itself before it can ping anything else.
The ipconfig /all stats look good on it, and it is working properly. So I
suggest this. Right-click on the NIC under Network Connections and select
"Disable". Then, right-click on it again and choose "Enable". Then, try to
have the client ping itself and then the server again. What happens?
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights |
|
| Back to top |
|
|
Greg
Guest
|
| Posted:
Mon Jan 24, 2005 10:57 pm Post subject:
Re: Unable to connect to server 2003 and AD |
|
|
The client pings itself, but not the server.
"Todd J Heron" wrote:
| Quote: | The client needs to be able to ping itself before it can ping anything else.
The ipconfig /all stats look good on it, and it is working properly. So I
suggest this. Right-click on the NIC under Network Connections and select
"Disable". Then, right-click on it again and choose "Enable". Then, try to
have the client ping itself and then the server again. What happens?
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
|
|
|
| Back to top |
|
|
Todd J Heron
Guest
|
| Posted:
Mon Jan 24, 2005 11:08 pm Post subject:
Re: Unable to connect to server 2003 and AD |
|
|
On the server, right-click on the NIC under Network Connections and select
"Disable". Then, right-click on it again and choose "Enable". Then, try to
have the server ping itself and then have the client ping the server again.
What happens?
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights |
|
| Back to top |
|
|
Greg
Guest
|
| Posted:
Mon Jan 24, 2005 11:57 pm Post subject:
Re: Unable to connect to server 2003 and AD |
|
|
Unfortunately, it is the same...
"Todd J Heron" wrote:
| Quote: | On the server, right-click on the NIC under Network Connections and select
"Disable". Then, right-click on it again and choose "Enable". Then, try to
have the server ping itself and then have the client ping the server again.
What happens?
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in