B
Benjimonster
Hello,
odd problem here.. I can ping the local domain name before I join it, then when I join I cannot ping it any longer. Nslookup domainname.local resolves and shows me the IP addresses of the 2 domain controllers. It says server unknown, could that the issue? I read that is not abnormal. It returns the IP of the domain controller under address and then lists the secondary one next as well as an IPV6 address. Could IPV6 be the problem?
C:\nslookup domainname.local
server:unknown
address: 192.168.1.5 (dc1)
Name: domainname.local
Addresses: [IPV6 address] (correct one)
192.168.1.5 (dc1)
192.168.1.6 (dc2)
I tried replacing the vNIC with a new one an no luck. The server has an onboard NIC with two ports that I have teamed in the host OS and I presented the team to the Vswitch.
I've tried adding domainname.local 192.168.1.5 (dc1) to the local host file as well.
I read a thread on spiceworks saying somebody resolved this problem by replacing the physical NIC in the machine. There has to be another fix for this, or should I just save the headache and get a new NIC? I can't believe I'd have to buy new hardware to fix something like this. I would try to rebuild the VM from scratch first.
I have the 2 domain controllers, the original DC is the only IP in my DNS. I just created the 2nd domain controller today. The network is very small, could there be a replication issue? All the DNS and AD are replicated...
I can ping the IP and name of both servers and everything on the network except the local domain. All other computers on the network can ping the local domain name. This is causing my GPO to not update and it's causing me to not have the right permission to install SQL, so it is a game breaker. I could probably install SQL as a local admin but I don't feel comfortable making this a production SQL server with this issue. I tried adding another vNIC so I had two, unjoining from the domain, renaming the machine, then deleting the older vNIC, and rejoining the domain in that order, still no luck.
Should I just make a new VM at this point? I have time. This same VM has installed the same windows defender update like 5 times today. Not to mention the apparently normal 5 hours it took to get updates installed.
Sorry to write a book, any help or advice is appreciated.
Continue reading...
odd problem here.. I can ping the local domain name before I join it, then when I join I cannot ping it any longer. Nslookup domainname.local resolves and shows me the IP addresses of the 2 domain controllers. It says server unknown, could that the issue? I read that is not abnormal. It returns the IP of the domain controller under address and then lists the secondary one next as well as an IPV6 address. Could IPV6 be the problem?
C:\nslookup domainname.local
server:unknown
address: 192.168.1.5 (dc1)
Name: domainname.local
Addresses: [IPV6 address] (correct one)
192.168.1.5 (dc1)
192.168.1.6 (dc2)
I tried replacing the vNIC with a new one an no luck. The server has an onboard NIC with two ports that I have teamed in the host OS and I presented the team to the Vswitch.
I've tried adding domainname.local 192.168.1.5 (dc1) to the local host file as well.
I read a thread on spiceworks saying somebody resolved this problem by replacing the physical NIC in the machine. There has to be another fix for this, or should I just save the headache and get a new NIC? I can't believe I'd have to buy new hardware to fix something like this. I would try to rebuild the VM from scratch first.
I have the 2 domain controllers, the original DC is the only IP in my DNS. I just created the 2nd domain controller today. The network is very small, could there be a replication issue? All the DNS and AD are replicated...
I can ping the IP and name of both servers and everything on the network except the local domain. All other computers on the network can ping the local domain name. This is causing my GPO to not update and it's causing me to not have the right permission to install SQL, so it is a game breaker. I could probably install SQL as a local admin but I don't feel comfortable making this a production SQL server with this issue. I tried adding another vNIC so I had two, unjoining from the domain, renaming the machine, then deleting the older vNIC, and rejoining the domain in that order, still no luck.
Should I just make a new VM at this point? I have time. This same VM has installed the same windows defender update like 5 times today. Not to mention the apparently normal 5 hours it took to get updates installed.
Sorry to write a book, any help or advice is appreciated.
Continue reading...