Title: RE: [SA-list] Re: [SA-list] RE: [SA-list] RE: [SA-list] RE: [SA-list] RE: [SA-list] What can masquerade as a name resolution problem?
and just after that can you do a
    net view \\server
 
 

Dirk.

 


From: Barron,Joseph [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 02, 2006 4:55 PM
To: Servers Alive Discussion List
Subject: [SA-list] RE: [SA-list] RE: What can masquerade as a name resolution proble m?

 

Yes, no problems there.

 


From: Dirk Bulinckx [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 02, 2006 10:40 AM
To: Servers Alive Discussion List
Subject: [SA-list] RE: What can masquerade as a name resolution problem?

 

can you do (from the system running SA)

    net use  \\<server>\ipc$ /u:username *

towards the remote system?

 

 

Dirk.

 

 


From: Barron,Joseph [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 02, 2006 4:15 PM
To: Servers Alive Discussion List
Subject: [SA-list] RE: [SA-list] Re: [SA-list] RE: [SA-list] RE: [SA-list] RE: [SA-l ist] RE: [SA-list] What can masquerade as a name resolution problem?

OK --

I understand these things, that is what is so confusing.

To be clear:

Local logged on user does not exist on remote machine.

I can't do a net view \\<server> using that user because **that user does not exist on my local machine running SA**.  Further, other machines (which incidentally have an identical administrator username/password in use) that have the same (replicated) checks running against them are working just fine.

For the checks that are failing (hell, for just about every check I have that's not a ping), "Authenticate before checking" IS checked.  The user that is specified in that box is specified hostname/username, (these boxes are not in a domain), and this is the method I use for every check on every box, including checks that work on these boxes, and checks identical to the nonworking checks, but that are running (and functioning properly) against other boxes.

Spelling errors and syntax for username/password checked, checked, and rechecked.

The username and password have been double checked to ensure that they do still exist on the remote boxes, and are still administrator accounts. (to rule out user changes by well meaning personnel local to the boxes)

Further, 2-3 months ago this wasn't a problem, so SOMETHING has changed, presumably on the remote side.

Joe


***********************************************************************
The information contained in this email and any attachments may be confidential and is provided solely for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any disclosure, distribution, or use of this e-mail, its attachments or any information contained therein is unauthorised and prohibited. If you have received this in error, please contact the sender immediately and delete this e-mail and any attachments.

No responsibility is accepted for any virus or defect that might arise from opening this e-mail or attachments, whether or not it has been checked by anti-virus software.

To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]

Reply via email to