Kbase 13580: NT Netbios Call to Server 1998, Server Unavailable 733 WFW
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
NT Netbios Call to Server 1998, Server Unavailable 733 WFW
Netbios call to server {servername} retrying (1998)
appearing 3 times, followed by:
Error 733 : "server {servername} not available" message
can be caused by three things when it occurs with
a MS-Windows or Windows for Workgroups Client to a NT
Server. (This applies to both V6 and V7 on the server
and client).
The three most common causes are the following:
1) The values for the database name and the -S are not
correct on the server startup and the client connection.
These values are case sensitive.
Example that will work:
server: _mprosrv c:\progress\test.db -S test
client: _prowin test -S test -H PC1
Example that will NOT work:
server: _mprosrv c:\progress\test.db -S test
client: _prowin test -S TEST -H PC1
2) On the Windows for Workgroups client, the first instance
of Netbios is NOT Netbeui/Netbios. Progress will use the
first instance of Netbios installed on the client machine.
If, for example, the network drivers for both Novell with
Netbios and Netbeui/Netbios are installed on the same client
and Novell's Netbios is the first instance of Netbios installed,
Progress will use this implementation of Netbios.
The NT Server will use Netbeui/Netbios by default, therefore
this must be used by the Progress client as the first
instance of Netbios.
To check to see what protocols are installed on the Windows
for Workgroups client, simply click the Network Setup icon
located in the Network Group. Make sure the first instance
of the Netbios protocol is "Microsoft NetBEUI".
3) On the NT server machine, the Netbios Interface is on a
different LANAbase than the client. By default it should be
on LANA 0. To check on the NT machine what LANAbase Netbios
is configured for, do the following:
From the Program Manager, select Control Panel, then select Network.
From the list of Installed Network Software, select NetBIOS Interface.
Click on Configure.
From the list of Network Routes, select
Nbf-<your network interface card>.
Now look at the Lana Number window.
If the Lana Number shown is not 0, you must change it to 0.
Note that if another Network Route (i.e. NwlnkNb or NetBT) is set to
zero, you'll have to renumber it, by selecting it and typing in a
non-zero Lana number. Once you have renumbered the conflicting Network
Route, select Nbf-<your NIC> and type in 0 for the Lana Number.
Progress Software Technical Support Note # 13580