joker0927 has asked for the wisdom of the Perl Monks concerning the following question:

Any windows users seen this one? 

D:\perlscripts>perl test.pl
test
D:\perlscripts>perl -d test.pl
Unable to connect to remote host: 127.0.0.1:2000
Compilation failed in require.
        main::BEGIN() called at D:/Perl/lib/perl5db.pl line 0
        eval {...} called at D:/Perl/lib/perl5db.pl line 0
BEGIN failed--compilation aborted.

[download]

There is nothing using port 2000 (see netstat below). I do not have a software firewall running. These are the only 2 suggestions I can find on the matter at activestate.

This started after upgrading to 5.8, it did not do it in 5.6. However, now when I go back to 5.6 I get the same error!

I've tried to uninstall/reinstall, and even cleaned the reg of all "activestate" and "perl" entries on the second uninstall/reinstall attempt.

Furthermore, I've experienced this on 3 different systems. Two 2000pro machines and one Me machine (I know, I know. It's not mine.) Netstat revealed that none of them were using port 2000 at the time of the error.

I don't know c yet, so I'd really like to avoid building perl from source. Any help will be greatly appreciated. I'm new to programming, so I really NEED the debugger ;-) 

D:\perlscripts>netstat -a -n

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:23             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:113            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1028           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1031           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1037           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1039           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1040           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1043           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1044           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3306           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:6667           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:6668           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33333          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33334          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33335          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33336          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33337          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33338          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33339          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33340          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33341          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33342          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33343          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33344          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33345          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33346          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33347          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33348          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33349          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33350          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33351          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33352          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:33353          0.0.0.0:0              LISTENING
  TCP    127.0.0.1:24           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:24           127.0.0.1:1031         ESTABLISHED
  TCP    127.0.0.1:1031         127.0.0.1:24           ESTABLISHED
  TCP    127.0.0.1:1043         127.0.0.1:3306         ESTABLISHED
  TCP    127.0.0.1:3306         127.0.0.1:1043         ESTABLISHED
  TCP    127.0.0.1:43958        0.0.0.0:0              LISTENING
  TCP    192.168.0.2:21         0.0.0.0:0              LISTENING
  TCP    192.168.0.2:23         169.237.66.128:3139    ESTABLISHED
  TCP    192.168.0.2:139        0.0.0.0:0              LISTENING
  TCP    192.168.0.2:1028       66.216.70.167:80       CLOSE_WAIT
  TCP    192.168.0.2:1037       216.136.233.135:80     ESTABLISHED
  TCP    192.168.0.2:1039       64.12.30.184:1080      ESTABLISHED
  TCP    192.168.0.2:1040       64.12.27.182:1080      ESTABLISHED
  TCP    192.168.0.2:1199       216.200.201.212:80     TIME_WAIT
  TCP    192.168.0.2:1203       216.200.201.212:80     TIME_WAIT
  UDP    0.0.0.0:135            *:*
  UDP    0.0.0.0:445            *:*
  UDP    0.0.0.0:1026           *:*
  UDP    0.0.0.0:6666           *:*
  UDP    127.0.0.1:1046         *:*
  UDP    192.168.0.2:137        *:*
  UDP    192.168.0.2:138        *:*
  UDP    192.168.0.2:500        *:*

[download]

2003-05-02 edit ybiC: <readmore>

Replies are listed 'Best First'.
Re: ActiveState 5.8 debugger "Unable to connect to remote host: 127.0.0.1:2000"
by BrowserUk (Patriarch) on May 02, 2003 at 18:41 UTC

    Sounds like you have the RemotePort option set in an environment var PERL5DB_OPTS?

    The relevamt bits from the output of the 'h o' command: 

     RemotePort          Remote hostname:port for remote debugging
 ...
 During startup options are initialized from $ENV{PERLDB_OPTS}.
 You can put additional initialization options TTY, noTTY,
 ReadLine, NonStop, and RemotePort there (or use
 `R' after you set them).

    [download]
    Examine what is said, not who speaks.
    1) When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong.
    2) The only way of discovering the limits of the possible is to venture a little way past them into the impossible
    3) Any sufficiently advanced technology is indistinguishable from magic.
    Arthur C. Clarke.
[reply]
[d/l]
Re: ActiveState 5.8 debugger "Unable to connect to remote host: 127.0.0.1:2000"
by jand (Friar) on May 02, 2003 at 19:39 UTC
    This may happen if you had the Perl Dev Kit installed and turned it into "remote" debugging mode. It uses port 2000 to connect to the graphical debugger. It is possible that Visual Perl uses the same port too. Anyways, removing the PERLDB_OPTS environment variable should solve your problem.
[reply]
Re: ActiveState 5.8 debugger "Unable to connect to remote host: 127.0.0.1:2000"
by spacey (Scribe) on May 02, 2003 at 18:59 UTC
    I might be way off here but if your running XP
    It has a built in firewall.
    I have found it’s turned on by default on some version.
    I.e. If dell pre-install it or Compaq.
    But like I say I could be well off the mark here?

    See http://is.curtin.edu.au/info-security/winxp_firewall.htm
    For details.

    Regards,

    Gareth

[reply]

Back to Seekers of Perl Wisdom