Remote debugger - cannot connect

I can’t get the remote debugger to work, despite trying everything I can find in Designer Help and this forum.

The problem is the same as several other people have reported, being:

I start the agent on the server, and the console shows that the remote debugger has paused the agent.

I start the remote debugger client, select the server and the database, click Open, and get the message “cannot connect to remote system”.

The setup is as follows:

Server: Domino 6.5.4 on Windows 2003; remote debugging is enabled in server document, remote debug port is enabled, and RDebug task is running.

Client: Notes 6.5.4

Agent: Scheduled to run Never; “Allow remote debugging” is checked on Security tab.

I’ve also tried setting the agent to run monthly on that server - made no difference.

Things suggested in other forum posts, which I’ve tried to no avail:

Changed remote debug port from 60000 to 1355 (shouldn’t matter because all ports on server are open to local traffic, according to our network administrator).

Moved database to Domino data directory (it was originally two levels deeper).

Checked for Java Server Controller; this is not running so should not be an issue.

Has anyone got any other suggestions which might fix this problem?

Subject: RE: Remote debugger - cannot connect

Is the DNS name of the server the same as the server common name? I’ve had problems because of this.

Subject: RE: Remote debugger - cannot connect

As far as I can tell, it is.

Server common name = britten.

Accessible through Windows explorer as \britten.

Can ping “britten”, which fully resolves to “britten.internal.isw.net.au”.

Subject: Remote debugger - problem solved!

For anyone else having trouble with the LotusScript remote debugger, I’ve solved my problem, and it was this:

On the Basics tab of the server document, the field “Fully qualified Internet host name” did not exactly match the server’s real name on the network.

I only noticed this morning, when I typed “load rdebug” at the server console I got the message:

Remote Debug Server: Unable to obtain the server’s IP address, will use loopback address: No address associated with name

Once the field was corrected in the server document and the server was restarted, the problems went away, and the debugger now works perfectly.

Thanks to all who responded to this thread, but I think the only person on the right track was Andre.

Subject: Remote debugger - problem solved differently

Had the same problem, however we could not just chnage the fully qualified name and the server name. What I did was just created a server connection document from the client with the full server name and that fixed my problem. Hope that helps someone.

Subject: Remote debugger - problem solved differently - but the same :slight_smile:

Defining of server’s FQDN in both server’s and client’s hosts files and putting FQDN in connection document solved problem that was bothering me for years…

T.

P.S: I used servers LAN address for all entries (not 127.0.0.1 on server or something like that…)

Subject: see our tip

I never got it working on a Domino 6 server just a Notes 6 client. I noticed that in the Domino 7 documentation that this is shown as a client feature only.

I thought someone in the forum said they got it working on a server before.

Howard

Subject: RE: see our tip

How is that link related to my problem?

I am trying to use the Domino Remote Debugger to debug a LotusScript agent, not a Java agent.

According to the Designer Help, and some posts on this forum, that works for LotusScript agents running on a server, and the Remote Debugger on a client, but I could only get “cannot connect to remote system” for the server I was using yesterday.

Today, I’ve tried the same thing with a test server at a different organisation, but with a copy of the same database and agent I was trying to debug yesterday, and it worked with no problems at all… weird.

Subject: RE: see our tip

Is remote debugging allowed on your server?

Subject: RE: see our tip

Yes. That was set to “Enabled”, and the RDebug task was started, before I made any attempt to use the remote debugger on the client.

Subject: *Sorry, too much Java (code, not coffee) lately…