Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ProjectWise
  • Product Communities
ProjectWise
ProjectWise Design Integration Forum ProjectWise - Datasource not showing?
    • Sign In

    • State Verified Answer
    • Replies 6 replies
    • Subscribers 58 subscribers
    • Views 8840 views
    • Users 0 members are here
    • Datasource not displaying
    • ProjectWise
    • datasources

    ProjectWise - Datasource not showing?

    jcallicott
    Offline jcallicott over 9 years ago

    I am trying to experiment with PW connectivity external to our company.  We are running PW 08.11.11.574.

    Our clients will connect-->Gateway-->Int

    Today, we got a FQDN and external IP set up for our Gateway.  The FQDN on Port 5800 is mapped to resolve to the internal server name and IP.

    On the servers, port 5800 is open both ways, and no firewalls are blocking access.  The Pcs internal to the comany simply enter in the IP of the gateway server in the PW network settings, and can see the datasources. 

    However, I'm trying to test external connectivity and I can't get it to work.  Formy config settings, I"ve enterted in  The data sources won't show.  No restrictions (by IP or computer name) exist on the datasources.  If I perform a pwping to the FQDN, it works.  Hop 1 shows up to the internal server name, so that's good.  

    I also tried the socket analyser tool, again to the FQDN on Port 5800. 

    I also made sure my firewall/anti-virus for this client PC were turned off. Nope.  I tried disabling UDP.  No dice. I double-checked the dmskrnl files for both my int and gateway servers.  They match what is shown in the guide.  Curious, I dug into the pwc.log.xml file, and after commenting out some items got this result produced:

    2014-08-29 03:31:03,207 ERROR [0x00001104] pwise.socket - Error -10060 on socket 1720 at func: socket_connect line: 1112
    2014-08-29 03:31:03,207 ERROR [0x00001104] pwise.socket - failed to connect socket:1720 to addr:'192.168.22.29' port:5800 flags:0
    2014-08-29 03:31:03,207 ERROR [0x00001104] pwise.socket - Error -10038 on socket -1 at func: socket_close line: 964
    2014-08-29 03:31:03,207 ERROR [0x00001104] pwise.netapi - Error -11501 "PXPW_INT" reported at func: request_establishSocketConnectionToServer line: 146
    2014-08-29 03:31:03,207 ERROR [0x00001104] pwise.netapi - Error -11501 "failed to connect to server" reported at func: request_openConnection line: 329
    2014-08-29 03:31:03,472 ERROR [0x00000824] pwise.server - Error -11501 "ServerConnectHandler" reported at func: ServerConnectHandler::Invoke line: 1058
    2014-08-29 03:31:03,472 ERROR [0x00000824] pwise.netapi - Error -11501 "failed to execute connect request" reported at func: request_openConnection line: 339
    2014-08-29 03:31:03,472 WARN [0x00000824] pwise.netapi.discovery - DS query to server '68.225.129.30' failed, status = -11501

    So it looks like the client request may well be getting to my int server from the gateway., which makes the datasource not displaying... weird.  

    The clients are Windows 7 Pro, the servers are Windows Server 2012.  

    Ideas are appreciated... thanks!

    • Sign in to reply
    • Cancel

    Top Replies

    • Jeff Burrill
      Offline Jeff Burrill Fri, Aug 29 2014 11:57 AM +1
      Unknown said: The FQDN on Port 5800 is mapped to resolve to the internal server name and IP. Port forwarding from external to internal IP through a firewall not work. Further, the gateway server must…
    • jcallicott
      Offline jcallicott Fri, Aug 29 2014 12:22 PM in reply to Jeff Burrill +1
      Jeff, I'm not sure I follow what you are saying. By DMZ, do you mean the gateway server must have its own firewall and be outside of the main firewall? Also, what would the updates to the dmskrnl files…
    Parents
    • Jeff Burrill
      0 Offline Jeff Burrill Fri, Aug 29 2014 11:57 AM

      Unknown said:
      The FQDN on Port 5800 is mapped to resolve to the internal server name and IP.

      Port forwarding from external to internal IP through a firewall not work. Further, the gateway server must be in the DMZ. Once it is in the DMZ, the dmskrnl.cfg on both Integration and Gateway will need to be updated with proper routing information.

      See the Troubleshooting ProjectWise Gateway or Connection Server tech note for more details.

      Please note that I post here on a voluntary basis and am not a Bentley employee. 

      • Cancel
      • Vote Up +1 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • jcallicott
      0 Offline jcallicott Fri, Aug 29 2014 12:22 PM in reply to Jeff Burrill

      Jeff, I'm not sure I follow what you are saying.  By DMZ, do you mean the gateway server must have its own firewall and be outside of the main firewall?

      Also, what would the updates to the dmskrnl files on the servers look like?  Do you have sample entries?

      • Cancel
      • Vote Up +1 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Kevin van Haaren
      0 Offline Kevin van Haaren Fri, Aug 29 2014 3:45 PM in reply to jcallicott

      I've got a gateway server setup using a port forwading setup. It works fine with this configuration:

      In [TeamMate] section set the ServerName and ServerIPAddress. Set these to what the external clients will use. The comment doesn't mention port fowarding scenarios, but it works for them too.

      ;
      ; Name and ip address to use when advertising server. When running in a clustered
      ; environment set these values to the cluster name and cluster IP address. If this
      ; server is on cloud or clustered environment, please set "ServerIPAddress" to your
      ; external host name (FQDN). This way the server can know the external IP address and
      ; report it to clients.
      ;
      ServerName=external_fqdn
      ServerIPAddress=external_ip

      In [Gateway] tell external clients to connect to internal servers via the external gateway:

      [Gateway]
      ; endpoint=first_server
      integration_server=fqdn

      In [Routing] tell the local server how to connect to the endpoint. If it will connect directly, just list the port to use.

      [Routing]
      ; endpoint=port,server
      ; endpoint=port
      integration_server=5800

       

       

      Answer Verified By: jcallicott 

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Reject Answer
      • Cancel
    Reply
    • Kevin van Haaren
      0 Offline Kevin van Haaren Fri, Aug 29 2014 3:45 PM in reply to jcallicott

      I've got a gateway server setup using a port forwading setup. It works fine with this configuration:

      In [TeamMate] section set the ServerName and ServerIPAddress. Set these to what the external clients will use. The comment doesn't mention port fowarding scenarios, but it works for them too.

      ;
      ; Name and ip address to use when advertising server. When running in a clustered
      ; environment set these values to the cluster name and cluster IP address. If this
      ; server is on cloud or clustered environment, please set "ServerIPAddress" to your
      ; external host name (FQDN). This way the server can know the external IP address and
      ; report it to clients.
      ;
      ServerName=external_fqdn
      ServerIPAddress=external_ip

      In [Gateway] tell external clients to connect to internal servers via the external gateway:

      [Gateway]
      ; endpoint=first_server
      integration_server=fqdn

      In [Routing] tell the local server how to connect to the endpoint. If it will connect directly, just list the port to use.

      [Routing]
      ; endpoint=port,server
      ; endpoint=port
      integration_server=5800

       

       

      Answer Verified By: jcallicott 

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Reject Answer
      • Cancel
    Children
    • jcallicott
      0 Offline jcallicott Fri, Aug 29 2014 4:15 PM in reply to Kevin van Haaren

      Kevin,

      Thanks for this info!  Yes, ours is a port forwarded configuration.  We have the FQDN, port 5800, re routing to our Gateway Server's internal IP address.

      We would edit the dmskrnl.cfg on the gateway with this info, correct?  Does your scenario work when the Gateway is not in a DMZ?

      Thanks again!

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • jcallicott
      0 Offline jcallicott Fri, Aug 29 2014 5:38 PM in reply to jcallicott

      Kevin, thank you!

      Your tip turned the trick.  I shared your advice with Bentley as I was talking with them and they thought it a good course of action too.  

      Once we advertised the server name and added the line of

      intergtation=external IP of Gateway

      it worked!

      Thank you so much!

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Jeff Burrill
      0 Offline Jeff Burrill Fri, Aug 29 2014 5:56 PM in reply to jcallicott

      I always thought there should be a way to get port forwarding to work, but I could never find such a configuration documented by Bentley and just figured something in PW prevented it. Thanks for sharing the "secret" Kevin. Bookmarking this one for sure!

      Please note that I post here on a voluntary basis and am not a Bentley employee. 

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel

    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies