in reply to Re: DBI Proxy connection prob
in thread DBI Proxy connection prob

I can run this small test server on my unix box
#!/home/utils/perl/bin/perl use strict; use warnings; use IO::Socket; my $server = IO::Socket::INET->new(LocalPort => 4444, Reuse => 1, List +en => 10); die $@ unless $server; print "waiting for a connection\n"; while (my $client = $server->accept()) { my $line = <$client>; print $line; close($client); }
And run this test client on my Win XP box...
use strict; use warnings; use IO::Socket; my $socket = IO::Socket::INET->new(PeerAddr => 'isfe', PeerPort => 4444, Type => SOCK_STREAM); die $@ unless $socket; print $socket "hello\n"; close($socket);
And successfully receive a message.
erickn@isfe:/home/erickn> server1.pl waiting for a connection hello
Does this prove I don't have a firewall issue?

Update:
this test shows me using port 4444 instead of 3333. However, I have also run it as 3333 and I get the same results.

Replies are listed 'Best First'.
Re^3: DBI Proxy connection prob
by tachyon (Chancellor) on Oct 04, 2004 at 23:30 UTC

    Well it proves connectivity on port 4444 which is not what you were using. This is pedantic but important. To prove that you can connect to isfe:3333 you actually need to connect to isfe:3333. You don't need a script, just telnet will do. You will either see it flip to a blank screen (or a header message in some cases but not this one) or give you a connection timed out message. You can open or firewall any port so it is an important sanity check.

    Anyway assuming that all is connective on 3333 the it is time to RTFS. If you grok the RPC::PlClient source around the line noted or just for the error message you will see it comes from the new() function.