Re: Mapping client shares from sbs 2003 server

EvanMac <EvanMac@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Thanks for getting back so soon. Actually it is more than just a
mapping problem.

....but you haven't actually answered my question about the error you get,
and how you're trying.

If I browse My Network from within Windows Explorer on the server I
can not access any of the workstations within the domain. I get a
permissions error when I click on any workstation. The error also
states that the network path was not found.

Browsing has very little to do with your ability to map a drive or access
\\computername or \\sharename. If you try going to that, in start | run,
what happens?

The server & workstations must all specify *only* the internal DNS server IP
(i.e., your SBS box's LAN IP) for DNS - no external IP addresses must show
up in an ipconfig /all

Browsing requires NetBIOS over TCP/IP, and won't work over a routed network
connection (you need WINS for that, and WINS should be used anyway). Make
sure that all clients have NetBIOS over TCP/IP enabled - they should, if
you're using your SBS server for DHCP. Then make sure they're all pointing
to the WINS server IP (if you're using your SBS server for DHCP, they
should). The Windows firewall should already have been configured to allow
you inboundaccess, if you ran the /connectcomputer script to join them to
the domain.

Much depends on your setup & how you configured everything.


"Lanwench [MVP - Exchange]" wrote:

EvanMac <EvanMac@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi,
I can not map to a share on a client workstation from our sbs 2003
machine while logged in as the domain admin. If I log onto another
workstation as the domain
admin it works fine, Just doesn't work from the server. Does anyone
have any ideas.
Thanks

You're logging into your server, and trying to map a drive to a
share on a client workstation? My first question is "why?" ....but
my second question is, what errors do you get? How are you trying to
do it? Via the command line (net use) or via Explorer?

Really best not to have any data or shares on client workstations;
keep it all on the server. You'll still want to figure out why you
can't do this & fix it, of course, but thought I'd mention this just
the same.



.

Relevant Pages

  • Re: Event ID 537: Error at Logon
    ... I think the SBS server configuration is fine and this is a client ... On this Windows XP Client workstation, please make sure that "time zone ... >> Windows includes the W32Time Time service tool that is required by the ...
    (microsoft.public.windows.server.sbs)
  • Re: Re-Post - "the trust relationship between this workstation and
    ... There were no logged events in either the DC or workstation. ... DC/DNS Server - DCDiag ... Attr: subschemaSubentry ... only problem is adding a new user account on the station. ...
    (microsoft.public.windows.server.active_directory)
  • trust relationship between workstation and the primary domain fail
    ... When I am at a workstation attached to the domain and try to add a local ... Server: server1.contoso.org ... Testing LDAP servers in Domain contoso ... ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.general)
  • RE: Slow Logon related to groups
    ... Open Server Management console on SBS ... Ensure the problematic user has permission to access its home folder on ... After the problematic user logon workstation, ...
    (microsoft.public.windows.server.sbs)
  • Re: =?ISO-8859-1?Q?Can=92t_see_a_compute?= =?ISO-8859-1?Q?r_in_the_network?=
    ... Find Computer Browser ... Find Server ... Find Workstation ... CONFIG and Browser and Sharedaccess are RUNNING. ...
    (microsoft.public.windowsxp.network_web)