:, I am having a lot of trouble getting a server up and then having people be able to join it. I see that computer that I’m having issues with and it has the wrong IP address along with a few other servers in the company. When I do a ipconfig /displydns from another computer on the network. In DHCP I see the correct IP address for machine1 and machine2. When I ping machine1 from any computer on our network I get X.X.X.86 which is the IP Address of machine2. What I mean when I say ping back with the wrong address when I ping machine1 it gives me the IP address of another computer. Yes, when I ping the fully qualified domain name I get the wrong IP address. The only thing the same on all the machines is the image, but I have other machines that when I ping them give me the correct IP address. Could the router have cached that IP with that computer name? This has been going on for about 3 months now I would have thought it would have flushed out. The gateway is pointed to our Cisco Router - Sorry my router knowledge is not that good. Use nslookup, nbtstat (nbtstat -c displays the netbios cache) and ipconfig /displaydns utility to check what happens on your machinesĬhecked the hosts and lnhosts.sam and those all look good. Now, let it be clear that in case a ping command seems to be reaching a wrong IP address, the problem is within the host that SENT the ping command, not with the host that you thought should have answered. Normally, if you use an fqdn name (), DNS should be used first. Now, it may be that the name resolution is not done with DNS but with WINS or even with broadcast. You will see which DNS answered, and with what IP address. On the machine that you ran a "ping" that did not reach the correct ip address, run an nslookup command When it knows the IP address, it sends the "ping message" (ICMP ECHO REQUEST) to tje destination machine. The host runs the usual process to resolve the destination machine name into an IP address. I don't understand what you mean by "ping back with the wrong address".Ī ping is ISSUED by a certain host. We don’t have any admin access to Domain B. I guess my questions is could the problem that we are seeing be caused by us not pushing down network configurations for Domain B? If we configured our Domain and DNS to reflect Domain B instead of Domain A would that fix the problem with DNS that we are seeing? Notes: The only reason we have Domain A is because the bigger company will not let us move our servers over to Domain B. I do see in the Reverse Lookup Zone all the computers on Domain B and they all seem to have a PTR record. When I look in the Forward Lookup Zone on Domain A under Domain A’s domain I don’t see any of our computers that are on Domain B even though I’m pushing down DNS setting from Domain A. The only network configurations we have from Domain B is a few DNS suffixes that get pushed down via Group Policy. All the network configuration (DHCP, Gateway, Domain, and DNS) all come from Domain A. So right now all our computers are on Domain B. For this example I will use Domain A for our old small domain and Domain B for the company that bought us out domain. We were a small company with our own domain we got bought out by a bigger company with its own domain. I have checked the IP address on the DHCP server and it is correct with what is on the machine. I have done an ipconfig /flushdns on them, but still they will not ping with the right address. I have a few machines that when I ping them they ping back with the wrong IP address.
0 Comments
Leave a Reply. |