Mark, Comments below.
--- Mark Street <[EMAIL PROTECTED]> wrote: > I am trying to troubleshoot remote connection of > CPRS. This is the same > problem I was experiencing with my first > installation of the HUI VistA. I > can connect to my vista server with both CPRS > through wine and CPRS > running on windows on my private network > (192.168.1.0/24). This sounds very much like the problem we were having at the WorldVistA conference. I think we decided that it was the old "CPRS can't connect through a firewall/router problem." Supposedly newer versions of CPRS have been modified to fix this problem. I had a patch that specified a callback port--but I don't think it ended up solving the problem either. > > If I try to connect from outside my private network > (my server has two > interfaces, int. and ext.) I don't get a sucessful > connection, I do get a > file created XWBTCPL.mjo in vista's home dir the > error message in the file > states "HOME DEVICE DOES NOT EXIST IN THE DEVICE > FILE". I have been getting .mj0 files in my home directory too. I don't know what they are about. Bhaskar saw them and didn't seem surprised or concerned. Mine have 0 length. > > So I go back to my configuration and recall that we > configure 4 devices. > Just for kicks I go in and see if there is a 'home' > device... from the 64 > or so devices....none noted. Then I say well, it > has to be one of the > devices I configured. > > CONSOLE > TELNET > HFS > NULL > > From what I understand only 1 device can be the > signon system device. > > SIGN-ON/SYSTEM DEVICE: ?? > > Answer 'yes' if this device is the primary device > amoung those > device entries that have the same $I and VOLUME > SET(CPU). > If answered 'YES', this field identifies that this > entry is the primary > device among those device entries that have the same > $I with the same > VOLUME SET(CPU). > > Among those device entries that have a common $I and > CPU, only one of > these entries can have this field set to 'YES'. If > none of the common > device entries are set to 'YES', the default device > will be identified by > the first device on the CPU x-ref. The default > device is used when the > device handler is invoked with $I as the device to > be selected. > > Choose from: > 1 YES > 0 NO > > Does anyone know how I would set the HOME DEVICE and > is that the same as > the SIGN-ON/SYSTEM DEVICE? > I got confused about this a few months ago. I asked, got my question answered, and then the problem seemed to go away. I can't remember what was said. But you might search for sign-on device, or home device. I think that entering User's Toolbox-->Edit User Characteristics will allow you to specify whether to ask for the signon device each time. Otherwise it uses the device that you used last time. I'm not sure if I am answering your question directly. But I don't think this has anything to do with your inability to connect. What we found was that the server was getting the intial connect request from CPRS. But when it tried to call back, the attempt was block somehow. CPRS never got a satisfactory reply and dies. > Maybe I need a little clarification on how RPC > Broker interfaces with the > different devices when a connection comes in on the > interface where RPC > listener runs. From what I recall i can setup more > than 1 listener, so > technically I could have a listener on different > ports for the same > server. The RPC Broker doesn't have anything to do with the sign-on devices, as far as I know. It's not like linux where the users "signs in" and is given a process shell with an interface etc. Instead, I believe RPC broker calls just return the requested information from the database. > > The GT.M specific devices are; > > GTM-UNIX-BROWSER HFS/CRT (GT.M-Linux) > /tmp/ddbr.txt > GTM-UNIX-CONSOLE Console (GT.M) > /dev/tty > GTM-UNIX-HFS Host File Server (GT.M) > /home/huivista3/tmp/hfs.dat > ROU > GTM-UNIX-IMAGING WORKSTATION BROKER > /usr/local/spool/ws.dat > GTM-UNIX-MESSAGE P-MESSAGE-HFS xmhfs.dat > xmhfs.dat > GTM-UNIX-NULL Bit Bucket (GT.M-Unix) > /dev/null > GTM-UNIX-TELNET TELNET /dev/pts/ > GTM-VMS-MESSAGE P-MESSAGE-HFS HFS (GT.M) > FILE => MESSAGE > XMHFS.DAT > > One other point on this, when I am editing my > devices I cannot change the > GTM-UNIX-HFS device from > /home/huivista3/tmp/hfs.dat, it prompts me with a > Replace? at the end of the line and does not let me > change the value. Hmm... Try making a copy of the record and editing that. Or look at the input transforms. By the way, do you have VPE installed? The time you spend gettting it installed will be easily paid back by the ease you call look at all the details of the fields etc. > > Am I supposed to have the hfs.dat database set > somewhere? > I don't think so. Good luck Kevin > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT > Products from real users. > Discover which products truly live up to the hype. > Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Hardhats-members mailing list > Hardhats-members@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hardhats-members > __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
