Pervasive

I am attempting an installation over a private VLAN that does not currently use NETBIOS naming anywhere in the infrastructure. I can see a line in the installation configuration file referring to NETBIOS: "MicroKernel Workgroup Engine\Version $from\Settings\NetBIOS Port Number=MicroKernel Workgroup Engine\Version $to\Settings\NetBIOS Port Number" Is there a way to disable use of NETBIOS and use DNS or IP Address to access the server from the client? Thanks!

The Server Engine does not support the use of NETBIOS -- this is exclusively a Workgroup Engine feature.  You should not have to do anything at all.

If you want to force the Client to use TCP, then start the PCC on the workstation and select "Configure Microkernel Router", which is just a fancy name for "Client".  Go to the Protocols tab and uncheck SPX and NETBIOS to keep them from being used.

Also, the section of the installation configuration file you referenced, [Registry Migration], is only used to migrate existing PSQL settings (set for versions of PSQL prior to v10) during an upgrade from that version to v10 or v11.

 

 

 

Thanks for your speedy response, Bill. I should have stated this another way: Some Summing Up: - Pervasive in this case is embedded in another product. - Server installed and working fine - Client on same subnet installed and working fine - Installation of Client on different subnet fails during installation of Pervasive. "Pervasive Cannot Reach DB Server". I am informed by tech support of the unnamed product that NETBIOS is REQUIRED for Pervasive to install. They will not help me further until I have NETBIOS running. Strange thing is, there is no WINS server configured on either network. Client on same subnet works just fine. I don't have the PCC or the CLI tool available under my limited install. Is there any way to reach inside the Registry (if that is where this config is kept) and twiddle the bits to force no SPX or NETBIOS?

 I can assure you that NETBIOS is not required for a Server Engine.

Suggestion: Try a command like this (with your own servername, of course):
    TELNET <servername> 3351
You should get a blank screen, letting you know that the connection succeeded.  If this works, then you should have valid connectivity.  You can also try testing with the Function Executor (WBEXEC32) to open a file on the server -- it should succeed.  If these fail, then you will need to fix the network routing, first. 

All of the registry settings can be found in HKLM/Software/Pervasive Software.  Look in the Communications Requester group for the Supported Protocols and change it to TCPIP.

 

Thanks again, Bill. It turns out that the product that embeds Pervasive requires that the host be resolvable by hostname only, and they interpret this as requiring NETBIOS. Untrue. By adding the DNS suffix to dns resolution, and specifying the hostname during installation, everything is now working perfectly. This was never a Pervasive issue, it was identified as such by the product company. Best, Ott