![]() |
![]() HP OpenVMS Systemsask the wizard |
![]() |
The Question is: We are using Compaq Advanced Server 7.2A on an Alpha station running 7.2-1 with TCPIP 5.0A as the only enabled network for Advanced server. When we try and connect from either Windows NT or Windows 98 clients using the \\IP address\sharename notation, the client is unable to access the Advanced Server but tries to access TCPIP's Portmapper and PCNFS services. If we access the server using \\unc name\share name, then we connect ok, what have we missed in our configurations? The Answer is : When you try to access the server using the \\IPaddress\sharename notation, the client tries to establish a TCP session to TCP port 139 on the specified server IPaddress; to the NetBIOS session port. The target NetBIOS connection name is specified as '*SMBSERVER', which is a special NetBIOS name that is silently claimed (without any real name claim or registration) by all Microsoft Windows NT 4.0 hosts and by all servers that emulate the Windows NT 4.0 behaviour. These servers will all honor a connect request to the NetBIOS name '*SMBSERVER'. The OpenVMS Wizard has not seen a situation where a client tries to access the Portmapper and the PCNFS services. The only possiblity that the OpenVMS Wizard can presume involves an attempt to connect to a server that is multi-homed (i.e. has more than one network interface, and when you specify \\servername\sharename, the IP address of \\servername is different than the IP address you are using when you specify \\IPaddress\sharename). In this case, the \\IPaddress is for an interface which is different than the interface which \\servername resolves to. The Advanced Server package will only operate over one of the available network interfaces. Should you try to access a share on this server using the IPaddress of the interface that is not being used by the Advanced Server, then this might trigger a situation where the client tries to access the Portmapper and PCNFS services. If this does not appear to be an explanation of the reported behaviour, please contact your Compaq Customer Support Center. It will likely be necessary to obtain network protocol traces and related supporting information as part of the resolution process.
|