NWAttachToFileserver problem

Hi, 

I am preparing to bring our Database server to a cluster I already 
implemented it on a test network and I am having a problem with an old 
VB 3 application that runs on a thousand remote stations. This 
application uses the NWAttachToFileserver call and then creates a map 
drive to access the data. 
When I try to attach to the "virtual server" created by the cluster I

receive the UNKNOWN FILE SERVER error. 

The cluster enables the virtual server to be accessible from the 
Bindery and I thought that the NWAttach call would use that bindery. 
Does anyone have experience in accessing a cluster resource from VB 3? 
Or maybe knows what that call is looking at to find the server? 


I will surely appreciate any help, 


Thanks, 


David 

<dbertran@girosol.com> wrote in message 
news:mZDqf.160$012.145@prv-forum2.provo.novell.com...
> Hi,
>
> I am preparing to bring our Database server to a cluster I already
> implemented it on a test network and I am having a problem with an old
> VB 3 application that runs on a thousand remote stations. This
> application uses the NWAttachToFileserver call and then creates a map
> drive to access the data.
> When I try to attach to the "virtual server" created by the
cluster I
> receive the UNKNOWN FILE SERVER error.
>
> The cluster enables the virtual server to be accessible from the
> Bindery and I thought that the NWAttach call would use that bindery.
> Does anyone have experience in accessing a cluster resource from VB 3?
> Or maybe knows what that call is looking at to find the server?

If I remember correctly, this function was rendered obsolete around 1998 
when the new connection APIs (prefix NWCC) were introduced. It almost 
certainly requires IPX for server location. I suggest replacing it with 
NWCCOpenConnByName.

John
DevSup SysOp 24