🚀 go-pugleaf

Hi - I have an Access2 database system to upgrade to sql 7, 
unfortunately the client workstations are to remain 16 bit win 
3.11 running an access2 front end.
I have developed a beta system in my development environment 2 
NT4 Servers, one running sql 7 the other running sql 6.5. TCP/IP 
is the network protocol used, and access2 is communicating to sql 
7 using the 16 bit sql 6.5 drivers, with named pipes as the 
transport protocol. - this works well.
However on site, I can not get the client access2 database to 
communicate with sql7. I can ping the server from the client and 
visa versa. The servers shared drives are exposed on the network, 
and I used the CD drive on the server to install the sql 6.5 odbc 
driver, and tools on to the 16 bit client.
I can connect to the server using the 16 bit ISQL/w tool if I use 
TCP/IP sockets, and use the default 1433 socket, but Accrss2 
refuses to connect to a dsn regardless of its transport protocol.
I can create test and use a 32 bit odbc dsn on a windows 95 
workstation and connect up ok using named pipes, but when I 
attempt to connect using tcpip sockets , it fails.
If TCP/IP is not working surely I would not be able to ping 
successfully?
If another base transport protocol was being used  i.e. IPX SPX, 
or netbeui, Surely the 16 bit TCP/IP sockets ISQL/W connection 
would fail?
I am confused, and puzzled, any help or suggestions will be