1

Topic: Check far off login to a computer on ip (not the domain)

Whether it is necessary to check up by one machine the login entered by the user approaches to another on ip. There is at least one implementation through WNetAddConnection2/WNetCancelConnection. There is it: https://support.microsoft.com/en-us/kb/180548 Is still LogonUser, but it without the domain works only locally (tried different methods). The first hangs at a local connection on public ip (there is  which it explicitly forbids to do). But it also hangs if to hammer not existing ip that is even worse. Advise to launch in a separate flow and CancelSynchronousIo to it then. It would be desirable that it answered at once if ip is not accessible, instead of hung how many to it takes in head (well or at least the time could be set a miss explicitly in API). The second is banal returns Guest even at the correct login. It would not be desirable to pick  or somehow far off them to adjust before checking up banality, to that-that the computer can be different and should remain in the same state as before check. Whether there are in the nature generally normal methods to check up the user and the password on a computer on ip without bedlam with a tambourine?

2

Re: Check far off login to a computer on ip (not the domain)

Hello, Vain, you wrote: V> It would be desirable that it answered at once if ip is not accessible So  it is necessary. If remote connections answers on  are automatically resolved also there are resolved.

3

Re: Check far off login to a computer on ip (not the domain)

Hello, wildwind, you wrote: V>> It would be desirable that it answered at once if ip is not accessible W> So  it is necessary. If remote connections answers on  are automatically resolved also there are resolved. Ping too can be superimposed. But not in it business. It is too much tambourine, for example, it is necessary to clarify that ip not local, differently as I wrote connection does not transit.