Solved

New  XP pc cannot find domain controlller or ping it

Posted on 2010-09-11
33
534 Views
Last Modified: 2012-05-10
I have two new XP PC's that I cannot get to join the domain. When I attempt to add to domain, it cannot find the DC. It can ping the router 192.168.0.1 but cannot ping the server 192.168.0.5. It also can ping the printers but not any of the pc's.
0
Comment
Question by:mel11755
  • 13
  • 8
  • 6
  • +4
33 Comments
 
LVL 9

Expert Comment

by:rfportilla
ID: 33655752
Are you pinging by ip address?  Are the computers you are pinging on a different network segment?  ARe you sure you didn't repeat an IP address or computer name?  Are you using DHCP?  

Firewall settings on other computers could cause them not to reply to ping, but this should not have anything to do with finding the domain controller.  Are other computers able to ping each other and the server?
0
 

Author Comment

by:mel11755
ID: 33655815
Yes by IP address.
Same network segment
DHCP and static. Tried both ways
0
 
LVL 24

Expert Comment

by:rfc1180
ID: 33655826
is the DC on the same switch as the new XP systems? What does the local arp table show?
do you have access to the switch(es)?

Billy
0
 
LVL 1

Expert Comment

by:amjad4
ID: 33656011
go to windows xp computer. go to start menu. go to run
than type command . ipconfig /all

than check your Network segment.
if your xp pc IP address segment is different. than change your XP PC IP manual.

IP Address          : 192.168.0.*** (available IP Address)
subnet mask        :  255.255.255.0
Default Gateway : 192.168.0.1
Preferred DNS     : 192.168.0.5

Than click ok..

0
 
LVL 11

Expert Comment

by:kaskhedikar_tushar
ID: 33656034
Hello,

Check with firewall.Make sure that only one firewall should be working.
If you are using antivirus with firewall,so please check for the both firewall is on? if both firewall is turn on,please turn off the windows firewall & configure the antivirus firewall with proper IP address range & then check.

If the problem is persist then check for the physical connectivity such as cat 5 cable, switch & computer network card.Check with ping command from both side,if one side is pinging so this is the problem of network card.

Regards,
Tushar Kaskhedikar

   
0
 

Author Comment

by:mel11755
ID: 33656116
So here let me confuse you more.  For the most part I have already done all the things each of you have suggested.  But here is what happened tongiht. We had to rebuild the server with new hard drives. The server has two nic cards. The original HD had only one nic card enabled. The new HD has both nic cards enabled. I gave the server the same IP address of 192.168.0.5. But I only gave it one ip address. When I perform an Iipconfig /all it shows that both nic cards are working . One with the ip address I hard coded it with (192.168.0.5) and the other 192.168.0.2. When I click on the properties, it tells me that both were configured manually.
Ok here is more strangeness.  The 192.168.0.5 has a dns of 127.0.0.1. I did not set this as the dns. It was suppose to be 192.168.0.5 as the server has the role of a DNS serer. It also has these settings:
192.168.0.5
255.255.255.0
192.168.0.1

127.0.00.1

Now the second nic has this settings:
192.168.0.2
255.255.255.0

127.0.0.1
But no gateway.  

So now the XP Computers can see the 192.168.0.2 ip address. You say good. Well here is the next odd thing. I only have one network cable attached. The other nic card does not have a cable.

So how am I obtaining two IP addresses if I only have it connected to one nic card.

And yes I was able to join the XP computers to the domain. So long as I keep the 192.168.0.2 connection.

Can anyone explain???  
0
 
LVL 4

Expert Comment

by:Nice-Ghaza
ID: 33656141
Dear,
           Please try to that Configure the IP Like That

Your systm IP  192.168.0 122
Subnet Mask  255.255.255.0
Gateway        192.168.0..........
DNS                 192.168.0........
 


It will be solved your Problem
0
 
LVL 9

Expert Comment

by:rfportilla
ID: 33656149
This is indeed a strange issue.

Which NIC is connected?  And why do you have both configured for the same subnet?

Your problem is partially in your DNS, and I think partially in your ARP.  You should remove the computers from the domain, flush the arp, make sure the server is plugged into the NIC that it is supposed to be on, and start over.

The DNS setting on the server is fine at 127.0.0.1, that is the local loop back address, internal to the server.

0
 
LVL 4

Expert Comment

by:Nice-Ghaza
ID: 33656150
please see the ip setting
ip-setting.JPG
0
 

Author Comment

by:mel11755
ID: 33657798
The local Area Connection 1 is the one that has a cable and the one that I configured with 192.168.0.5 with a subnet of 255.255.255.0 and  a gateway of 192.168.0.1 with a DNS of 127.0.0.1

 Local Area Connection 2 is not cabled but is showing the ip address of 192.168.0.2. and a subnet of 255.255.255.0 with no gateway and DNS of 127.0.0.1

I cannot ping 192.168.0.5 but I can ping 192.168.0.2 (the uncabled nic) .  If I configure the XP desktops with a dns of 192.168.0.2,  I am able to join the XP desktops to the domain. Once I removed that DNS from their settings I can no longer access the domain.

DNS shows both IP addresses in it's table.
.
0
 

Author Comment

by:mel11755
ID: 33657802
What would prevent the XP desktops from seeing the 192.168.0.5 IP address (hard coded IP).  They are on the same subnet, using the same gateway and same DNS settings.
0
 
LVL 10

Expert Comment

by:ddiazp
ID: 33657834
Could it be as simple as LAN Connection 1 is actually LAN Connection 2?

The DNS Servers should have DNS Server: 127.0.0.1 (as you have it already), the clients should have 192.168.0.2 (as you mentioned you can ping it).

Are additional IP addresses assigned to these NICs?:

Right click LAN Connection Icon
Properties
Advanced
IP Addresses

Make sure there are no other workstations with 192.168.0.5 on the network
0
 
LVL 10

Expert Comment

by:ddiazp
ID: 33657841
Also, look at teh arp table on the XP machines (arp -a from command line) and make sure 192.168.0.5 is mapped to the proper mac address. If in doubt, just type the command  `arp -d *`
0
 
LVL 10

Expert Comment

by:ddiazp
ID: 33657850
Again, also; do these servers connect to the router directly? (Router switchports) or to a network switch? Try restarting the switch or clearing the cam table on the switch as it might be sending packets to wrong mac address.
0
 

Author Comment

by:mel11755
ID: 33658031
ARP Table on XP Desktop show correct MAC address for 192.168.0.5 but shows it as dynamic and should be static
I had to add the XP Desktops to the arp tables but they show up as static and they are actually dynamic. This is on both XP Desktops. They still cannot ping each other but I can RDP to any of them from any of the machines.

I also checked the router and the MAC address is the same there.

Dont have access to the switch to check the table there.

0
 
LVL 24

Expert Comment

by:rfc1180
ID: 33658302
>ARP Table on XP Desktop show correct MAC address for 192.168.0.5 but shows it as dynamic and should be static I had to add the XP Desktops to the arp tables but they show up as static and they are actually dynamic.

You should never have to add in static entries; your statement is a bit confusing though:
"hows it as dynamic and should be static"
So you are saying that 192.168.0.5 has a MAC address and the MAC address is that of the DC? If so, sounds like you have a filtering issue somewhere (Firewall in the path, possibly enabled on the server?).


>I also checked the router and the MAC address is the same there.
default gateway has nothing to do with local communications


Billy
0
What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

 
LVL 10

Expert Comment

by:ddiazp
ID: 33658428
If you can RDP but ping fails it's probaly the native windows firewall.. Even if it's turned off, in some patches/service packs the firewall will stop pings even if firewall's off.


Open the firewall, Go to Advanced, click the Settings button for ICMP and check 'allow incoming requests'.

This should clear the ping misunderstanding - Is the native windows firewall on on the windows server?
0
 
LVL 9

Expert Comment

by:rfportilla
ID: 33689125
The reason why the arp shows it as dynamic is that you did not have to manually add the arp entry.  THe arp service pulled it on its own, automatically=dynamic.  I have some questions to try to narrow this down:

As rfc1180 is suggesting, did you check the mac address in the arp table against the mac address on the 192.168.0.5 nic?  

Is your DNS server set up to run on all IP addresses on the server?

What device is handling DHCP?  Router or server, or both?  

According to DHCP, what is your DNS's IP address?  

Why do you have 192.168.0.2 set up on another nic???  Is there a reason for this?

Why is 192.168.0.2 in your DNS?  You should remove it from DNS if it is not active.

After getting this straightened out, you should delete the arp and dns caches on the XP computers.
  arp -d *
  ipconfig -flusdns
0
 

Author Comment

by:mel11755
ID: 33693800
rfportilla.

I have confirmed the MAC address on the arp table and it is correct.

DHCP is setup on the router.
DNS is setup for server which is 192.168.0.5
The IP address of 192.168.0.2 is not one that we configured. And that is what perplexes us. We tried removing it and when we did the XP boxes could no longer access the DC ( 192.168.0.5 ) This IP address shows up on the second NIC but we do not have a cable plugged into it. It is enabled but no cable attached.
0
 
LVL 10

Expert Comment

by:ddiazp
ID: 33694326
Perhaps the second NIC is  just the first NIC.

Are there secondary IP addresses configured on the primary NIC?
0
 
LVL 9

Expert Comment

by:rfportilla
ID: 33698343
This may not be the answer you want to hear, but the best, easiest solution might be to just use the .2 address and be done with it.  You already have many computers using this address already.  I have no idea what all of the ramifications are, but once you set the address for a domain server it is not supposed to be changed.  Whether or not it was intentional, the address seems to be the .2 address.  It is probably easier to just use that than try to change things.  JMHO.
0
 
LVL 9

Expert Comment

by:rfportilla
ID: 33698348
Even though the other nic is not connected, it is on the same subnet and as the 1st nic and so the computer will reply to it.  That is a Microsoft thing.
0
 

Author Comment

by:mel11755
ID: 33710126
Ok. Correction. Both NICS have a CAT5 cable. I did not see my partner connect both of them. NIC1 is 192.168.0.5. This is the one that we configured with the IP address. NIC 2 is 192.168.0.2. After looking at it's configuration it does not have a gateway listed.
NIC1
IP Address92.168.0.5
Subnet Address 255.255.255.0.
Gateway Address 192.168.0.1
DNS 127.0.0.1
DNS 192.168.0.5
DNS 192.168.0.2

NIC 2
IP Address 192.168.0.2
Subnet  255.255.255.0
Gateway
DNS 127.0.0.1
DNS 192.168.0.5
DNS 192.168.0.2

Another interesting thing is when you check the configuration of each nic by clicking on its properties and selecting the TCP/IP setting It will not allow me to view the settings for 192.168.0.2 But I can on the 192.168.0.5 settings.  
0
 
LVL 10

Expert Comment

by:ddiazp
ID: 33710236
under network connections, you can only have the properties of a NIC opened at a time. If you opened the settings for .0.5 and then tried to open the settings for .0.2 it will throw you an error saying it can't open the new window.

You need to close the .0.5 properties window and then open the .0.2 properties.


Going back to your original problem; can you ping the PCs that cannot join the domain from the DC?

On your DNS server, what does the SRV record point to?

On the server, just leave 127.0.0.1 as DNS Server
0
 

Author Comment

by:mel11755
ID: 33712158
ddiazp...  Ok I will check the SRV. This two nic thing is crazy. So now my RDP connection is not working. I have the external IP address NAT to 192.168.0.5  With this new nic in the pic I can't RDP into my server. So i will have to go into the office and change the NAT to  192.168.0.2 . Then I will also check the SRV Records. But if I remember both NIC cards are listed to the DC

And No i cannot ping the PC's from the DC.   Here is more. I can RCP from the PC's to 192.168.0.2 but not to 192.168.0.5.  In the network connections, I can see the domain but I can't access it.  

I was finally able to add the PC's to the domain but that is about it. Can't access anything.   All I am able to do is RDP to the PC's.
0
 
LVL 9

Expert Comment

by:rfportilla
ID: 33717593
Bottom line, I really think you need to lose the 2 nic set up.  It is causing issues.  ;-)
0
 

Author Comment

by:mel11755
ID: 33795432
I will remove the second nic this weekend and let you know how it goes.
0
 
LVL 9

Expert Comment

by:rfportilla
ID: 33800702
ahh, you don't have to physically remove it, but I would definitely disable it or disconnect it and reconfigure with just one IP address.  It would be nice to keep for a failover.  

0
 

Author Comment

by:mel11755
ID: 33909910
I have not had  a chance to disable this nic as yet. I am hoping to schedule this weekend.
0
 

Accepted Solution

by:
mel11755 earned 0 total points
ID: 34029714
I ended up calling Microsoft Tech Support. Spent 4 hours online with them. Made so many changes on both machines
0
 
LVL 9

Expert Comment

by:rfportilla
ID: 34030345
What is the final configuration then?
0
 

Author Comment

by:mel11755
ID: 34030354
Unfortunately the tech took control of the mouse and made changes in the registry, group policy and I could not keep track of what he did. He would make a change undo it and then make more changes so I can't say for sure what was the fix.
0
 

Author Closing Comment

by:mel11755
ID: 34067946
Paid for support as none of the options here resolved my problem.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Suggested Solutions

This is an article about my experiences with remote access to my clients (so that I may serve them) and eventually to my home office system via Radmin Remote Control. I have been using remote access for over 10 years and have been improving my metho…
If your business is like most, chances are you still need to maintain a fax infrastructure for your staff. It’s hard to believe that a communication technology that was thriving in the mid-80s could still be an essential part of your team’s modern I…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now