Very Computer

Is this normal?  I would have thought that I would have
been able to browse published items to the active directoy
even when Netbios was disabled.

Quote:> the active directory icon does not show
> up when double clicking on the "Entire Network" icon.  I
> can do a search and find the shared folder in the active
> directory so I believe everything is setup correctly.

> Is this normal?  I would have thought that I would have
> been able to browse published items to the active directoy
> even when Netbios was disabled.

Mike
--
Mike Brannigan [MS]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions.
Please use these newsgroups

Quote:> I have created a share and published it to the active
> directory as spelled out in several help documents.  I am
> experiencing a problem with a XP Pro client machine with
> Netbios disabled.  The client machine is part of the
> Windows 2000 server domain and can log in sucessfully.  In
> windows explorer the active directory icon does not show
> up when double clicking on the "Entire Network" icon.  I
> can do a search and find the shared folder in the active
> directory so I believe everything is setup correctly.

> Is this normal?  I would have thought that I would have
> been able to browse published items to the active directoy
> even when Netbios was disabled.

**************
The following process is TOTALLY UNSUPPORTED and provided AS IS with no
warranties, and confers no rights.
To re-enable the Directory folder on a Windows XP Professional client PC in
a Domain Environment:

1. Copy the dsfolder.dll from a Windows 2000 (SP2 or later) machine to the
Windows XP machines (It is in the SYSTEM32 folder under the WINNT folder on
Windows 2000 (by default) and needs to go into the SYSTEM32 folder usually
under WINDOWS on Windows XP (by default)

2. Close all instances of Windows Explorer

3. Run "regsvr32 dsfolder.dll" on the XP machines.

4. Done

The above process is TOTALLY UNSUPPORTED and provided AS IS with no
warranties, and confers no rights.
**************

It works for me.

--
Best Regards,
Ron Lowe.
MS-MVP - Windows Networking

Mike
--
Mike Brannigan [MS]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions.
Please use these newsgroups

Quote:> I have created a share and published it to the active
> directory as spelled out in several help documents.  I am
> experiencing a problem with a XP Pro client machine with
> Netbios disabled.  The client machine is part of the
> Windows 2000 server domain and can log in sucessfully.  In
> windows explorer the active directory icon does not show
> up when double clicking on the "Entire Network" icon.  I
> can do a search and find the shared folder in the active
> directory so I believe everything is setup correctly.

> Is this normal?  I would have thought that I would have
> been able to browse published items to the active directoy
> even when Netbios was disabled.

**************
The following process is TOTALLY UNSUPPORTED and provided AS IS with no
warranties, and confers no rights.
To re-enable the Directory folder on a Windows XP Professional client PC
in
a Domain Environment:

1. Copy the dsfolder.dll from a Windows 2000 (SP2 or later) machine to
the
Windows XP machines (It is in the SYSTEM32 folder under the WINNT folder
on
Windows 2000 (by default) and needs to go into the SYSTEM32 folder
usually
under WINDOWS on Windows XP (by default)

2. Close all instances of Windows Explorer

3. Run "regsvr32 dsfolder.dll" on the XP machines.

4. Done

The above process is TOTALLY UNSUPPORTED and provided AS IS with no
warranties, and confers no rights.
**************

It works for me.

--
Best Regards,
Ron Lowe.
MS-MVP - Windows Networking

Quote:> Thanks Ron,  I forgot to include the workaround I posted to another
> group.  :-)
> --
> Regards,

> Mike

I was reading your post in the same way I read most output from MS, ie by reading between the lines.   There's often as much information contained in what's _not_ said as there is in what _is_ said.

I knew you posted the original workaround.
So the fact you hadn't mentioned it raised an eyebrow.
I assumed that you had intentionally chosen not to repeat it.
And I wondered why.
I wondered if some internal fall-out might have followed it's original posting.

So I re-posted it without crediting the source so as not to re-involve you in any potential internal political fall-out.

Am I becoming a conspiricy theorist or what?
<Adjusts tinfoil hat>

--
Best Regards,
Ron Lowe.
MS-MVP - Windows Networking