Domain

[maxi]

I need help about this :

 

 

I am a network administrator for linkgroup.com. The network consists of a single Active Directory domain named linkgroup.com.

All network servers running on Windows Server 2008 and all client computers running the Windows Vista operating systems.

 

I installed a new server named Server22 with default settings. During installation, I set the IP configuraciju as shown:

 

Windows IP Configuration

 

Host Name. . . . . . . . . . . . : Server22

Primary Dns Suffix. . . . . . . :

Node Type. . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

 

Ethernet adapter Local Area Connection:

 

Connection-specific DNS Suffix. :

Description. . . . . . . . . . . VIA Rhine II Fast Ethernet Adapter

Physical Address. . . . . . . . . : 00-0F-CC-BC-FD-BB

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.10.100.71

Subnet Mask. . . . . . . . . . . : 255.255.0.0

Default Gateway. . . . . . . . . : 10.10.10.3

DNS Servers. . . . . . . . . . . : 10.10.100.71

 

 

 

I have done Server22 Article Workgroup's. After that I restart Server22 and I used local administrator account to log on locally.

I inserted Server22 to the domain linkgroup.com (join domain).

After that I restart Server22 and I used the Domain Administrator account to log on to the server. However, I could not do that.

 

I have to ensure that Server22 is a member of the domain. What should I do? :unsure:

 

 

 

please, if anyone can help me

[mmthomas]

It looks like you have it pointed to itself for DNS. Try pointing it at one of the domain DNS servers, unless you made it a DNS server for the domain?

[maxi]

It looks like you have it pointed to itself for DNS. Try pointing it at one of the domain DNS servers, unless you made it a DNS server for the domain?

 

 

I have to direct it towards one of the DNS domain.Tell me if I should something to change in this setting that I mentioned.

 

Not enrolled Primary Dns Suffix,

IP Address. . . . . . . . . . . . : 10.10.100.71

DNS Servers. . . . . . . . . . . : 10.10.100.71

Is the IP and DNS needs to be different? Am I on the right track?

I am new to this and trying to figure out how to solve this problem and I hope that I didn`t ask stupid.

[mmthomas]

The IP Address should be OK if it is in the same network as your other servers, but the DNS Server address should be changed on your Ethernet adapter TCP/IP properties to the address of a DNS server that is already in the domain to which you are trying to connect. If you point the DNS to itself, then the server does not know how to authenticate you when you try to log on with a domain account. By pointing to the DNS address to a DNS server that is already in the domain, when you try to login with a domain account, the server can ask the DNS server where the domain controllers are for the domain and then forward your logon request for authentication.

 

So, for example, let us say that you have a domain controller for your domain:

IP Address: 10.10.100.5

Default Gateway: 10.10.100.3

 

Let us also assume that this domain controller is running DNS for the domain. If so, its DNS setting will look like this:

DNS Server: 10.10.100.5 or it might say 127.0.0.1

 

In that case, it is OK to point to itself because the domain controller is also the primary DNS server for the domain.

 

 

If I add another server, it should look like this:

IP Address: 10.10.100.15

Default Gateway: 10.10.100.3

DNS Server: 10.10.100.5

 

Unless you are a very large company, you will probably only have one or two servers that are running DNS for your domain. All of your servers and workstations need to point to one of those DNS servers in order to work properly. The only servers that should point to themselves for DNS are the DNS servers themselves.

[maxi]

Matt, thanks for the help ... I changed the address of the DNS server and I managed to log on... :thumbsup: