Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

Patient Portal/Secure Messaging

General Discussion

Last Post by [email protected] 10 years ago

2 Posts

2 Users

0 Reactions

60 Views

RSS

Anonymous

(@Anonymous)

Posts: 0

New Member Guest

Topic starter

I would love to hear from someone who has gone through the same problems I am having right now...

PPSM has been installed for a few months now and has never gone live. We have a range of multiple external ip addresses. XXX.170 - XXX.174. Our Firewall is using XXX.170 and we were planning on using XXX.171 for use with ppsm. We have it registered with our ISP and domain registrar to resolve portal.gaspa.com to xxx.171.

Here is the issue:

I apply a rule on our firewall for XXX.171 to resolve to the internal ip address for the server running ppsm. As soon as I apply this rule the server is unable to browse the internet and we are unable to browse to the portal website. I am however able to ping say google.com from the server in question.

I have taken a laptop and configured it to use the XXX.171 address directly with no problems at all. So we were told it must be issues with the firewall.

Last night we had the firewall replaced with a brand new beefy Cisco ASA and the same issue remains.

If anyone has any insight, questions, been through this or wishes moral support I can be reached by email at [email protected]

Thanks in advance!

Posted : April 25, 2012 3:16 am

[email protected]

(@dcambiousnellc-com)

Posts: 18

Eminent Member

We had sort of a similar problem were some of our e-mails were not reaching their destinations. No error messages, the notification just didn't show up in the recipients inbox. It turned out that our ISP was blocking it. they had to make some kind of configuration modification on their end. It may be worth exploring your issue with your ISP.

Posted : January 7, 2015 12:56 pm

Share:

24 Forums
9,940 Topics
39.9 K Posts
2 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0