Problems with Joining Domain from desktop station to Domain contro

active directory >> Problems with Joining Domain from desktop station to Domain contro

Hi,

I am having big trouble to join most of the user's PC to their domain
controller. I have just join this new company and found out that they have
one domain controller: "thedomainname.local". However, most of the users are
logging in to their own PC accounts (means local PC account) and connected to
"WORKGROUP" network instead of the Domain controller and some of them are
able to access the file server located at the domain controller.

Now, when most of them now are having difficulty in accessing the file
server, I tried to change their computer to join the domain controller
"thedomainname.local". However, when i click on join the domain, it is giving
me error saying the either the Domain name is not correct or is not
contactable (it might be issue with the DNS server). I checked on the server
the domain controller is working fine.

Another thing is that when I put on restrictions on the Everyone group on
not to access certain folder on the file server, it does not work. I assume
it is because they are not connecting to the Domain at the moment. But what
makes me really wonder is how they are able t connect to the file server when
they are connecting to the WORKGROUP network. Sadly, the previous IT guy had
left 3 months ago and there is no where to contact this guy.

Please help as I am in a lost on how to fixed this Domain and network issue.
Any help will be greatly appreciated.

Regards,
Jannarko

Windows OS135

active directory >> Problems with Joining Domain from desktop station to Domain contro This sounds like a DNS issue. What happens if you try and join the domain
using the NETBIOS name?

Is the domain controller running DNS? Are the clients using it as a DNS
server?

> Hi,
>
> I am having big trouble to join most of the user's PC to their domain
> controller. I have just join this new company and found out that they have
> one domain controller: "thedomainname.local". However, most of the users
> are
> logging in to their own PC accounts (means local PC account) and connected
> to
> "WORKGROUP" network instead of the Domain controller and some of them are
> able to access the file server located at the domain controller.
>
> Now, when most of them now are having difficulty in accessing the file
> server, I tried to change their computer to join the domain controller
> "thedomainname.local". However, when i click on join the domain, it is
> giving
> me error saying the either the Domain name is not correct or is not
> contactable (it might be issue with the DNS server). I checked on the
> server
> the domain controller is working fine.
>
> Another thing is that when I put on restrictions on the Everyone group on
> not to access certain folder on the file server, it does not work. I
> assume
> it is because they are not connecting to the Domain at the moment. But
> what
> makes me really wonder is how they are able t connect to the file server
> when
> they are connecting to the WORKGROUP network. Sadly, the previous IT guy
> had
> left 3 months ago and there is no where to contact this guy.
>
> Please help as I am in a lost on how to fixed this Domain and network
> issue.
> Any help will be greatly appreciated.
>
> Regards,
> Jannarko

active directory >> Problems with Joining Domain from desktop station to Domain contro Hi Daniel,

I just try to do some testing on the DNS server, i go to the command line
prompt and type in "nslookup". After that i typed in "server IP address" (the
DNS IP address), it returns me the default server name:
server.domainname.local and the DNS IP address.

I then proceed to type in "set querytype=any" and put in command "ls -d
domain name" (name of our forward lookup zone in the DNS server).
The command returns an unexpected error of:
"DNS server refused to transfer the zone laserresearch.local to your
computer. Please check zone transfer security setting for the domain".

Afterwards, I tried to reset one user account password from the server
domain. I went to the user pc and try to log off and log on again by using
the new password i resetted from domain. To my surprise, the computer does
not accept the new password.
Instead, it accepts only the old password. I verified that the account is
log into Domain and under the computer name is also joined to the Domain.
Does this means that the Domain is not running?

Regards,
Jannarko

> This sounds like a DNS issue. What happens if you try and join the domain
> using the NETBIOS name?
>
> Is the domain controller running DNS? Are the clients using it as a DNS
> server?
>

> > Hi,
> >
> > I am having big trouble to join most of the user's PC to their domain
> > controller. I have just join this new company and found out that they have
> > one domain controller: "thedomainname.local". However, most of the users
> > are
> > logging in to their own PC accounts (means local PC account) and connected
> > to
> > "WORKGROUP" network instead of the Domain controller and some of them are
> > able to access the file server located at the domain controller.
> >
> > Now, when most of them now are having difficulty in accessing the file
> > server, I tried to change their computer to join the domain controller
> > "thedomainname.local". However, when i click on join the domain, it is
> > giving
> > me error saying the either the Domain name is not correct or is not
> > contactable (it might be issue with the DNS server). I checked on the
> > server
> > the domain controller is working fine.
> >
> > Another thing is that when I put on restrictions on the Everyone group on
> > not to access certain folder on the file server, it does not work. I
> > assume
> > it is because they are not connecting to the Domain at the moment. But
> > what
> > makes me really wonder is how they are able t connect to the file server
> > when
> > they are connecting to the WORKGROUP network. Sadly, the previous IT guy
> > had
> > left 3 months ago and there is no where to contact this guy.
> >
> > Please help as I am in a lost on how to fixed this Domain and network
> > issue.
> > Any help will be greatly appreciated.
> >
> > Regards,
> > Jannarko
>

active directory >> Problems with Joining Domain from desktop station to Domain contro

> Hi Daniel,
>
> I just try to do some testing on the DNS server, i go to the command line
> prompt and type in "nslookup". After that i typed in "server IP address" (the
> DNS IP address), it returns me the default server name:
> server.domainname.local and the DNS IP address.
>
> I then proceed to type in "set querytype=any" and put in command "ls -d
> domain name" (name of our forward lookup zone in the DNS server).
> The command returns an unexpected error of:
> "DNS server refused to transfer the zone laserresearch.local to your
> computer. Please check zone transfer security setting for the domain".
>
> Afterwards, I tried to reset one user account password from the server
> domain. I went to the user pc and try to log off and log on again by using
> the new password i resetted from domain. To my surprise, the computer does
> not accept the new password.
> Instead, it accepts only the old password. I verified that the account is
> log into Domain and under the computer name is also joined to the Domain.
> Does this means that the Domain is not running?
>
> Regards,
> Jannarko
>
>
>

> > This sounds like a DNS issue. What happens if you try and join the domain
> > using the NETBIOS name?
>
> > Is the domain controller running DNS? Are the clients using it as a DNS
> > server?
>

> > > Hi,
>
> > > I am having big trouble to join most of the user's PC to their domain
> > > controller. I have just join this new company and found out that they have
> > > one domain controller: "thedomainname.local". However, most of the users
> > > are
> > > logging in to their own PC accounts (means local PC account) and connected
> > > to
> > > "WORKGROUP" network instead of the Domain controller and some of them are
> > > able to access the file server located at the domain controller.
>
> > > Now, when most of them now are having difficulty in accessing the file
> > > server, I tried to change their computer to join the domain controller
> > > "thedomainname.local". However, when i click on join the domain, it is
> > > giving
> > > me error saying the either the Domain name is not correct or is not
> > > contactable (it might be issue with the DNS server). I checked on the
> > > server
> > > the domain controller is working fine.
>
> > > Another thing is that when I put on restrictions on the Everyone group on
> > > not to access certain folder on the file server, it does not work. I
> > > assume
> > > it is because they are not connecting to the Domain at the moment. But
> > > what
> > > makes me really wonder is how they are able t connect to the file server
> > > when
> > > they are connecting to the WORKGROUP network. Sadly, the previous IT guy
> > > had
> > > left 3 months ago and there is no where to contact this guy.
>
> > > Please help as I am in a lost on how to fixed this Domain and network
> > > issue.
> > > Any help will be greatly appreciated.
>
> > > Regards,
> > > Jannarko- Hide quoted text -
>
> - Show quoted text -

Did you verify DNS is setup correctly? I would begin by running
dcdiag /e /v from a command prompt on the domain controller.

active directory >> Problems with Joining Domain from desktop station to Domain contro Hi ctvader,

Currently I use net use command line to force the PC to loginto Domain and
map the drive to the file server. I created a bat file and put inside the
registry for it to run everytime the PC startup. I still do not managed to
find out what is the actual problem here. The DNS is running but I am not
sure whether it is setup correctly as I am new at the company so I still have
to troubleshoot more.

Regards,
Jannarko

> > Hi Daniel,
> >
> > I just try to do some testing on the DNS server, i go to the command line
> > prompt and type in "nslookup". After that i typed in "server IP address" (the
> > DNS IP address), it returns me the default server name:
> > server.domainname.local and the DNS IP address.
> >
> > I then proceed to type in "set querytype=any" and put in command "ls -d
> > domain name" (name of our forward lookup zone in the DNS server).
> > The command returns an unexpected error of:
> > "DNS server refused to transfer the zone laserresearch.local to your
> > computer. Please check zone transfer security setting for the domain".
> >
> > Afterwards, I tried to reset one user account password from the server
> > domain. I went to the user pc and try to log off and log on again by using
> > the new password i resetted from domain. To my surprise, the computer does
> > not accept the new password.
> > Instead, it accepts only the old password. I verified that the account is
> > log into Domain and under the computer name is also joined to the Domain.
> > Does this means that the Domain is not running?
> >
> > Regards,
> > Jannarko
> >
> >
> >

> > > This sounds like a DNS issue. What happens if you try and join the domain
> > > using the NETBIOS name?
> >
> > > Is the domain controller running DNS? Are the clients using it as a DNS
> > > server?
> >

> > > > Hi,
> >
> > > > I am having big trouble to join most of the user's PC to their domain
> > > > controller. I have just join this new company and found out that they have
> > > > one domain controller: "thedomainname.local". However, most of the users
> > > > are
> > > > logging in to their own PC accounts (means local PC account) and connected
> > > > to
> > > > "WORKGROUP" network instead of the Domain controller and some of them are
> > > > able to access the file server located at the domain controller.
> >
> > > > Now, when most of them now are having difficulty in accessing the file
> > > > server, I tried to change their computer to join the domain controller
> > > > "thedomainname.local". However, when i click on join the domain, it is
> > > > giving
> > > > me error saying the either the Domain name is not correct or is not
> > > > contactable (it might be issue with the DNS server). I checked on the
> > > > server
> > > > the domain controller is working fine.
> >
> > > > Another thing is that when I put on restrictions on the Everyone group on
> > > > not to access certain folder on the file server, it does not work. I
> > > > assume
> > > > it is because they are not connecting to the Domain at the moment. But
> > > > what
> > > > makes me really wonder is how they are able t connect to the file server
> > > > when
> > > > they are connecting to the WORKGROUP network. Sadly, the previous IT guy
> > > > had
> > > > left 3 months ago and there is no where to contact this guy.
> >
> > > > Please help as I am in a lost on how to fixed this Domain and network
> > > > issue.
> > > > Any help will be greatly appreciated.
> >
> > > > Regards,
> > > > Jannarko- Hide quoted text -
> >
> > - Show quoted text -
>
> Did you verify DNS is setup correctly? I would begin by running
> dcdiag /e /v from a command prompt on the domain controller.
>

active directory >> Problems with Joining Domain from desktop station to Domain contro

> Hi ctvader,
>
> Currently I use net use command line to force the PC to loginto Domain and
> map the drive to the file server. I created a bat file and put inside the
> registry for it to run everytime the PC startup. I still do not managed to
> find out what is the actual problem here. The DNS is running but I am not
> sure whether it is setup correctly as I am new at the company so I still have
> to troubleshoot more.
>
> Regards,
> Jannarko
>
>
>

> > > Hi Daniel,
>
> > > I just try to do some testing on the DNS server, i go to the command line
> > > prompt and type in "nslookup". After that i typed in "server IP address" (the
> > > DNS IP address), it returns me the default server name:
> > > server.domainname.local and the DNS IP address.
>
> > > I then proceed to type in "set querytype=any" and put in command "ls -d
> > > domain name" (name of our forward lookup zone in the DNS server).
> > > The command returns an unexpected error of:
> > > "DNS server refused to transfer the zone laserresearch.local to your
> > > computer. Please check zone transfer security setting for the domain".
>
> > > Afterwards, I tried to reset one user account password from the server
> > > domain. I went to the user pc and try to log off and log on again by using
> > > the new password i resetted from domain. To my surprise, the computer does
> > > not accept the new password.
> > > Instead, it accepts only the old password. I verified that the account is
> > > log into Domain and under the computer name is also joined to the Domain.
> > > Does this means that the Domain is not running?
>
> > > Regards,
> > > Jannarko
>

> > > > This sounds like a DNS issue. What happens if you try and join the domain
> > > > using the NETBIOS name?
>
> > > > Is the domain controller running DNS? Are the clients using it as a DNS
> > > > server?
>

> > > > > Hi,
>
> > > > > I am having big trouble to join most of the user's PC to their domain
> > > > > controller. I have just join this new company and found out that they have
> > > > > one domain controller: "thedomainname.local". However, most of the users
> > > > > are
> > > > > logging in to their own PC accounts (means local PC account) and connected
> > > > > to
> > > > > "WORKGROUP" network instead of the Domain controller and some of them are
> > > > > able to access the file server located at the domain controller.
>
> > > > > Now, when most of them now are having difficulty in accessing the file
> > > > > server, I tried to change their computer to join the domain controller
> > > > > "thedomainname.local". However, when i click on join the domain, it is
> > > > > giving
> > > > > me error saying the either the Domain name is not correct or is not
> > > > > contactable (it might be issue with the DNS server). I checked on the
> > > > > server
> > > > > the domain controller is working fine.
>
> > > > > Another thing is that when I put on restrictions on the Everyone group on
> > > > > not to access certain folder on the file server, it does not work. I
> > > > > assume
> > > > > it is because they are not connecting to the Domain at the moment. But
> > > > > what
> > > > > makes me really wonder is how they are able t connect to the file server
> > > > > when
> > > > > they are connecting to the WORKGROUP network. Sadly, the previous IT guy
> > > > > had
> > > > > left 3 months ago and there is no where to contact this guy.
>
> > > > > Please help as I am in a lost on how to fixed this Domain and network
> > > > > issue.
> > > > > Any help will be greatly appreciated.
>
> > > > > Regards,
> > > > > Jannarko- Hide quoted text -
>
> > > - Show quoted text -
>
> > Did you verify DNS is setup correctly? I would begin by running
> > dcdiag /e /v from a command prompt on the domain controller.- Hide quoted text -
>
> - Show quoted text -

In order to the use the ls -d command, you need to add your ip address
into the xfer list or allow anyone to xfer the zone.