Article ID: KWin0089
Added: 4/8/2009 SS/EL
Updated: 8/05/2009 SS/ML (See **)
Stat 3105 and/or 3103 Trying to Log Into RDP
This error can be seen in RDP-DOS or RDPWin and is a
result of the pervasive client not being able to connect with the server. This
is the definition from PSQL 10.0:
3105: No available transport protocol for the Pervasive Network
No transport protocol that is common to both the target server engine and
clients is available. For example, this status code could be caused by a client
using SPX when the server engine only has TCP/IP available. Check the Supported
protocols setting within the Communication protocols option for both the client
and server. For more information on Communication protocols, refer to Advanced
We’ve seen this several times where the Windows firewall is blocking
pervasive. Turn off the windows firewall on the workstation and/or the server.
- Navigate to Start | Settings | Control Panel and double-click on Windows Firewall.
- Select the Off radio button on the General tab.
- If you want to leave the Windows Firewall on, you can
add pervasive and RDP in the exceptions sections.
- If turning off the Windows Firewall does not allow you to open RDPWin,
there are other issues to network connectivity for Pervasive.
Another thing you can try is opening up, or allow traffic on the following
ports which pervasive will use:
Pervasive PSQL communicates through three ports. Your firewall(s) and
routers need to allow access to the following ports for remote access with
the server database engine:
- 3351 for the transactional interface
- 1583 for the relational interface
- 139 for named pipes (see note)
- Test DNS using NSLOOKUP
- Have the network
administrator check/modify the DNS settings for the workstation to make sure it
is pointed to the proper DNS server.
- To troubleshoot DNS:
- Go to the Troubleshoot DNS document for IRM.Net
any reference to IRM with the current workstation.