View previous topic :: View next topic |
Author |
Message |
Marcus
Joined: 18 Nov 2002 Posts: 367
|
Posted: Thu Apr 01, 2004 1:18 am Post subject: |
|
|
I don't believe it is impossible to force a connection with a different account. I can believe you haven't found the right way yet |
|
Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002 Posts: 12795 Location: USA
|
Posted: Thu Apr 01, 2004 1:20 am Post subject: |
|
|
Connection Manager uses correct account, Windows uses another one
Yes, we can try to find some workaround but we may fail |
|
Back to top |
|
|
Marcus
Joined: 18 Nov 2002 Posts: 367
|
Posted: Thu Apr 01, 2004 2:04 am Post subject: |
|
|
One thing I know for sure: The first connection is made with the account used to start HostMonitor. There is no other connection (successfull or failed). HostMonitor just doesn't make the connection with the credentials supplied.
Since there are more application who are able to connect to a remote machine using a different account, I'm sure you will find the right method to connect to a remote machine.
Quote: | Connection Manager uses correct account, Windows uses another one | This implies there should be at least two login attempts: One from HostMonitor, which is dropped and then the one from Windows. Like I said before, there is only one. |
|
Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002 Posts: 12795 Location: USA
|
Posted: Thu Apr 01, 2004 12:53 pm Post subject: |
|
|
Quote: | This implies there should be at least two login attempts: One from HostMonitor, which is dropped and then the one from Windows. Like I said before, there is only one. |
You do not understand. HostMonitor does not perform connection by itself. HostMonitor uses Windows API, it says "I need connection to that system using this user name and this password". Windows says "Ok" and uses different user name and password.
Regards
Alex |
|
Back to top |
|
|
Marcus
Joined: 18 Nov 2002 Posts: 367
|
Posted: Fri Apr 02, 2004 2:06 am Post subject: |
|
|
Quote: | You do not understand |
I do now and I'm sure you will find a solution |
|
Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002 Posts: 12795 Location: USA
|
Posted: Fri Apr 02, 2004 2:16 pm Post subject: |
|
|
I already know one possible workaround but I cannot guarantee it will work in all cases.
Use IP address of the system instead of name. E.g. when I use \\testsystem1\d as path, Windows uses wrong user account. If I specify \\192.168.10.5\d, Windows uses specified user account.
Regards
Alex |
|
Back to top |
|
|
Marcus
Joined: 18 Nov 2002 Posts: 367
|
Posted: Mon Apr 05, 2004 1:15 am Post subject: |
|
|
Quote: | Use IP address of the system instead of name |
Does this mean I have to change every test?? or just the entry in the Connection Manager? |
|
Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002 Posts: 12795 Location: USA
|
Posted: Mon Apr 05, 2004 12:18 pm Post subject: |
|
|
Entry in Connection Manager. |
|
Back to top |
|
|
mmonaghan
Joined: 01 Nov 2003 Posts: 19
|
Posted: Tue Apr 06, 2004 11:40 pm Post subject: |
|
|
Quote: |
Posted: Thu Apr 01, 2004 7:16 am Post subject:
--------------------------------------------------------------------------------
Quote:
The message is titled "HostMonitor", says "Invalid pointer operation." and has an "OK" button. Spelling, spacing, Caps, etc were preserved.
Finally I found it. There is update at www.ks-soft.net/hostmon.eng/hm441.zip
Regards
Alex
|
There's no file at that address. I'd be happy to test it if it were there. |
|
Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002 Posts: 12795 Location: USA
|
Posted: Tue Apr 06, 2004 11:44 pm Post subject: |
|
|
You don't need that file anymore. Advanced Host Monitor 4.42 available at web site
Regards
Alex |
|
Back to top |
|
|
Marcus
Joined: 18 Nov 2002 Posts: 367
|
Posted: Thu Apr 08, 2004 4:27 am Post subject: |
|
|
Quote: | Entry in Connection Manager. |
Tried all three combinations, none worked. |
|
Back to top |
|
|
Marcus
Joined: 18 Nov 2002 Posts: 367
|
Posted: Fri Apr 09, 2004 4:51 am Post subject: |
|
|
Tried the following:
1. Created a seperate account on a remote machine
2. Added the server name as a resource for the remote machine, using the new account (in Connection Manager).
3. Changed the new password with the password generator (OK)
3. Changed the password for the account HostMonitor is running under on the remote machine (so login should fail)
4. Started the test for the remote machine
This what happened at the remote machine:
1. After starting the test, a login failure appears for the account HostMonitor is running under (OK, is changed so should not work)
2. Successfull login attempt with the new seperate account is made and the tests are performed
After 10 minutes (the test interval)
1. A login failure appears for the account HostMonitor is running under (OK, is changed so should not work)
2. HostMonitor goes to the "bad" status! No login attempts with the new seperate account is tried!
After this, changing the password for the new account, using the password generator shows a login failure for the HostMonitor account followed by a succesfull login of the new seperate account. The password is changed successfully!
Setting is to reconnect when needed and to log for failed authentication attempts (log file is not present)
Anybody any clue?? |
|
Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002 Posts: 12795 Location: USA
|
Posted: Fri Apr 09, 2004 5:38 pm Post subject: |
|
|
Quote: | 2. Successfull login attempt with the new seperate account is made and the tests are performed
After 10 minutes (the test interval)
1. A login failure appears for the account HostMonitor is running under (OK, is changed so should not work)
2. HostMonitor goes to the "bad" status! No login attempts with the new seperate account is tried! |
Interesting who/what dropped connection between 1st and 2nd tests? HostMonitor does not do that.
Regards
Alex |
|
Back to top |
|
|
Marcus
Joined: 18 Nov 2002 Posts: 367
|
Posted: Sat Apr 10, 2004 7:06 am Post subject: |
|
|
Quote: | Interesting who/what dropped connection |
The problem is, there is no second connection attempt logged at the remote server. In other words: HostMonitor does not try to make the second connection (which it should). |
|
Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002 Posts: 12795 Location: USA
|
Posted: Mon Apr 12, 2004 6:40 pm Post subject: |
|
|
I checked following test methods:
- Folder/File Size
- File/Folder Availability
- File Integrity
- Process
- Service
- CPU
- File Compare
- UNC
Code is correct.
What test did you check?
BTW:
Note #1: If application calls Windows API to perform connect (using WNetAddConnection2 function) and attempt fails, Windows ignores following calls for some time. I don't know what exactly timeout because its not documented but its how my Windows 2000 system works.
Probably different Windows works in different way, I don't know. Have not seen any information in Microsoft docs.
Note #2: Connection Manager has its own cache with 3 sec timeout. So, if HostMonitor starts test and cannot connect to remote system, it does not perform another connection to the same system using the same account (and password) within 3 sec.
Regards
Alex |
|
Back to top |
|
|
|