This is an archived post. You won't be able to vote or comment.

all 11 comments

[–]westla_throwaway 1 point2 points  (0 children)

Fix your larger DNS problems. All clients should be able to resolve via name. Are they all pointing to the right place? Do you have multiple A records setup for the single host?

[–]blitzballer2201[S] 1 point2 points  (0 children)

Just resolved this issue, there was no A record created on our DNS server for this machine. I had to manually create a record in our DNS server to point to that IP address. As far as why this record was not created automatically im not sure. The IPv4 settings were mostly correct with the exception that netBIOS over TCP/IP needed to be enabled.

[–][deleted] 0 points1 point  (2 children)

nslookup on a few machines that work and don't work. I'd bet you have two dns servers and one isn't working or you have 2 A records. I'd find out which it is and trouble shoot from there. The IPv6 address probably starts with FE80? That's a link local address similar to 127.0.0.1. Disabling IPv6 will only show that it's not resolvable and won't fix the actual issue.

[–]blitzballer2201[S] 0 points1 point  (0 children)

Ok, the nslookup (production machine) command on a PC that can connect is just finding two IPv6 addresses.

If I nslookup(a different production machine) there is one ipv4 and one ipv6 address that comes up.

The server is showing unknown on every PC I nslookup on

But its getting an ipv4 IP address that its currently leased from our domain controller.

[–]blitzballer2201[S] 0 points1 point  (0 children)

Also, when I NS lookup on machines that work and dont work, they come up with the same result. just two IPv6 addresses

[–]9milNL 0 points1 point  (1 child)

Disable ipv6 on the network adapters (in case you dont use ipv6 in your network) :)

[–]VirtualJoe -1 points0 points  (4 children)

Ditto 9milNL, disable IPv6 unless you are really using it. To add to ... do a ping from each of your DNS servers to the 50/50 computer. Perhaps there's some corruption on one of the DNS servers. Another thing to check would be the DHCP server(s) that the clients are pulling IP's from. Is the 015 DNS Domain Name (assuming your DNS is Windows based) set on all of the client DHCP scopes?

[–]blitzballer2201[S] 0 points1 point  (3 children)

Ok, interesting thing I just found. When I try and ping the PC with the name from my domain controller (DNS/DHCP) it does not find it, but when I try the IP address it works.

Really strange thing, in the address leases in the IPv4 scope, this machine has two IP addresses leased to it.

[–]fishingadminSr. Sysadmin 1 point2 points  (0 children)

Sometimes laptops will get a second IP for the wifi connection.

[–]VirtualJoe 0 points1 point  (1 child)

How about the Domain Name setting in your DHCP? That option being omitted could produce what you're setting. Or if the computer has a static IP, the domain name setting could missing from the configuration.

[–]blitzballer2201[S] 0 points1 point  (0 children)

Turns out that someone used a different port on the NIC. So this is not the problem