web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Unable to connect to t...
Microsoft Dynamics GP (Archived)

Unable to connect to the Remote server message

(0) ShareShare
ReportReport
Posted on by Community Member

We just set up a new gp 2016 environment to which we migrated the data from our 2013 server.  Now, we are getting a message within GP 2016 and GPWeb 2016 when using the applications. The message is "Unable to connect to the Remote server" and pops up after a long delay.  If you click on the 'OK' button your page will usually open.  The message comes up when the application is querying data from the sql server.   It is happening from any workstation you use and usually on the same screens. 

Has anyone run into this and do you have a solution.

Thanks.

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    We have narrowed it down a little bit.  It seems we are only getting the unable to connect message when we are in the Purchasing module.  I cannot figure out what would be unique about that.

  • Community Member Profile Picture
    Community Member on at

    Narrowed it down a little more.  With the SQL server firewall turned off we do not experience this issue.  When we turn the firewall back on we receive the unable to connect message.  Do any TCP or UDP ports need to be open on the firewall other than TCP 1433?

  • Community Member Profile Picture
    Community Member on at

    Alright, we found out how to solve this issue but am not sure why we had to do this.  What solved the problem was opening another hole in the Windows firewall on the database server.  We had to open port 80.  So now we have port 80 and 1433 opened for SQL Server.  Does anyone know why we had to do this?  

    When looking at the traffic between a GP client and the database server the client was sending out packets on port 80 identified as SOAP traffic.  So once we opened port 80 on the database we no longer get the "Unable to connect"  message.

  • Community Member Profile Picture
    Community Member on at

    Thank you for narrowing that down HastingsJim!  We've got a client with the exact same problem - down to the module.   We'll give your solution a try.  

    Not sure why the solution worked for you though, sorry! 

  • Bill Campbell Profile Picture
    Bill Campbell 12 on at

    Jim good day - I am not sure of the exact reason - but I was wondering if you might have any 3rd party applications running along with the core GP Purchasing application?

    I have not found that it was necessary to pop the 80 port open but have opened the 433 ( not 1433 ) not sure if that is my configuration or something unique I missed.

    Good luck and I would be interested to know what else you learn.  Posting of self learned solutions helps others.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans