DC Access Problem

I have a big problem with a Server 2003 to connect to the Domain. Everything
was working fine and then I had to add another PC to the network. The PC
isn't even joined to the Domain. The problem is that I loged in with the
same name as the server is. After that all the users couldn't connect to the
Mapped Drive anymore and also if I tried to connect to the files on the long
way (Entire network - Microsoft Windows Network - XXX I get an error saying
that acces is denied and to contact system administrator. After that I tried
to take one PC of the Domain and tried to join it again to the Domain. I
then get the following error:
Logon to Domain failed. The following error occurred. Attempt to join
Domain XYZ, Access Denied. However, I can ping the server IP no problem.
What could have caused this behaviour and how can I fix it? I really
appreciate any help I can get, I am stuck.
Thank you

Hello Somchai,

Remove the pc with the same name as the server, then check DNS and DHCP if
it is listed there and delete the entries.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> I have a big problem with a Server 2003 to connect to the Domain.
> Everything
> was working fine and then I had to add another PC to the network. The
> PC
> isn't even joined to the Domain. The problem is that I loged in with
> the
> same name as the server is. After that all the users couldn't connect
> to the
> Mapped Drive anymore and also if I tried to connect to the files on
> the long
> way (Entire network - Microsoft Windows Network - XXX I get an error
> saying
> that acces is denied and to contact system administrator. After that
> I tried
> to take one PC of the Domain and tried to join it again to the Domain.
> I
> then get the following error:
> Logon to Domain failed. The following error occurred. Attempt to
> join
> Domain XYZ, Access Denied. However, I can ping the server IP no
> problem.
> What could have caused this behaviour and how can I fix it? I really
> appreciate any help I can get, I am stuck.
> Thank you

Hi Meinolf,

Thanks for your reply. I removed the PC already. And as you say I deleted
the the entries already. But still same problem. Any other hints? I really
appreciate it.

"Meinolf Weber" wrote:

> Hello Somchai,
>
> Remove the pc with the same name as the server, then check DNS and DHCP if
> it is listed there and delete the entries.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > I have a big problem with a Server 2003 to connect to the Domain.
> > Everything
> > was working fine and then I had to add another PC to the network. The
> > PC
> > isn't even joined to the Domain. The problem is that I loged in with
> > the
> > same name as the server is. After that all the users couldn't connect
> > to the
> > Mapped Drive anymore and also if I tried to connect to the files on
> > the long
> > way (Entire network - Microsoft Windows Network - XXX I get an error
> > saying
> > that acces is denied and to contact system administrator. After that
> > I tried
> > to take one PC of the Domain and tried to join it again to the Domain.
> > I
> > then get the following error:
> > Logon to Domain failed. The following error occurred. Attempt to
> > join
> > Domain XYZ, Access Denied. However, I can ping the server IP no
> > problem.
> > What could have caused this behaviour and how can I fix it? I really
> > appreciate any help I can get, I am stuck.
> > Thank you
>
>
>

What I may have to mention is well, it is not the login which is the same as
I said, it is actually the PC name which is the same name as the Server which
runs the DC and files. Also running an AD diagnostics I get an error similar
AD service cannot connect DNS to resolve name. And in the Event log I get
something like Cannot connect to AD service. Thanks

"Meinolf Weber" wrote:

> Hello Somchai,
>
> Remove the pc with the same name as the server, then check DNS and DHCP if
> it is listed there and delete the entries.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > I have a big problem with a Server 2003 to connect to the Domain.
> > Everything
> > was working fine and then I had to add another PC to the network. The
> > PC
> > isn't even joined to the Domain. The problem is that I loged in with
> > the
> > same name as the server is. After that all the users couldn't connect
> > to the
> > Mapped Drive anymore and also if I tried to connect to the files on
> > the long
> > way (Entire network - Microsoft Windows Network - XXX I get an error
> > saying
> > that acces is denied and to contact system administrator. After that
> > I tried
> > to take one PC of the Domain and tried to join it again to the Domain.
> > I
> > then get the following error:
> > Logon to Domain failed. The following error occurred. Attempt to
> > join
> > Domain XYZ, Access Denied. However, I can ping the server IP no
> > problem.
> > What could have caused this behaviour and how can I fix it? I really
> > appreciate any help I can get, I am stuck.
> > Thank you
>
>
>

Hello Somchai,

Run dcdiag /v and netdiag /v and post the output here if you have errors.
Also post an ipconfig /all from the DC and the machine with problems. How
many DC's do you have?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hi Meinolf,
>
> Thanks for your reply. I removed the PC already. And as you say I
> deleted the the entries already. But still same problem. Any other
> hints? I really appreciate it.
>
> "Meinolf Weber" wrote:
>
>> Hello Somchai,
>>
>> Remove the pc with the same name as the server, then check DNS and
>> DHCP if it is listed there and delete the entries.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> I have a big problem with a Server 2003 to connect to the Domain.
>>> Everything
>>> was working fine and then I had to add another PC to the network.
>>> The
>>> PC
>>> isn't even joined to the Domain. The problem is that I loged in
>>> with
>>> the
>>> same name as the server is. After that all the users couldn't
>>> connect
>>> to the
>>> Mapped Drive anymore and also if I tried to connect to the files on
>>> the long
>>> way (Entire network - Microsoft Windows Network - XXX I get an error
>>> saying
>>> that acces is denied and to contact system administrator. After
>>> that
>>> I tried
>>> to take one PC of the Domain and tried to join it again to the
>>> Domain.
>>> I
>>> then get the following error:
>>> Logon to Domain failed. The following error occurred. Attempt to
>>> join
>>> Domain XYZ, Access Denied. However, I can ping the server IP no
>>> problem.
>>> What could have caused this behaviour and how can I fix it? I
>>> really
>>> appreciate any help I can get, I am stuck.
>>> Thank yo

Hello Somchai,

You can not have to machines, doesn't matter if server or workstation, with
the same computername.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> What I may have to mention is well, it is not the login which is the
> same as I said, it is actually the PC name which is the same name as
> the Server which runs the DC and files. Also running an AD
> diagnostics I get an error similar AD service cannot connect DNS to
> resolve name. And in the Event log I get something like Cannot
> connect to AD service. Thanks
>
> "Meinolf Weber" wrote:
>
>> Hello Somchai,
>>
>> Remove the pc with the same name as the server, then check DNS and
>> DHCP if it is listed there and delete the entries.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> I have a big problem with a Server 2003 to connect to the Domain.
>>> Everything
>>> was working fine and then I had to add another PC to the network.
>>> The
>>> PC
>>> isn't even joined to the Domain. The problem is that I loged in
>>> with
>>> the
>>> same name as the server is. After that all the users couldn't
>>> connect
>>> to the
>>> Mapped Drive anymore and also if I tried to connect to the files on
>>> the long
>>> way (Entire network - Microsoft Windows Network - XXX I get an error
>>> saying
>>> that acces is denied and to contact system administrator. After
>>> that
>>> I tried
>>> to take one PC of the Domain and tried to join it again to the
>>> Domain.
>>> I
>>> then get the following error:
>>> Logon to Domain failed. The following error occurred. Attempt to
>>> join
>>> Domain XYZ, Access Denied. However, I can ping the server IP no
>>> problem.
>>> What could have caused this behaviour and how can I fix it? I
>>> really
>>> appreciate any help I can get, I am stuck.
>>> Thank yo

I know but it was done by mistake and that created the problem. After that
happen, even I haven taken the PC off, nobody can access the files anymore,
not even administrator. Regarding the DC I only have one Server which is the
DC and also the files are on this server.

"Meinolf Weber" wrote:

> Hello Somchai,
>
> You can not have to machines, doesn't matter if server or workstation, with
> the same computername.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > What I may have to mention is well, it is not the login which is the
> > same as I said, it is actually the PC name which is the same name as
> > the Server which runs the DC and files. Also running an AD
> > diagnostics I get an error similar AD service cannot connect DNS to
> > resolve name. And in the Event log I get something like Cannot
> > connect to AD service. Thanks
> >
> > "Meinolf Weber" wrote:
> >
> >> Hello Somchai,
> >>
> >> Remove the pc with the same name as the server, then check DNS and
> >> DHCP if it is listed there and delete the entries.
> >>
> >> Best regards
> >>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >> ** Please do NOT email, only reply to Newsgroups
> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >>> I have a big problem with a Server 2003 to connect to the Domain.
> >>> Everything
> >>> was working fine and then I had to add another PC to the network.
> >>> The
> >>> PC
> >>> isn't even joined to the Domain. The problem is that I loged in
> >>> with
> >>> the
> >>> same name as the server is. After that all the users couldn't
> >>> connect
> >>> to the
> >>> Mapped Drive anymore and also if I tried to connect to the files on
> >>> the long
> >>> way (Entire network - Microsoft Windows Network - XXX I get an error
> >>> saying
> >>> that acces is denied and to contact system administrator. After
> >>> that
> >>> I tried
> >>> to take one PC of the Domain and tried to join it again to the
> >>> Domain.
> >>> I
> >>> then get the following error:
> >>> Logon to Domain failed. The following error occurred. Attempt to
> >>> join
> >>> Domain XYZ, Access Denied. However, I can ping the server IP no
> >>> problem.
> >>> What could have caused this behaviour and how can I fix it? I
> >>> really
> >>> appreciate any help I can get, I am stuck.
> >>> Thank you
>
>
>

Hi Meinolf,
Back again. FYI, in the event log I get a DNS error ID: 4013

"Somchai" wrote:

> I know but it was done by mistake and that created the problem. After that
> happen, even I haven taken the PC off, nobody can access the files anymore,
> not even administrator. Regarding the DC I only have one Server which is the
> DC and also the files are on this server.
>
> "Meinolf Weber" wrote:
>
> > Hello Somchai,
> >
> > You can not have to machines, doesn't matter if server or workstation, with
> > the same computername.
> >
> > Best regards
> >
> > Meinolf Weber
> > Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> > no rights.
> > ** Please do NOT email, only reply to Newsgroups
> > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >
> > > What I may have to mention is well, it is not the login which is the
> > > same as I said, it is actually the PC name which is the same name as
> > > the Server which runs the DC and files. Also running an AD
> > > diagnostics I get an error similar AD service cannot connect DNS to
> > > resolve name. And in the Event log I get something like Cannot
> > > connect to AD service. Thanks
> > >
> > > "Meinolf Weber" wrote:
> > >
> > >> Hello Somchai,
> > >>
> > >> Remove the pc with the same name as the server, then check DNS and
> > >> DHCP if it is listed there and delete the entries.
> > >>
> > >> Best regards
> > >>
> > >> Meinolf Weber
> > >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> > >> confers
> > >> no rights.
> > >> ** Please do NOT email, only reply to Newsgroups
> > >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> > >>> I have a big problem with a Server 2003 to connect to the Domain.
> > >>> Everything
> > >>> was working fine and then I had to add another PC to the network.
> > >>> The
> > >>> PC
> > >>> isn't even joined to the Domain. The problem is that I loged in
> > >>> with
> > >>> the
> > >>> same name as the server is. After that all the users couldn't
> > >>> connect
> > >>> to the
> > >>> Mapped Drive anymore and also if I tried to connect to the files on
> > >>> the long
> > >>> way (Entire network - Microsoft Windows Network - XXX I get an error
> > >>> saying
> > >>> that acces is denied and to contact system administrator. After
> > >>> that
> > >>> I tried
> > >>> to take one PC of the Domain and tried to join it again to the
> > >>> Domain.
> > >>> I
> > >>> then get the following error:
> > >>> Logon to Domain failed. The following error occurred. Attempt to
> > >>> join
> > >>> Domain XYZ, Access Denied. However, I can ping the server IP no
> > >>> problem.
> > >>> What could have caused this behaviour and how can I fix it? I
> > >>> really
> > >>> appreciate any help I can get, I am stuck.
> > >>> Thank you
> >
> >
> >

Hello Somchai,

What about dcdiag, netdiag and how many dc's do you have from my posting
before?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hi Meinolf,
> Back again. FYI, in the event log I get a DNS error ID: 4013
> "Somchai" wrote:
>
>> I know but it was done by mistake and that created the problem.
>> After that happen, even I haven taken the PC off, nobody can access
>> the files anymore, not even administrator. Regarding the DC I only
>> have one Server which is the DC and also the files are on this
>> server.
>>
>> "Meinolf Weber" wrote:
>>
>>> Hello Somchai,
>>>
>>> You can not have to machines, doesn't matter if server or
>>> workstation, with the same computername.
>>>
>>> Best regards
>>>
>>> Meinolf Weber
>>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>>> confers
>>> no rights.
>>> ** Please do NOT email, only reply to Newsgroups
>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>> What I may have to mention is well, it is not the login which is
>>>> the same as I said, it is actually the PC name which is the same
>>>> name as the Server which runs the DC and files. Also running an AD
>>>> diagnostics I get an error similar AD service cannot connect DNS to
>>>> resolve name. And in the Event log I get something like Cannot
>>>> connect to AD service. Thanks
>>>>
>>>> "Meinolf Weber" wrote:
>>>>
>>>>> Hello Somchai,
>>>>>
>>>>> Remove the pc with the same name as the server, then check DNS and
>>>>> DHCP if it is listed there and delete the entries.
>>>>>
>>>>> Best regards
>>>>>
>>>>> Meinolf Weber
>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>>> and
>>>>> confers
>>>>> no rights.
>>>>> ** Please do NOT email, only reply to Newsgroups
>>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>>> I have a big problem with a Server 2003 to connect to the Domain.
>>>>>> Everything
>>>>>> was working fine and then I had to add another PC to the network.
>>>>>> The
>>>>>> PC
>>>>>> isn't even joined to the Domain. The problem is that I loged in
>>>>>> with
>>>>>> the
>>>>>> same name as the server is. After that all the users couldn't
>>>>>> connect
>>>>>> to the
>>>>>> Mapped Drive anymore and also if I tried to connect to the files
>>>>>> on
>>>>>> the long
>>>>>> way (Entire network - Microsoft Windows Network - XXX I get an
>>>>>> error
>>>>>> saying
>>>>>> that acces is denied and to contact system administrator. After
>>>>>> that
>>>>>> I tried
>>>>>> to take one PC of the Domain and tried to join it again to the
>>>>>> Domain.
>>>>>> I
>>>>>> then get the following error:
>>>>>> Logon to Domain failed. The following error occurred. Attempt
>>>>>> to
>>>>>> join
>>>>>> Domain XYZ, Access Denied. However, I can ping the server IP no
>>>>>> problem.
>>>>>> What could have caused this behaviour and how can I fix it? I
>>>>>> really
>>>>>> appreciate any help I can get, I am stuck.
>>>>>> Thank you

Binding Paths:
Owner of the binding path : Point to Point Protocol Over Ethernet
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Point to Point Protocol Over Ethernet
Lower Component: HP NC7760 Gigabit Server Adapter


Component Name : Point to Point Tunneling Protocol
Bind Name: mspptp
Binding Paths:

Component Name : Layer 2 Tunneling Protocol
Bind Name: msl2tp
Binding Paths:

Component Name : Remote Access NDIS WAN Driver
Bind Name: NdisWan
Binding Paths:
Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: Direct Parallel

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: WAN Miniport (PPPOE)

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: WAN Miniport (PPTP)

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: WAN Miniport (L2TP)

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanasync
Upper Component: Remote Access NDIS WAN Driver
Lower Component: RAS Async Adapter


Component Name : Message-oriented TCP/IP Protocol (SMB session)
Bind Name: NetbiosSmb
Binding Paths:

Component Name : WINS Client(TCP/IP) Protocol
Bind Name: NetBT
Binding Paths:
Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: HP NC7760 Gigabit Server Adapter

Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : Internet Protocol (TCP/IP)
Bind Name: Tcpip
Binding Paths:
Owner of the binding path : Internet Protocol (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: HP NC7760 Gigabit Server Adapter

Owner of the binding path : Internet Protocol (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : Client for Microsoft Networks
Bind Name: LanmanWorkstation
Binding Paths:
Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Client for Microsoft Networks
Lower Component: Message-oriented TCP/IP Protocol (SMB session)

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: HP NC7760 Gigabit Server Adapter

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : WebClient
Bind Name: WebClient
Binding Paths:

Component Name : DHCP Server
Bind Name: DHCPServer
Binding Paths:

Component Name : Wireless Configuration
Bind Name: wzcsvc
Binding Paths:

Component Name : Network Load Balancing
Bind Name: Wlbs
Binding Paths:
Owner of the binding path : Network Load Balancing
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Network Load Balancing
Lower Component: HP NC7760 Gigabit Server Adapter


Component Name : Steelhead
Bind Name: RemoteAccess
Binding Paths:

Component Name : Dial-Up Server
Bind Name: msrassrv
Binding Paths:

Component Name : Remote Access Connection Manager
Bind Name: RasMan
Binding Paths:

Component Name : Dial-Up Client
Bind Name: msrascli
Binding Paths:

Component Name : File and Printer Sharing for Microsoft Networks
Bind Name: LanmanServer
Binding Paths:
Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: Message-oriented TCP/IP Protocol (SMB session)

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: HP NC7760 Gigabit Server Adapter

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : NetBIOS Interface
Bind Name: NetBIOS
Binding Paths:
Owner of the binding path : NetBIOS Interface
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: HP NC7760 Gigabit Server Adapter

Owner of the binding path : NetBIOS Interface
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : Generic Packet Classifier
Bind Name: Gpc
Binding Paths:

Component Name : Application Layer Gateway
Bind Name: ALG
Binding Paths:

Component Name : WAN Miniport (IP)
Bind Name: NdisWanIp
Binding Paths:

Component Name : Direct Parallel
Bind Name: {DEF9ACFB-D3B2-4544-99B3-75686B068FF1}
Binding Paths:

Component Name : WAN Miniport (PPPOE)
Bind Name: {F7841D4D-4836-4E4A-9D07-16B3EA59A2A7}
Binding Paths:

Component Name : WAN Miniport (PPTP)
Bind Name: {941BDE96-496B-47DB-89D8-6CAF8F13EF3A}
Binding Paths:

Component Name : WAN Miniport (L2TP)
Bind Name: {432B74F2-4C0A-4F8C-947C-756FCED497CD}
Binding Paths:

Component Name : RAS Async Adapter
Bind Name: {AEECD217-C193-4E6C-899F-0BB47BC6AA8B}
Binding Paths:

Component Name : HP NC7760 Gigabit Server Adapter
Bind Name: {35A9E169-D4D4-497E-B580-A4909E3C1CDF}
Binding Paths:



WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully

C:\Documents and Settings\Administrator>


"Meinolf Weber" wrote:

> Hello Somchai,
>
> What about dcdiag, netdiag and how many dc's do you have from my posting
> before?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > Hi Meinolf,
> > Back again. FYI, in the event log I get a DNS error ID: 4013
> > "Somchai" wrote:
> >
> >> I know but it was done by mistake and that created the problem.
> >> After that happen, even I haven taken the PC off, nobody can access
> >> the files anymore, not even administrator. Regarding the DC I only
> >> have one Server which is the DC and also the files are on this
> >> server.
> >>
> >> "Meinolf Weber" wrote:
> >>
> >>> Hello Somchai,
> >>>
> >>> You can not have to machines, doesn't matter if server or
> >>> workstation, with the same computername.
> >>>
> >>> Best regards
> >>>
> >>> Meinolf Weber
> >>> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >>> confers
> >>> no rights.
> >>> ** Please do NOT email, only reply to Newsgroups
> >>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >>>> What I may have to mention is well, it is not the login which is
> >>>> the same as I said, it is actually the PC name which is the same
> >>>> name as the Server which runs the DC and files. Also running an AD
> >>>> diagnostics I get an error similar AD service cannot connect DNS to
> >>>> resolve name. And in the Event log I get something like Cannot
> >>>> connect to AD service. Thanks
> >>>>
> >>>> "Meinolf Weber" wrote:
> >>>>
> >>>>> Hello Somchai,
> >>>>>
> >>>>> Remove the pc with the same name as the server, then check DNS and
> >>>>> DHCP if it is listed there and delete the entries.
> >>>>>
> >>>>> Best regards
> >>>>>
> >>>>> Meinolf Weber
> >>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
> >>>>> and
> >>>>> confers
> >>>>> no rights.
> >>>>> ** Please do NOT email, only reply to Newsgroups
> >>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >>>>>> I have a big problem with a Server 2003 to connect to the Domain.
> >>>>>> Everything
> >>>>>> was working fine and then I had to add another PC to the network.
> >>>>>> The
> >>>>>> PC
> >>>>>> isn't even joined to the Domain. The problem is that I loged in
> >>>>>> with
> >>>>>> the
> >>>>>> same name as the server is. After that all the users couldn't
> >>>>>> connect
> >>>>>> to the
> >>>>>> Mapped Drive anymore and also if I tried to connect to the files
> >>>>>> on
> >>>>>> the long
> >>>>>> way (Entire network - Microsoft Windows Network - XXX I get an
> >>>>>> error
> >>>>>> saying
> >>>>>> that acces is denied and to contact system administrator. After
> >>>>>> that
> >>>>>> I tried
> >>>>>> to take one PC of the Domain and tried to join it again to the
> >>>>>> Domain.
> >>>>>> I
> >>>>>> then get the following error:
> >>>>>> Logon to Domain failed. The following error occurred. Attempt
> >>>>>> to
> >>>>>> join
> >>>>>> Domain XYZ, Access Denied. However, I can ping the server IP no
> >>>>>> problem.
> >>>>>> What could have caused this behaviour and how can I fix it? I
> >>>>>> really
> >>>>>> appreciate any help I can get, I am stuck.
> >>>>>> Thank you
>
>
>