Overview

The ProjectWise Gateway Service is used to enable external ProjectWise Explorer clients (individuals located outside the company's firewall) to reach a ProjectWise Integration Server residing on the secure local network inside the company's firewall.

This guide will help aid in troubleshooting some common issues.

Notes

• This requires a gateway configuration be set up on the Gateway and Caching servers. 
• It is necessary that the gateway machine be configured to advertise its IP address as an address that the client can connect to.
• If you are using thick client access, the gateway machine should be configured to advertise the public IP. 
• If a client is using the gateway as both a Web Server and a thick client Gateway Server, the thick client needs to associate the public IP with the gateway machine. 
• There may be times, if the Web Server is inside a DMZ and is configured to access the Application Server via the gateway, it may be unable to access the gateway via the advertised public IP.
• A Web Server, on the other hand, will be configured to connect directly to the Application Server via the ProjectWise Network Control Panel applet. 
• The existing routing entries on the Application Server will not need to change, and there should be no need to add or change any NameResolution config file information on the Application Server's dmskrnl.cfg file.
• ProjectWiseV8i client connections through ProjectWise Gateway Service are not supported using IPv6.
• If you installed the ProjectWise Gateway Service (which does not require a license), but then later enabled the file caching feature in that service's dmskrnl.cfg file you will need a license because this is essentially turning a ProjectWise Gateway Service into a ProjectWise Caching Server.

Getting Started

The following section provides a list of items to check when troubleshooting ProjectWise Gateway issues.

1. Port 5800 needs to be open bi-directionally through all firewalls. 
2. In the dmskrnl.cfg file, Disable Allow/deny statements until you know that caching/routing works.
3. Gateway Service can NOT be installed on computer on which ProjectWise Integration Server or ProjectWise Caching Server is already installed.

Configuration 

The following section shows the basic dmskrnl entries needed on the Gateway Server.

Check the following sections of the dmskrnl.cfg for each Caching/FTS Server and Gateway Servers under c:\ Program Files\Bentley\ProjectWise\bin\

[Name Resolution]
Ip = Gateway/Connection Server
Ip = Integration Server
Ip = Caching Server

[Gateway]
Integration Server=Connection/Gateway Server
Caching Server =Connection Server

[Routing)]
Integration Server =5800
Caching Server=5800

On Gateway Server Only
ConnectionSrv=1

[Cache]- Caching Server only
Enabled=true
Storagepath=c:\cache
Limit=200

The ProjectWise Network Control Panel

The ProjectWise Network Control Panel is used to point the client machine to use specific network settings when connecting to ProjectWise servers. ***Double check the following two items to ensure they are configured correctly and that the hostname is spelled correctly.

1. DNS and Datasource Tabs point to Gateway\Connection Server-Port 5800
2. UDP checked for Disabled on both tabs

Trouble Shooting Potential Issues

Firewall

When the Windows Firewall is ON (recommended) on the ProjectWise server computer that is publishing datasource lists, the firewall will block the default ProjectWise broadcasting and listening ports of 5799 and 5800.

• This means that clients of the server (ProjectWise Administrator, ProjectWise Explorer, ProjectWise Web Parts, etc.) will not be able to see that server or its datasources even if they are located on the same computer, and even if you have defined connections to the server through the ProjectWise Network Configuration Utility.

• On each of the ProjectWise Integration Server, Caching Server, and Gateway Service computers you will need to add ports 5799 and 5800 to the exception list of the Windows Firewall.

- Select Control Panel > Windows Firewall.
- The Windows Firewall dialog opens. The General tab displays whether the firewall is on or off.
- Assuming it is ON (recommended), select the Exceptions tab and click Add Port.
- To add port 5799, set name to "ProjectWise UDP", set port to 5799, and set protocol to UDP.
- To add port 5800, set name to "ProjectWise TCP", setport to 5800, and set protocol to TCP.

DNS

There may be instances when DNS is a factor. Therefore, it would be best to complete the (Name Resolution) section of the dmskrnl.cfg file.

1. Verify that each server can resolve either the short names of the other server or use the FQDN (Fully Qualified Domain Name) for each server. 
2. If you choose FQDN, the storage area for each data source must also be updated to a FQDN. ProjectWise needs to be able to resolve the servername listed in the storage area setup just as it must resolve the name of other ProjectWise servers.

All three of the commands should produce similar results, in a slightly different format.

Open a command prompt window and enter each command listed below.

• Nbtstat -c 
• Nslookup (hostname)
Nslookup (ip address)
• Ipconfig /all

Nbstat-c Displays protocol statistics and current TCP/IP connections using NBT
(NetBIOS over TCP/IP) and lists NBT's cache of remote [machine] names and respective IP addresses

NSlookup -will verify that the hostname and ip address being configured is not conflicting with any other machine

ipconfig /ALL -Allows to see both the computer name and if WINS is configured. 
**Please note your results

Connectivity

Make sure the gateway service is started and run the ProjectWise Tool "Socket Analyzer" to ensure you have a connection.

The Windows Socket Analyzer tests the connection to the remote host. (See the Help Section in ProjectWise Explorer for step by step instructions.)

PW PING

The PWPING utiliy provides detailed information on the connectivity between the client machine and server or from server to server. If you are experiencing problems, turn up the logging as indicated below, run the pwping command and review the logs.

1. Turn up logging utility by going to c:\program files\Bentley\ProjectWise\bin\pwping.log.xml . Open this file with NotePad. 
2. From the Menu, do an Edit, Replace. 
3. In the field "Find What" type "warn" and Replace with "all". 
4. Select Replace All, close the window and Save the file.

Go to a Command Prompt and browse to c:\ Program Files\Bentley\ProjectWise\bin\ 
Type Pwping - (hostname or ip of the remote destination)

Ping from each hop: Caching to Gateway, Gateway to Integration

The pwping.log file generated from the pwping will be located at c:\documents and settings\user that you are logged into the server as\application data\bentley\logs

See Also

Product TechNotes and FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!