>>>But anyway, all that has nothing to do with the fact that I can't find the NT server on the network.
>>
>>Make sure you use the builtin Winsock connection in Windows '95. Don't take what came with Instant Internet.
>
>I'll lose functionallity with Instant Internet if I don't use its WINSOCK.
>
>>
>>On your NT, have you used a domain name or a workground name. Is that name the same in your workstations?
>
>We set it up as a domain and I put that domain name in my Win95 network configuration.


If you are running Instant Internet you want to run non-TCP/IP
protocols on the LAN side of the box. The Instant Internet
converts betweeen IPX and TCP/IP, and has a side effect of
being a very effective firewall.

The proprietary winsock should not come into play for accessing
the NT Server from a Windows 95 workstation in a NON-tcpip mode.

I would set up one Windows 95 station to Netbeui and set up the
NT server the same with Microsoft Network turned on. If you
cannot browse with the network neighborhood function, then try
to map a drive from the 95 workstation by actually specifying
the share name \\theserver\adirectory . I have run into
some circumstances when using DNS to resolve network names that the system will not browse properly but will allow a name
to be specified.

If the Netbeui works, which it should because it is a simple test, then remove the netbeui and add ipx/spx protocols and
retest. You may need to use Netware 32 bit stuff that comes with windows 95 or download new vlms or drivers from
Novell. We are running pure TCP/IP here and are not
having this problem.