Re: Sysvol issues.....
- From: .bas <bas.30u4ng@xxxxxxxxxxxxx>
- Date: Fri, 30 Nov 2007 05:23:48 +0530
Hi, Paul.
There is some revolution In my case. The main problem is accessing the
network shares created on DC1. I can’t get access to it form any
computer in my network. And because of that I have the problem to
access the SYSVOL and Netlogon default shares. That creates a whole
range of errors in my AD environment. Even if I create a new Test share
with the right permissions and security configuration I get the same
error when accessing the share by typing its path with server name.
That means that I can’t access shares using path like this
\\DC1\Testshare\ from any client/server that is a domain computer or
even form the DC1 server itself when logged on by the console. I was
trying to do that with the Administrator account. What is strange is
that I can access this shares by the server IP Address and the share
name ( \\192.168.10.1\Testshare\ ). When typing it like this the access
is granted and I can do everything that is permitted by the security to
that share. I think this is something with security configuration but I
don’t now how to fix it.
In my physical network I have two Network services 1 is an AD Directory
Service and 2 one is a workgroup. Both are in the same subnet range
192.168.10.0 /24. There is access to the computers form AD to WorkG and
vice versa. And here comes the part that I really don’t
understand:
- When list the \\DC1\ from WorgG I am prompted to login. I write the
user name and password and… I !can access the computer ( Server )
and shares using names. This is what I need but;
- When trying this form the Domain computer or Domain server, there is
something like this:
(There’s access to server it self - shares appears on the screen
without login prompt)
-Domain computer: when trying to open the share folder: I’m
prompted to write user name and the password and this goes over and
over again. The access is not granted.
- Domain server logged in locally or by the console to the server that
holds the share ( DC1 ) when trying to open the share folder that
appears on the screen there is a message:
“\\DC1\Testshare\ is not accessible. You may not have permission
to use this network resource. Contact the administrator of this server
to find out if you have access permissions.”
“It’s not possible to read information about the domain
controller configuration, because the device is busy or the access is
forbidden.” <- this is in other language so I have translate it
the best I can.
P.S.
There are 2 DC in my AD environment. There are no problems like this
with my second DC.
Help… And sorry for my bad English I’m trying the best I
can.
I don't see a problem modifying the registry to force the client to
broadcast mode. Once done, you may have to reboot (Not sure) but after
the
change try and see if you can get it to work.
The dc doesn't need to be a b-type for a client to find him.
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no
rights.
".bas" <bas.30j3fe@xxxxxxxxxxxxx> wrote in message
news:bas.30j3fe@xxxxxxxxxxxxxxxx
--
..bas
------------------------------------------------------------------------
..bas's Profile: http://forums.techarena.in/member.php?userid=35689
View this thread: http://forums.techarena.in/showthread.php?t=410029
http://forums.techarena.in
.
- Follow-Ups:
- Re: Sysvol issues.....
- From: Paul Bergson [MVP-DS]
- Re: Sysvol issues.....
- References:
- Re: Sysvol issues.....
- From: . bas
- Re: Sysvol issues.....
- From: Paul Bergson [MVP-DS]
- Re: Sysvol issues.....
- From: . bas
- Re: Sysvol issues.....
- From: Paul Bergson [MVP-DS]
- Re: Sysvol issues.....
- From: . bas
- Re: Sysvol issues.....
- From: Paul Bergson [MVP-DS]
- Re: Sysvol issues.....
- Prev by Date: Re: DHCP in mulit-domain
- Next by Date: RE: Does a domain rename (or trust then migrate) keep user profile
- Previous by thread: Re: Sysvol issues.....
- Next by thread: Re: Sysvol issues.....
- Index(es):
Relevant Pages
|