From: Agostino on

Here's an error joining an xp workstation to a sbs 2003 domain.

The following error occurred attempting to join the domain "<domain>":
Windows cannot find the network path.

Then i added "Files and Printer Sharing for Microsoft Networks" to the
server lan interface, and it has worked

Why doesn't dcdiag/netdiag diagnose this missing correctly?
Thanks in advance
agostino


From: Lanwench [MVP - Exchange] on
Agostino <sclauzero(a)cancellami.cedapsrl.com> wrote:
> Here's an error joining an xp workstation to a sbs 2003 domain.
>
> The following error occurred attempting to join the domain "<domain>":
> Windows cannot find the network path.
>
> Then i added "Files and Printer Sharing for Microsoft Networks" to the
> server lan interface, and it has worked

Hmm - odd that it wasn't there already?
>
> Why doesn't dcdiag/netdiag diagnose this missing correctly?
> Thanks in advance
> agostino

You should be using http://servername/connectcomputer to do this, since
you're in SBS. Set up everything with the wizards and it will work. If you
deviate from them it's entirely possible a lot of things will be messed up.


From: Agostino Sclauzero on
> You should be using http://servername/connectcomputer to do this, since
> you're in SBS. Set up everything with the wizards and it will work. If you
> deviate from them it's entirely possible a lot of things will be messed
> up.

Tried to do http://servername/connectcomputer.
But the error (as often happens with web interfaces) was much more cryptic
than this one.

"Lanwench [MVP - Exchange]"
<lanwench(a)heybuddy.donotsendme.unsolicitedmailatyahoo.com> ha scritto nel
messaggio news:%23DRqxNPbIHA.4712(a)TK2MSFTNGP04.phx.gbl...
> Agostino <sclauzero(a)cancellami.cedapsrl.com> wrote:
>> Here's an error joining an xp workstation to a sbs 2003 domain.
>>
>> The following error occurred attempting to join the domain "<domain>":
>> Windows cannot find the network path.
>>
>> Then i added "Files and Printer Sharing for Microsoft Networks" to the
>> server lan interface, and it has worked
>
> Hmm - odd that it wasn't there already?
>>
>> Why doesn't dcdiag/netdiag diagnose this missing correctly?
>> Thanks in advance
>> agostino
>
> You should be using http://servername/connectcomputer to do this, since
> you're in SBS. Set up everything with the wizards and it will work. If you
> deviate from them it's entirely possible a lot of things will be messed
> up.
>

From: Lanwench [MVP - Exchange] on
Agostino Sclauzero <sc.agostino(a)gmail.com> wrote:
>> You should be using http://servername/connectcomputer to do this,
>> since you're in SBS. Set up everything with the wizards and it will
>> work. If you deviate from them it's entirely possible a lot of
>> things will be messed up.
>
> Tried to do http://servername/connectcomputer.
> But the error (as often happens with web interfaces) was much more
> cryptic than this one.
>

Then you probably have larger issues - you might mention the errors, whether
this ever worked, what you see in your event logs, and perhaps also how you
set up the server in the first place.


> "Lanwench [MVP - Exchange]"
> <lanwench(a)heybuddy.donotsendme.unsolicitedmailatyahoo.com> ha scritto
> nel messaggio news:%23DRqxNPbIHA.4712(a)TK2MSFTNGP04.phx.gbl...
>> Agostino <sclauzero(a)cancellami.cedapsrl.com> wrote:
>>> Here's an error joining an xp workstation to a sbs 2003 domain.
>>>
>>> The following error occurred attempting to join the domain
>>> "<domain>": Windows cannot find the network path.
>>>
>>> Then i added "Files and Printer Sharing for Microsoft Networks" to
>>> the server lan interface, and it has worked
>>
>> Hmm - odd that it wasn't there already?
>>>
>>> Why doesn't dcdiag/netdiag diagnose this missing correctly?
>>> Thanks in advance
>>> agostino
>>
>> You should be using http://servername/connectcomputer to do this,
>> since you're in SBS. Set up everything with the wizards and it will
>> work. If you deviate from them it's entirely possible a lot of
>> things will be messed up.



 | 
Pages: 1
Prev: VSS Errors after disk clone
Next: Malformed Emails