Nancy --
Isn't the new broker preferable to the old one, and isn't that what Marc
is trying to run, if he is opening up port 9200 on the router?
-- Bhaskar
On Thu, 2006-01-12 at 17:07 -0500, Nancy Anthracite wrote:
> Also, check the log from D VIEW^XWBDLOG to confirm that the new broker is not
> being used and that is why you cannot connect. If the new broker is being
> used, you will see a lot of [XWB], i.e., XWB in square brackets, and if it is
> the old, all but the first one will be in curly braces {XWB}.
>
> On Thursday 12 January 2006 04:45 pm, Nancy Anthracite wrote:
> Try stopping the Broker and restarting with D ^ZISTCP^XWBTCPM1(9200) and
> stopping when you are done with D STOPALL^XWBTCP. The broker may be hard to
> stop. You may have to kill the process, but if you can do it another way, it
> would be preferable.
>
> On Thursday 12 January 2006 04:16 pm, Marc Krawitz wrote:
> I've been able to get VistA and CPRS running successfully within my internal
> network (at least until this power outage occured). However, I still cannot
> get CPRS to connect to the VistA server when CPRS is running outside of my
> network (e.g. on the public internet). I opened up port 9200 on my router
> to no avail. Any ideas? In both the internal and external scenarios, CPRS
> is running on the same machine (e.g. my laptop).
>
> Thanks,
>
> Marc
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
