Unable to browse network

Our college network has two domains in it, I'll call one DomainA, and the
other DomainB.

DomainA is a WinNT-based domain. DomainB is Win2003 with Active Directory.

I am the manager of an organizational unit in DomainB.

I have set up a Windows 2003 server in my OU. Using ActiveDirectory Users
and Computers, I can see that this server is a member of my OU. I have 8
WinXP computers in the OU as well.

I have established a mutual trust relationship between DomainA, and DomainB.

I am not able to browse DomainB, the parent domain of the OU with Windows
Explorer from the Win2k3 server.

When I run Windows Explorer on my Win2k3 server, go to My Network
Places...Entire Network...Microsoft Windows Network...I can see both
DomainA, and DomainB listed.

If I click on DomainA, the tree expands to show me each of the computers in
DomainA, and I can view each of the shares on those computers.

However, when I click on DomainB, after a long delay, I get an error message
"DomainB is not accessible. You might not have permission to use this
network resource. Contact the administrator of this server to find out if
you have access permissions."

Incidentally, I am able to browse DomainB from my WinXP workstation, which
is also a member of the OU. However, the browsing appears to be incomplete.
While it shows the other workstations in the OU, it does not show the Win2k3
server, nor does it show the OU itself.

Incidentally-2: On the Win2K3 server, Windows Explorer, I am able to
manually map a drive to a shared folder on my workstation.

I appreciate your help with this.

Thanks,
Jim

The first thing to check is that Netbios over TCP/IP is enabled on the
NIC of this server. The computer browser service uses Netbios names and
broadcasts to build the browse list.

Jim Walsh wrote:
> Our college network has two domains in it, I'll call one DomainA, and
> the other DomainB.
>
> DomainA is a WinNT-based domain. DomainB is Win2003 with Active
> Directory.
> I am the manager of an organizational unit in DomainB.
>
> I have set up a Windows 2003 server in my OU. Using ActiveDirectory
> Users and Computers, I can see that this server is a member of my OU.
> I have 8 WinXP computers in the OU as well.
>
> I have established a mutual trust relationship between DomainA, and
> DomainB.
> I am not able to browse DomainB, the parent domain of the OU with
> Windows Explorer from the Win2k3 server.
>
> When I run Windows Explorer on my Win2k3 server, go to My Network
> Places...Entire Network...Microsoft Windows Network...I can see both
> DomainA, and DomainB listed.
>
> If I click on DomainA, the tree expands to show me each of the
> computers in DomainA, and I can view each of the shares on those
> computers.
> However, when I click on DomainB, after a long delay, I get an error
> message "DomainB is not accessible. You might not have permission to
> use this network resource. Contact the administrator of this server
> to find out if you have access permissions."
>
> Incidentally, I am able to browse DomainB from my WinXP workstation,
> which is also a member of the OU. However, the browsing appears to be
> incomplete. While it shows the other workstations in the OU, it does
> not show the Win2k3 server, nor does it show the OU itself.
>
> Incidentally-2: On the Win2K3 server, Windows Explorer, I am able to
> manually map a drive to a shared folder on my workstation.
>
> I appreciate your help with this.
>
> Thanks,
> Jim

Check the DNS Settings on workstations trying to connect to Domain B. These
should really include a DNS Server from both domains, with the primary being
the DNS Server in it's own domain (For example, a workstation in Domain B
will have have it's primary DNS as it's own authenticating server and it's
secondary as the DNS Server in Domain A.)

You didn't mention whether or not you'd setup a DNS Server in your NT 4
Domain, and if not, now might be a good time to start!

Gareth Saunders
BOFH

"Jim Walsh" wrote:

> Our college network has two domains in it, I'll call one DomainA, and the
> other DomainB.
>
> DomainA is a WinNT-based domain. DomainB is Win2003 with Active Directory.
>
> I am the manager of an organizational unit in DomainB.
>
> I have set up a Windows 2003 server in my OU. Using ActiveDirectory Users
> and Computers, I can see that this server is a member of my OU. I have 8
> WinXP computers in the OU as well.
>
> I have established a mutual trust relationship between DomainA, and DomainB.
>
> I am not able to browse DomainB, the parent domain of the OU with Windows
> Explorer from the Win2k3 server.
>
> When I run Windows Explorer on my Win2k3 server, go to My Network
> Places...Entire Network...Microsoft Windows Network...I can see both
> DomainA, and DomainB listed.
>
> If I click on DomainA, the tree expands to show me each of the computers in
> DomainA, and I can view each of the shares on those computers.
>
> However, when I click on DomainB, after a long delay, I get an error message
> "DomainB is not accessible. You might not have permission to use this
> network resource. Contact the administrator of this server to find out if
> you have access permissions."
>
> Incidentally, I am able to browse DomainB from my WinXP workstation, which
> is also a member of the OU. However, the browsing appears to be incomplete.
> While it shows the other workstations in the OU, it does not show the Win2k3
> server, nor does it show the OU itself.
>
> Incidentally-2: On the Win2K3 server, Windows Explorer, I am able to
> manually map a drive to a shared folder on my workstation.
>
> I appreciate your help with this.
>
> Thanks,
> Jim
>
>
>

Bill,

Thanks for your suggestion. I should have included that NetBios over TCP/IP
is enabled on the NIC of this server.

What next?

Jim

"Bill Grant" <not.available@online> wrote in message
news:uGm9TZ$(E-Mail Removed)...
> The first thing to check is that Netbios over TCP/IP is enabled on the
> NIC of this server. The computer browser service uses Netbios names and
> broadcasts to build the browse list.
>
> Jim Walsh wrote:
>> Our college network has two domains in it, I'll call one DomainA, and
>> the other DomainB.
>>
>> DomainA is a WinNT-based domain. DomainB is Win2003 with Active
>> Directory.
>> I am the manager of an organizational unit in DomainB.
>>
>> I have set up a Windows 2003 server in my OU. Using ActiveDirectory
>> Users and Computers, I can see that this server is a member of my OU.
>> I have 8 WinXP computers in the OU as well.
>>
>> I have established a mutual trust relationship between DomainA, and
>> DomainB.
>> I am not able to browse DomainB, the parent domain of the OU with
>> Windows Explorer from the Win2k3 server.
>>
>> When I run Windows Explorer on my Win2k3 server, go to My Network
>> Places...Entire Network...Microsoft Windows Network...I can see both
>> DomainA, and DomainB listed.
>>
>> If I click on DomainA, the tree expands to show me each of the
>> computers in DomainA, and I can view each of the shares on those
>> computers.
>> However, when I click on DomainB, after a long delay, I get an error
>> message "DomainB is not accessible. You might not have permission to
>> use this network resource. Contact the administrator of this server
>> to find out if you have access permissions."
>>
>> Incidentally, I am able to browse DomainB from my WinXP workstation,
>> which is also a member of the OU. However, the browsing appears to be
>> incomplete. While it shows the other workstations in the OU, it does
>> not show the Win2k3 server, nor does it show the OU itself.
>>
>> Incidentally-2: On the Win2K3 server, Windows Explorer, I am able to
>> manually map a drive to a shared folder on my workstation.
>>
>> I appreciate your help with this.
>>
>> Thanks,
>> Jim
>
>

Gareth,

Thanks for your reply to my posting.

Actually, all of the computers (workstations and servers), in both domains,
are using the same DNS servers, and these DNS servers are located in
DomainB.

Jim

"Gareth Saunders" <(E-Mail Removed)> wrote in
message news:BEC7C665-E708-4012-A229-(E-Mail Removed)...
> Check the DNS Settings on workstations trying to connect to Domain B.
> These
> should really include a DNS Server from both domains, with the primary
> being
> the DNS Server in it's own domain (For example, a workstation in Domain B
> will have have it's primary DNS as it's own authenticating server and it's
> secondary as the DNS Server in Domain A.)
>
> You didn't mention whether or not you'd setup a DNS Server in your NT 4
> Domain, and if not, now might be a good time to start!
>
> Gareth Saunders
> BOFH
>
> "Jim Walsh" wrote:
>
>> Our college network has two domains in it, I'll call one DomainA, and the
>> other DomainB.
>>
>> DomainA is a WinNT-based domain. DomainB is Win2003 with Active
>> Directory.
>>
>> I am the manager of an organizational unit in DomainB.
>>
>> I have set up a Windows 2003 server in my OU. Using ActiveDirectory Users
>> and Computers, I can see that this server is a member of my OU. I have 8
>> WinXP computers in the OU as well.
>>
>> I have established a mutual trust relationship between DomainA, and
>> DomainB.
>>
>> I am not able to browse DomainB, the parent domain of the OU with Windows
>> Explorer from the Win2k3 server.
>>
>> When I run Windows Explorer on my Win2k3 server, go to My Network
>> Places...Entire Network...Microsoft Windows Network...I can see both
>> DomainA, and DomainB listed.
>>
>> If I click on DomainA, the tree expands to show me each of the computers
>> in
>> DomainA, and I can view each of the shares on those computers.
>>
>> However, when I click on DomainB, after a long delay, I get an error
>> message
>> "DomainB is not accessible. You might not have permission to use this
>> network resource. Contact the administrator of this server to find out if
>> you have access permissions."
>>
>> Incidentally, I am able to browse DomainB from my WinXP workstation,
>> which
>> is also a member of the OU. However, the browsing appears to be
>> incomplete.
>> While it shows the other workstations in the OU, it does not show the
>> Win2k3
>> server, nor does it show the OU itself.
>>
>> Incidentally-2: On the Win2K3 server, Windows Explorer, I am able to
>> manually map a drive to a shared folder on my workstation.
>>
>> I appreciate your help with this.
>>
>> Thanks,
>> Jim
>>
>>
>>

Jim

I have the same setup.

I had problems initially with firewalls active on clients. Norton Security
Suite was killing any browsing. I removed Norton and I can see all machines
on both domains from any client.

Rgds

Maurice

"Jim Walsh" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Gareth,
>
> Thanks for your reply to my posting.
>
> Actually, all of the computers (workstations and servers), in both
> domains, are using the same DNS servers, and these DNS servers are located
> in DomainB.
>
> Jim
>
> "Gareth Saunders" <(E-Mail Removed)> wrote in
> message news:BEC7C665-E708-4012-A229-(E-Mail Removed)...
>> Check the DNS Settings on workstations trying to connect to Domain B.
>> These
>> should really include a DNS Server from both domains, with the primary
>> being
>> the DNS Server in it's own domain (For example, a workstation in Domain
>> B
>> will have have it's primary DNS as it's own authenticating server and
>> it's
>> secondary as the DNS Server in Domain A.)
>>
>> You didn't mention whether or not you'd setup a DNS Server in your NT 4
>> Domain, and if not, now might be a good time to start!
>>
>> Gareth Saunders
>> BOFH
>>
>> "Jim Walsh" wrote:
>>
>>> Our college network has two domains in it, I'll call one DomainA, and
>>> the
>>> other DomainB.
>>>
>>> DomainA is a WinNT-based domain. DomainB is Win2003 with Active
>>> Directory.
>>>
>>> I am the manager of an organizational unit in DomainB.
>>>
>>> I have set up a Windows 2003 server in my OU. Using ActiveDirectory
>>> Users
>>> and Computers, I can see that this server is a member of my OU. I have 8
>>> WinXP computers in the OU as well.
>>>
>>> I have established a mutual trust relationship between DomainA, and
>>> DomainB.
>>>
>>> I am not able to browse DomainB, the parent domain of the OU with
>>> Windows
>>> Explorer from the Win2k3 server.
>>>
>>> When I run Windows Explorer on my Win2k3 server, go to My Network
>>> Places...Entire Network...Microsoft Windows Network...I can see both
>>> DomainA, and DomainB listed.
>>>
>>> If I click on DomainA, the tree expands to show me each of the computers
>>> in
>>> DomainA, and I can view each of the shares on those computers.
>>>
>>> However, when I click on DomainB, after a long delay, I get an error
>>> message
>>> "DomainB is not accessible. You might not have permission to use this
>>> network resource. Contact the administrator of this server to find out
>>> if
>>> you have access permissions."
>>>
>>> Incidentally, I am able to browse DomainB from my WinXP workstation,
>>> which
>>> is also a member of the OU. However, the browsing appears to be
>>> incomplete.
>>> While it shows the other workstations in the OU, it does not show the
>>> Win2k3
>>> server, nor does it show the OU itself.
>>>
>>> Incidentally-2: On the Win2K3 server, Windows Explorer, I am able to
>>> manually map a drive to a shared folder on my workstation.
>>>
>>> I appreciate your help with this.
>>>
>>> Thanks,
>>> Jim
>>>
>>>
>>>
>
>

In general, it must be enough to browse your network.

"Jim Walsh" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Bill,
>
> Thanks for your suggestion. I should have included that NetBios over
> TCP/IP is enabled on the NIC of this server.
>
> What next?
>
> Jim
>
> "Bill Grant" <not.available@online> wrote in message
> news:uGm9TZ$(E-Mail Removed)...
>> The first thing to check is that Netbios over TCP/IP is enabled on the
>> NIC of this server. The computer browser service uses Netbios names and
>> broadcasts to build the browse list.
>>
>> Jim Walsh wrote:
>>> Our college network has two domains in it, I'll call one DomainA, and
>>> the other DomainB.
>>>
>>> DomainA is a WinNT-based domain. DomainB is Win2003 with Active
>>> Directory.
>>> I am the manager of an organizational unit in DomainB.
>>>
>>> I have set up a Windows 2003 server in my OU. Using ActiveDirectory
>>> Users and Computers, I can see that this server is a member of my OU.
>>> I have 8 WinXP computers in the OU as well.
>>>
>>> I have established a mutual trust relationship between DomainA, and
>>> DomainB.
>>> I am not able to browse DomainB, the parent domain of the OU with
>>> Windows Explorer from the Win2k3 server.
>>>
>>> When I run Windows Explorer on my Win2k3 server, go to My Network
>>> Places...Entire Network...Microsoft Windows Network...I can see both
>>> DomainA, and DomainB listed.
>>>
>>> If I click on DomainA, the tree expands to show me each of the
>>> computers in DomainA, and I can view each of the shares on those
>>> computers.
>>> However, when I click on DomainB, after a long delay, I get an error
>>> message "DomainB is not accessible. You might not have permission to
>>> use this network resource. Contact the administrator of this server
>>> to find out if you have access permissions."
>>>
>>> Incidentally, I am able to browse DomainB from my WinXP workstation,
>>> which is also a member of the OU. However, the browsing appears to be
>>> incomplete. While it shows the other workstations in the OU, it does
>>> not show the Win2k3 server, nor does it show the OU itself.
>>>
>>> Incidentally-2: On the Win2K3 server, Windows Explorer, I am able to
>>> manually map a drive to a shared folder on my workstation.
>>>
>>> I appreciate your help with this.
>>>
>>> Thanks,
>>> Jim
>>
>>
>
>

Maurice,

Can you provide me with more details?

1. How many machines in each network? Are you domain administrator in both
domains?

2. Firewalls? WinXP firewall? Did you disable them? Were they needed for
network security?

3. Removing Norton ultimately solved the problem? Was NAV the problem? Does
your network have no antivirus now?

4. One symptom of my problem is the inconsitency between machines. My Win2K3
server, a member of DomainB, is not allowed to browse DomainB at all, while
another machine in DomainB has no problem.

Thanks for your help.

Jim


"Maurice Bishop" <(E-Mail Removed)> wrote in message
news:4405146f$0$3594$(E-Mail Removed)...
> Jim
>
> I have the same setup.
>
> I had problems initially with firewalls active on clients. Norton Security
> Suite was killing any browsing. I removed Norton and I can see all
> machines on both domains from any client.
>
> Rgds
>
> Maurice
>
> "Jim Walsh" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Gareth,
>>
>> Thanks for your reply to my posting.
>>
>> Actually, all of the computers (workstations and servers), in both
>> domains, are using the same DNS servers, and these DNS servers are
>> located in DomainB.
>>
>> Jim
>>
>> "Gareth Saunders" <(E-Mail Removed)> wrote in
>> message news:BEC7C665-E708-4012-A229-(E-Mail Removed)...
>>> Check the DNS Settings on workstations trying to connect to Domain B.
>>> These
>>> should really include a DNS Server from both domains, with the primary
>>> being
>>> the DNS Server in it's own domain (For example, a workstation in Domain
>>> B
>>> will have have it's primary DNS as it's own authenticating server and
>>> it's
>>> secondary as the DNS Server in Domain A.)
>>>
>>> You didn't mention whether or not you'd setup a DNS Server in your NT 4
>>> Domain, and if not, now might be a good time to start!
>>>
>>> Gareth Saunders
>>> BOFH
>>>
>>> "Jim Walsh" wrote:
>>>
>>>> Our college network has two domains in it, I'll call one DomainA, and
>>>> the
>>>> other DomainB.
>>>>
>>>> DomainA is a WinNT-based domain. DomainB is Win2003 with Active
>>>> Directory.
>>>>
>>>> I am the manager of an organizational unit in DomainB.
>>>>
>>>> I have set up a Windows 2003 server in my OU. Using ActiveDirectory
>>>> Users
>>>> and Computers, I can see that this server is a member of my OU. I have
>>>> 8
>>>> WinXP computers in the OU as well.
>>>>
>>>> I have established a mutual trust relationship between DomainA, and
>>>> DomainB.
>>>>
>>>> I am not able to browse DomainB, the parent domain of the OU with
>>>> Windows
>>>> Explorer from the Win2k3 server.
>>>>
>>>> When I run Windows Explorer on my Win2k3 server, go to My Network
>>>> Places...Entire Network...Microsoft Windows Network...I can see both
>>>> DomainA, and DomainB listed.
>>>>
>>>> If I click on DomainA, the tree expands to show me each of the
>>>> computers in
>>>> DomainA, and I can view each of the shares on those computers.
>>>>
>>>> However, when I click on DomainB, after a long delay, I get an error
>>>> message
>>>> "DomainB is not accessible. You might not have permission to use this
>>>> network resource. Contact the administrator of this server to find out
>>>> if
>>>> you have access permissions."
>>>>
>>>> Incidentally, I am able to browse DomainB from my WinXP workstation,
>>>> which
>>>> is also a member of the OU. However, the browsing appears to be
>>>> incomplete.
>>>> While it shows the other workstations in the OU, it does not show the
>>>> Win2k3
>>>> server, nor does it show the OU itself.
>>>>
>>>> Incidentally-2: On the Win2K3 server, Windows Explorer, I am able to
>>>> manually map a drive to a shared folder on my workstation.
>>>>
>>>> I appreciate your help with this.
>>>>
>>>> Thanks,
>>>> Jim
>>>>
>>>>
>>>>
>>
>>
>
>

Iuri,

Thanks for your response to my posting.

I don't understand what you are telling me. Do you think that NetBios over
TCP/IP is enough to enable browsing? If so, why is browsing failing?

Jim

"Iuri Cuznetov" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In general, it must be enough to browse your network.
>
> "Jim Walsh" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Bill,
>>
>> Thanks for your suggestion. I should have included that NetBios over
>> TCP/IP is enabled on the NIC of this server.
>>
>> What next?
>>
>> Jim
>>
>> "Bill Grant" <not.available@online> wrote in message
>> news:uGm9TZ$(E-Mail Removed)...
>>> The first thing to check is that Netbios over TCP/IP is enabled on
>>> the NIC of this server. The computer browser service uses Netbios names
>>> and broadcasts to build the browse list.
>>>
>>> Jim Walsh wrote:
>>>> Our college network has two domains in it, I'll call one DomainA, and
>>>> the other DomainB.
>>>>
>>>> DomainA is a WinNT-based domain. DomainB is Win2003 with Active
>>>> Directory.
>>>> I am the manager of an organizational unit in DomainB.
>>>>
>>>> I have set up a Windows 2003 server in my OU. Using ActiveDirectory
>>>> Users and Computers, I can see that this server is a member of my OU.
>>>> I have 8 WinXP computers in the OU as well.
>>>>
>>>> I have established a mutual trust relationship between DomainA, and
>>>> DomainB.
>>>> I am not able to browse DomainB, the parent domain of the OU with
>>>> Windows Explorer from the Win2k3 server.
>>>>
>>>> When I run Windows Explorer on my Win2k3 server, go to My Network
>>>> Places...Entire Network...Microsoft Windows Network...I can see both
>>>> DomainA, and DomainB listed.
>>>>
>>>> If I click on DomainA, the tree expands to show me each of the
>>>> computers in DomainA, and I can view each of the shares on those
>>>> computers.
>>>> However, when I click on DomainB, after a long delay, I get an error
>>>> message "DomainB is not accessible. You might not have permission to
>>>> use this network resource. Contact the administrator of this server
>>>> to find out if you have access permissions."
>>>>
>>>> Incidentally, I am able to browse DomainB from my WinXP workstation,
>>>> which is also a member of the OU. However, the browsing appears to be
>>>> incomplete. While it shows the other workstations in the OU, it does
>>>> not show the Win2k3 server, nor does it show the OU itself.
>>>>
>>>> Incidentally-2: On the Win2K3 server, Windows Explorer, I am able to
>>>> manually map a drive to a shared folder on my workstation.
>>>>
>>>> I appreciate your help with this.
>>>>
>>>> Thanks,
>>>> Jim
>>>
>>>
>>
>>
>
>

Sorry, if my response was hard to understand for you.

Computer borwsing uses NetBIOS protocol and broadcasts for completing the
list of computers in your "Network Neighbourhood". In most of cases,
enabling NetBIOS over TCP/IP is enough to start network browsing. When you
enabled this protocol on your Win2003 server, you had to wait some time
because of Master Browser election procedure, wich was started in that
moment. If your browsing is still failng, can you post here "ipconfig /all"
and "nbtstat -n" results from your server.

Hope my english was clear enough.


"Jim Walsh" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Iuri,
>
> Thanks for your response to my posting.
>
> I don't understand what you are telling me. Do you think that NetBios over
> TCP/IP is enough to enable browsing? If so, why is browsing failing?
>
> Jim
>
> "Iuri Cuznetov" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> In general, it must be enough to browse your network.
>>
>> "Jim Walsh" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Bill,
>>>
>>> Thanks for your suggestion. I should have included that NetBios over
>>> TCP/IP is enabled on the NIC of this server.
>>>
>>> What next?
>>>
>>> Jim
>>>
>>> "Bill Grant" <not.available@online> wrote in message
>>> news:uGm9TZ$(E-Mail Removed)...
>>>> The first thing to check is that Netbios over TCP/IP is enabled on
>>>> the NIC of this server. The computer browser service uses Netbios names
>>>> and broadcasts to build the browse list.
>>>>
>>>> Jim Walsh wrote:
>>>>> Our college network has two domains in it, I'll call one DomainA, and
>>>>> the other DomainB.
>>>>>
>>>>> DomainA is a WinNT-based domain. DomainB is Win2003 with Active
>>>>> Directory.
>>>>> I am the manager of an organizational unit in DomainB.
>>>>>
>>>>> I have set up a Windows 2003 server in my OU. Using ActiveDirectory
>>>>> Users and Computers, I can see that this server is a member of my OU.
>>>>> I have 8 WinXP computers in the OU as well.
>>>>>
>>>>> I have established a mutual trust relationship between DomainA, and
>>>>> DomainB.
>>>>> I am not able to browse DomainB, the parent domain of the OU with
>>>>> Windows Explorer from the Win2k3 server.
>>>>>
>>>>> When I run Windows Explorer on my Win2k3 server, go to My Network
>>>>> Places...Entire Network...Microsoft Windows Network...I can see both
>>>>> DomainA, and DomainB listed.
>>>>>
>>>>> If I click on DomainA, the tree expands to show me each of the
>>>>> computers in DomainA, and I can view each of the shares on those
>>>>> computers.
>>>>> However, when I click on DomainB, after a long delay, I get an error
>>>>> message "DomainB is not accessible. You might not have permission to
>>>>> use this network resource. Contact the administrator of this server
>>>>> to find out if you have access permissions."
>>>>>
>>>>> Incidentally, I am able to browse DomainB from my WinXP workstation,
>>>>> which is also a member of the OU. However, the browsing appears to be
>>>>> incomplete. While it shows the other workstations in the OU, it does
>>>>> not show the Win2k3 server, nor does it show the OU itself.
>>>>>
>>>>> Incidentally-2: On the Win2K3 server, Windows Explorer, I am able to
>>>>> manually map a drive to a shared folder on my workstation.
>>>>>
>>>>> I appreciate your help with this.
>>>>>
>>>>> Thanks,
>>>>> Jim
>>>>
>>>>
>>>
>>>
>>
>>
>
>