Re: Client Tool can't connect to ARServer 7.5

Hi, You can make sure the following are in your ar.conf Register-With-Portmapper: T TCD-Specific-Port: 7100 Then in your client tool, specify 7100 in the account TCP. You can use other numbers but do check with your network team. The basic idea is keep over 1024. Kind regards Danny Original Me

Re: Client Tool can't connect to ARServer 7.5

Hi David, Not seen you since the UBS days. Hope all is well, Kind regards Danny Original Message: - From: David Sanders david.sand...@westoverconsulting.co.uk Date: Tue, 13 Oct 2009 12:41:35 +0100 To: arslist@ARSLIST.ORG Subject: Re: Client Tool can't connect to ARServer 7.5 So

Re: Client Tool can't connect to ARServer 7.5

Hi, Since your running portmapper, this should reply on UDP port 111 so make sure you have that open on any firewall you may have. To see on a windows env, I use tcpview from microsoft. This will show the process and the tcp port. http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx R

Re: [623] Authentication failed

Hi, Turn on plugin logging and set it to ALL (100 in the ar.conf) this will tell you exactly what the problem is. Feel free to post it when your done and we can take a look. Make sure you copy from +VL until -VL for that user. You will know what I mean when you look at the plugin log file. Kind

Re: cmdbdriver exporting data

What happends if you still use computer system but put a qualifier in so you reduce the output. Or put a value for first matching and max matching and do it in batches Kind regards Danny Original Message: - From: Frank Caruso caruso.fr...@gmail.com Date: Thu, 27 Aug 2009 10:40:32