F5F Stay Refreshed Power Users Networks Configuration problems with Active Directory

Configuration problems with Active Directory

Configuration problems with Active Directory

Pages (3): 1 2 3 Next
W
WitherKing010
Junior Member
9
06-22-2025, 07:30 PM
#1
Hello, I'm preparing a home lab with web servers and an Active Directory domain. The main challenge is that "SERVER1" isn't reaching the domain, so it can't join or be promoted. I've drawn a network diagram showing the setup, but the issue remains unclear. Any suggestions would be appreciated.
W
WitherKing010
06-22-2025, 07:30 PM #1

Hello, I'm preparing a home lab with web servers and an Active Directory domain. The main challenge is that "SERVER1" isn't reaching the domain, so it can't join or be promoted. I've drawn a network diagram showing the setup, but the issue remains unclear. Any suggestions would be appreciated.

L
Light_S
Junior Member
14
07-08-2025, 04:39 AM
#2
Consider adjusting DNS manually or designating the DCS as the DNS server. This appears to be a DNS-related problem.
L
Light_S
07-08-2025, 04:39 AM #2

Consider adjusting DNS manually or designating the DCS as the DNS server. This appears to be a DNS-related problem.

H
HorseyHay
Member
208
07-08-2025, 10:56 AM
#3
Performed configuration on the client device. Configured 10.230.0.240 as the sole DNS server and cleared the DNS cache. Domain remains unreachable via ping.
H
HorseyHay
07-08-2025, 10:56 AM #3

Performed configuration on the client device. Configured 10.230.0.240 as the sole DNS server and cleared the DNS cache. Domain remains unreachable via ping.

S
Sadikhadzovic
Junior Member
33
07-08-2025, 02:56 PM
#4
Consider disabling the firewall on the DC temporarily to test if it resolves the issue. Review its rules to ensure they won't block necessary traffic. Also, verify whether all network clients receive IP addresses via DHCP or if they're assigned manually.
S
Sadikhadzovic
07-08-2025, 02:56 PM #4

Consider disabling the firewall on the DC temporarily to test if it resolves the issue. Review its rules to ensure they won't block necessary traffic. Also, verify whether all network clients receive IP addresses via DHCP or if they're assigned manually.

H
hrgriff
Senior Member
573
07-08-2025, 03:31 PM
#5
It didn't resolve as expected.
H
hrgriff
07-08-2025, 03:31 PM #5

It didn't resolve as expected.

K
KillSw1tch4367
Junior Member
1
07-08-2025, 04:23 PM
#6
K
KillSw1tch4367
07-08-2025, 04:23 PM #6

U
UltiPengz
Member
143
07-10-2025, 05:24 AM
#7
I can send a message to the DC. I changed its name to DC1, and when I type "ping dc1" it responds. If I use "ping dc1.domain.com" (like an example), it doesn<|pad|>, doesn't reply.
U
UltiPengz
07-10-2025, 05:24 AM #7

I can send a message to the DC. I changed its name to DC1, and when I type "ping dc1" it responds. If I use "ping dc1.domain.com" (like an example), it doesn<|pad|>, doesn't reply.

D
dragon_gamer44
Junior Member
2
07-22-2025, 07:49 AM
#8
It seems the problem lies with DNS. Verify the DNS server on DC; it might be assigning wrong IP addresses to these domain names.
D
dragon_gamer44
07-22-2025, 07:49 AM #8

It seems the problem lies with DNS. Verify the DNS server on DC; it might be assigning wrong IP addresses to these domain names.

K
kaaskotskikker
Posting Freak
795
08-08-2025, 02:48 AM
#9
The DNS layout on DC1 appears as is. I opted for ecorp since there wasn’t a suitable name, inspired by Mr Robot.
K
kaaskotskikker
08-08-2025, 02:48 AM #9

The DNS layout on DC1 appears as is. I opted for ecorp since there wasn’t a suitable name, inspired by Mr Robot.

T
TotallyNotAlec
Junior Member
12
08-08-2025, 03:25 AM
#10
It asks about the IP address used to ping on dc1.ecorp.local.
T
TotallyNotAlec
08-08-2025, 03:25 AM #10

It asks about the IP address used to ping on dc1.ecorp.local.

Pages (3): 1 2 3 Next