Re: Login server unavilable?
anonymous_at_discussions.microsoft.com
Date: 02/03/04
- Next message: Steve Winograd [MVP]: "Re: What is MATCLI .."
- Previous message: Daniel L. Belton: "DNS - wierd problem"
- In reply to: Ron Lowe: "Re: Login server unavilable?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 3 Feb 2004 02:26:12 -0800
Thanks for the help....
The mappeed drive solution allowed a connect.
Then even better I can now browse and open network shares.
Thanks
Again.
>-----Original Message-----
>"Andy" <anonymous@discussions.microsoft.com> wrote in
message
>news:8b3201c3e980$2f336950$a601280a@phx.gbl...
>> I have networked 2 machines via a netgear hub.
>> The hub also connects to a router, providing ADSL access
>> to both machines.
>>
>> Machine 1 is running W2000 Pro on a domain (work
computer)
>> Machine 2 is running XP pro on a workgroup (home
computer)
>>
>> Both systems are able to connect to the internet.
>>
>> Both systems can be seen on the microsoft network under
>> the workgroup.
>> Both systems are getting valid DHCP ip addresses
assigned
>> by the router.
>> I can ping both machines.
>>
>> My problem is:
>>
>> Using machine 2 I can connect to machine 1 and access
>> share drives.
>>
>> However when using machine 1 I can see machine 2 on the
>> network, but when I click on the network icon
representing
>> machine 2 I get the following error:
>>
>> 'Computer unavailable
>> A network login server is not available to service the
>> request'
>>
>> I have enabled all obvious settings on machine 2
>> Root drive share and security set to allow connections
>> My computer set to allow remote connections
>>
>> One person I have spoken to suggested that XP by default
>> does not allow connections from lower versions of
windows??
>>
>>
>> Am I missing something ???
>> Do I need to set up specific permissions in the security
>> settings?
>>
>> Please help
>
>
>Rather than browsing into the machine,
>try to map a drive, but using alternate credentials to
>explicitly specify a local account...
>
>On machine 1, go to the map network drive dialog.
>Enter the name of the drive you would like to call it (
like Z: )
>Enter the network path ( like \\machine2\sharename )
>Click the option to connect using a different user name.
>Supply a username valid on machine 2 in the form:
> machine2\username
>and enter the password.
>
>The explicit use of a local account should prevent it
>looking for a domain controller.
>
>The stuff about lower versions of windows is not correct.
>
>
>--
>Best Regards
>Ron Lowe
>MVP - Windows Networking
>
>
>
>
>
>.
>
- Next message: Steve Winograd [MVP]: "Re: What is MATCLI .."
- Previous message: Daniel L. Belton: "DNS - wierd problem"
- In reply to: Ron Lowe: "Re: Login server unavilable?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|