Re: Sysvol issues.....


Hi,

Yes the clients and the DC1 are in the same subnet. I was writing about
access deny situation that appears on the DC1 with network path using
NetBIOS name.

nslookup returns:

DC1
Serwer: UnKnown
Address: 192.168.10.1

*** UnKnown can?t find DC1: Server failed.

The FQDN ( \\DC1 ) path to the server lets You in and show the shared
list.


'Paul Bergson [MVP-DS Wrote:
;3330042']Is the client on the same subnet as the dc? If not then
NETBIOS broadcasts
won't work.

What happens if you do an nslookup of dc1? Does it bring back the IP
address?

Can you access the dc via the FQDN?

--
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.30i0jf@xxxxxxxxxxxxx> wrote in message
news:bas.30i0jf@xxxxxxxxxxxxxxxx

Hello,
@Paul Bergson
@Zeno

First of all I would like to tank @Paul for his complete reply in
this
topic. I need to refresh it a little bit. On my network, there are
two
W2k3 R2 SP2 servers (DC1 and DC2) and both have the DC role. Active
directory schema is simple. It is a single domain in forest, with
only
few not standard OU were the corporate clients and computers are
dropped. There are no GPO's attached to this OU's.

By the way there are no extra GPO's only the two standard GPO's DDP
and
DDCP.

What is the problem:

I can't access any share on DC1 by its computer NetBIOS name. If I
go
to: \\DC1\SYSVOL
the access is Deny. The permissions and security config. For this
folder are as it should be. This occurs when I'm logged in on an
Administrator account locally on this DC.
I can't access any ( even new created share ) on this Server by
using
it's NetBIOS name\share name. If you go to the share by the IP
Address
192.168.10.1(ex.)\SYSVOL the access is granted.

I was checking the NetBIOS helper: OK ( RUN ) / NIC priority in
advanced connection prosperities: OK (LAN NIC is the first one ).
The
domain name pings are correct. The DC1 from DC2 pings are correct.

Can anybody help me with my problem !? I was looking for solution
for
about 4 months now and I cant find jack unfortunately. I am at the
very
thin line to go madness with this one. I even reconsider
reformatting
drives on this server and re-cofigurate it again. But is it the good
idea - I don't think so.


--
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



--
..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

.

Relevant Pages

  • Re: Sysvol issues.....
    ... Is the client on the same subnet as the dc? ... @Paul Bergson ... I can't access any share on DC1 by its computer NetBIOS name. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Sysvol issues.....
    ... How do have your NETBIOS name resolution set up? ... If you are running dhcp you can set it to run via broadcast. ... Yes the clients and the DC1 are in the same subnet. ... 'Paul Bergson [MVP-DS Wrote: ...
    (microsoft.public.windows.server.active_directory)
  • RE: Browser Problems
    ... As for DC1, please send the screen shot of the exact error message to ... the 4321 issue may be caused by a NetBIOS name conflict between ... the workstation and either another workstation with the same NetBIOS name, ...
    (microsoft.public.windows.server.migration)
Loading