F5F Stay Refreshed Software Operating Systems Issues with Windows Server 2008

Issues with Windows Server 2008

Issues with Windows Server 2008

Pages (2): 1 2 Next
O
ox_
Junior Member
11
08-13-2016, 11:50 PM
#1
Attempting to join a new Windows Server 2008 machine to the network triggers this warning... The message indicates DNS resolution issues within the domain. Ensure the client is properly set up to connect to a DNS server that supports resolving names in the target domain. You’re able to access the internet from Windows 7/8/10 but not from the Server 2008 machine—this could point to configuration or network restrictions. Since you’re now connected to a Windows Server 2012 R2 DC, check firewall rules, DNS settings, and ensure the server is reachable on the internal network.
O
ox_
08-13-2016, 11:50 PM #1

Attempting to join a new Windows Server 2008 machine to the network triggers this warning... The message indicates DNS resolution issues within the domain. Ensure the client is properly set up to connect to a DNS server that supports resolving names in the target domain. You’re able to access the internet from Windows 7/8/10 but not from the Server 2008 machine—this could point to configuration or network restrictions. Since you’re now connected to a Windows Server 2012 R2 DC, check firewall rules, DNS settings, and ensure the server is reachable on the internal network.

F
flycatcher9
Junior Member
47
08-14-2016, 04:52 AM
#2
Choose between adding as a DC or as a client. Enter the IP of the 2012 R2 device into the DNS settings. When prompted, select "Use the following DNS server address." Also, configure a static IP for the server.
F
flycatcher9
08-14-2016, 04:52 AM #2

Choose between adding as a DC or as a client. Enter the IP of the 2012 R2 device into the DNS settings. When prompted, select "Use the following DNS server address." Also, configure a static IP for the server.

X
xanderzone317
Posting Freak
957
08-14-2016, 01:40 PM
#3
*
X
xanderzone317
08-14-2016, 01:40 PM #3

*

_
_DamTDM_
Member
120
08-14-2016, 06:16 PM
#4
Joining as a client. All previous attempts still failing. If you're comfortable with this process and no one responds, I could message you to request assistance and share some screenshots of your current configuration.
_
_DamTDM_
08-14-2016, 06:16 PM #4

Joining as a client. All previous attempts still failing. If you're comfortable with this process and no one responds, I could message you to request assistance and share some screenshots of your current configuration.

R
Redstoner137
Posting Freak
811
08-14-2016, 06:29 PM
#5
Additionally, the domain name matters—use the exact case. Also, test the DC server connection.
R
Redstoner137
08-14-2016, 06:29 PM #5

Additionally, the domain name matters—use the exact case. Also, test the DC server connection.

H
hahaha100
Member
172
08-14-2016, 10:07 PM
#6
I've tested various cases but didn't consider sending a ping! Smart.
H
hahaha100
08-14-2016, 10:07 PM #6

I've tested various cases but didn't consider sending a ping! Smart.

C
CH_SwissPower
Junior Member
41
08-14-2016, 11:02 PM
#7
I suspect there might be an issue with your DNS server. I checked the information online.
C
CH_SwissPower
08-14-2016, 11:02 PM #7

I suspect there might be an issue with your DNS server. I checked the information online.

L
lulugdb
Member
174
08-15-2016, 05:00 AM
#8
Thanks a lot!
L
lulugdb
08-15-2016, 05:00 AM #8

Thanks a lot!

L
lukeswindworld
Junior Member
3
08-27-2016, 04:33 AM
#9
Have you confirmed the DNS role is set up on the DC? Visit the server and verify its presence.
L
lukeswindworld
08-27-2016, 04:33 AM #9

Have you confirmed the DNS role is set up on the DC? Visit the server and verify its presence.

X
xImFizzy
Member
213
08-27-2016, 05:49 AM
#10
The issue was clear—I was glad to assist.
X
xImFizzy
08-27-2016, 05:49 AM #10

The issue was clear—I was glad to assist.

Pages (2): 1 2 Next