F5F Stay Refreshed Power Users Networks Connection Problem with Domain

Connection Problem with Domain

Connection Problem with Domain

A
Anselhero
Senior Member
582
11-25-2016, 05:50 AM
#1
You're encountering an issue where the connection to the Active Directory server is being blocked by the Windows 10 Education VM. The server acknowledges the domain exists but rejects the connection attempt after prompting for credentials. This suggests a permissions or configuration problem on the Education VM side. Double-check that the VM has the necessary AD permissions and that the domain join settings are correctly configured.
A
Anselhero
11-25-2016, 05:50 AM #1

You're encountering an issue where the connection to the Active Directory server is being blocked by the Windows 10 Education VM. The server acknowledges the domain exists but rejects the connection attempt after prompting for credentials. This suggests a permissions or configuration problem on the Education VM side. Double-check that the VM has the necessary AD permissions and that the domain join settings are correctly configured.

3
3Edge
Senior Member
718
11-25-2016, 07:08 PM
#2
Checking the connection method and confirming the DNS server address for the client PC.
3
3Edge
11-25-2016, 07:08 PM #2

Checking the connection method and confirming the DNS server address for the client PC.

D
DJemi
Member
150
11-25-2016, 09:22 PM
#3
Also check the firewall settings on both the w10 and the server. If you have them on default there is a big chance it won't work.
D
DJemi
11-25-2016, 09:22 PM #3

Also check the firewall settings on both the w10 and the server. If you have them on default there is a big chance it won't work.

M
Miyuumi
Senior Member
543
11-25-2016, 11:06 PM
#4
Using the router helped, but I still couldn't locate the server's IP address. I checked the standard public IP, like 192.168..., but it didn't work.
M
Miyuumi
11-25-2016, 11:06 PM #4

Using the router helped, but I still couldn't locate the server's IP address. I checked the standard public IP, like 192.168..., but it didn't work.

C
ConanGhost
Member
152
11-29-2016, 09:17 PM
#5
I didn't specify any changes to the IP address on the domain controller.
C
ConanGhost
11-29-2016, 09:17 PM #5

I didn't specify any changes to the IP address on the domain controller.

C
55
12-07-2016, 08:49 AM
#6
Turn off IPv6 since it occasionally causes problems, and I prefer to disable it completely.
C
carebearisboss
12-07-2016, 08:49 AM #6

Turn off IPv6 since it occasionally causes problems, and I prefer to disable it completely.

T
t3kk1t_pro
Junior Member
15
12-07-2016, 12:26 PM
#7
The address is 192.168.1.1, which is a private IP. It’s free to use, so you don’t need to disable IPv6. Check both server and client settings if needed.
T
t3kk1t_pro
12-07-2016, 12:26 PM #7

The address is 192.168.1.1, which is a private IP. It’s free to use, so you don’t need to disable IPv6. Check both server and client settings if needed.

W
201
12-07-2016, 06:56 PM
#8
I resolved the issue by connecting the server VM to the client VM through the computer, but the TalkTalk router was preventing access, likely encouraging you to purchase their enterprise products.
W
wilger_monster
12-07-2016, 06:56 PM #8

I resolved the issue by connecting the server VM to the client VM through the computer, but the TalkTalk router was preventing access, likely encouraging you to purchase their enterprise products.