WorldVistA Connection Problem

[Jeffrey Fu]

Hi,

      I had downloaded and installed "astronaut-wv-server-beta-0.8-2.i386.rpm" package into my Fedora Core Linux server and when I am trying to use the TMG-CPRS client from windows to connect the server, it shows up that the SSH channel had been established with putty, but TMG-CPRS get a problem with the connection and terminated.

     When I trying to connect from the server itself use both "ssh -p 9260 localhost" or "telnet locahost 9260". It shows up something from xinetd (vista_client-port-xwb.sh is the RPC Broker?)had listened to the port 9260, but I won't get connected.

 

Is there any thing wrong with my RPC Broker configuration(I use the default Astronaut installation) or am I using the way I access the WV system is incorrect? Thanks for any reply about this issue.

BTW, I had tried turn down firewalls on both Windows client and Linux server, so there should not be some firewall problems.

 

Jeffrey Fu

[Jeffrey Fu]

[I, Valdes]

Jeffrey,
1) Try the ssh login again and see what you get with id: clientEHR and
password not#1sostrong
2) Are you using the rpm defaults or did you override the defaults?

Thanks! -- IV

[Jeffrey Fu]

Hi, IV

     When I start putty from windows, it printed the following message:

 

Using username "clientEHR"

Last login: Tue Nov 10 01:55:18 2009 from 192.168.0.102

Astonaut VistA SSH Tunnel...Minimize, do not exit or close.

 

it seems the SSH Tunnel had successfully established, but when I start TMG-CPRS, it said "connection lost" and terminated.

 

When I use Linux to command

 

ssh -p 9260 localhost

 

It respond with some SSH_KEY_EXCHANGE problem message

"ssh_exchange_identification: Connection closed by remote host"

 

Is there some things incorrect or I run the false command?

I use the default rpm installation settings

with GT.M in /opt/lsb-gtm/

and WV in /opt/worldvista/EHR/

 

thanks,

Jeffrey Fu

[I, Valdes]

I'll have to try to reproduce... -- IV

On Nov 9, 9:14 am, Jeffrey Fu <gsb...@gmail.com> wrote:
> Hi, IV
>      When I start putty from windows, it printed the following message:
>
> Using username "clientEHR"
> Last login: Tue Nov 10 01:55:18 2009 from 192.168.0.102
> Astonaut VistA SSH Tunnel...Minimize, do not exit or close.
>
> it seems the SSH Tunnel had successfully established, but when I start
> TMG-CPRS, it said "connection lost" and terminated.
>
> When I use Linux to command
>
> ssh -p 9260 localhost
>
> It respond with some SSH_KEY_EXCHANGE problem message
> "ssh_exchange_identification: Connection closed by remote host"
>
> Is there some things incorrect or I run the false command?
> I use the default rpm installation settings
> with GT.M in /opt/lsb-gtm/
> and WV in /opt/worldvista/EHR/
>
> thanks,
> Jeffrey Fu
>

[JohnLeo Zimmer]

On Mon, Nov 9, 2009 at 9:23 AM, I, Valdes <iva...@hal-pc.org> wrote:
>
> I'll have to try to reproduce... -- IV
>

Careful, Ignatio, we try to keep this list G-rated, what with VA employees, etc.

GpZ

Maybe on the VistA list...

[I, Valdes]

Best comment ever. -- IV

On Nov 9, 9:47 am, JohnLeo Zimmer <johnleo...@gmail.com> wrote:

[Butch]

LMAO, comedy that good, and that clean is hard to come by these
days.

On Nov 9, 10:47 am, JohnLeo Zimmer <johnleo...@gmail.com> wrote:

[Crawford Rainwater]

Jeffery:

What I suspect you did during your Fedora Core installation is accept
the default configuration for networks and firewalls. This will open
some ports like ssh (port 22) and http (80), but not "odd ports" like
for CPRS.

To confirm this, from the command line as either "root" (the user) or
via a sudoer, type in "iptables -L" which will list your current
iptables (the Linux "firewall" basically). If you see a ton of stuff
here, then my assumption is correct.

To remedy this with Fedora (or RHEL or CentOS) there is the "system-
config-securitylevel-tui" package which I believe will allow you to go
through and re-configure this like the install. Plan B is "iptables -
F" which will "flush" the iptables until a reboot is performed of the
main policies are changed (i.e., INPUT, OUTPUT, and FORWARD are not
"ACCEPT" for full access).

HTH.

--- Crawford

The Linux ETC Company
10121 Yates Court
Westminster, CO 80031 USA
voice: +1.303.604.2550
web: http://www.linux-etc.com

On Nov 9, 8:14 am, Jeffrey Fu <gsb...@gmail.com> wrote:
> Hi, IV
>      When I start putty from windows, it printed the following message:
>
> Using username "clientEHR"
> Last login: Tue Nov 10 01:55:18 2009 from 192.168.0.102
> Astonaut VistA SSH Tunnel...Minimize, do not exit or close.
>
> it seems the SSH Tunnel had successfully established, but when I start
> TMG-CPRS, it said "connection lost" and terminated.
>
> When I use Linux to command
>
> ssh -p 9260 localhost
>
> It respond with some SSH_KEY_EXCHANGE problem message
> "ssh_exchange_identification: Connection closed by remote host"
>
> Is there some things incorrect or I run the false command?
> I use the default rpm installation settings
> with GT.M in /opt/lsb-gtm/
> and WV in /opt/worldvista/EHR/
>
> thanks,
> Jeffrey Fu
>

[Jeffrey Fu]

Thanks for your advice Crawford, I will try your suggestions and see what happend.

I also suspect some firewall problem of this. The weird thing is that I have tried to set firewall disabled with Fedora setup program and shutdown the iptables service, which seems to totally get rid of the firewalls, but the problem still exist.

I have tried shutdown the "xined" service for which the "VistA TCP listener" was supposed to reside in, and then ssh or telnet to the port 9260, it shows different information compared to "xinetd" started, so I don't know if that is some problem with VistA TCP listener. As I do not have much information of how this xined wrapped TCP listener works, I can't test to see what is the problem. Anyway, thanks for your suggestion, I will try if that solves the problem.

 

Jeffrey

[Butch]

If he just needs to punch a couple of holes in the firewall then using
Lokkit should work as well. It's installed be default on RHEL and
CentOS, not sure about Fedora though. From the command line (as root)
type:
lokkit
Then you can add whatever other ports you need open on the firewall.

On Nov 10, 10:51 am, Crawford Rainwater <crawford.rainwa...@linux-