Can't browse or map NT from workstation

I assume your using TCP/IP and NWLink protocols on Win95/98 clients. Take a look at how the clients are logging on to the network. Change one to "Client for Microsoft Networks". Make sure the workgroup name matches the Domain you're logging on. Thensee if logging on through that will allow it to see the NT Servers and vise versa. And the obvious, make sure you have shares on the workstations (File and Print Sharing installed) for reverse troubleshooting from the server.
If this works, but theclients cannot see the Novell servers, you may have to set up one of the NT Servers as a Gateway to the Novell resources.

"the three domains" caught my attention here. While NT workstation can "see" other domains, WIN95/98 will only see the domain that is listed in it's "workgroup" setting in the Network section of the control panel. Also having Wins services running on one server may help (assuming you're using TCP/IP). Really need more info to point you in a posotive direction.. Are these NT servers PDC+BDC or all stand alone ? All separate Domains as suggested in you're question ? In any case past experience has showed that it is much easier to get Clients Logging into NT (NT Domain accounts) to see a Novell server than getting clients logging into a Novell server to see NT servers .. especially if those NT servers are set up as Stand-alone servers. If youwant full functionality between NT and Novell you really need to purchase the Novell gateway option.

I assume that the three domains are for security reasons - one external (Web host), one internal (DB server), and the Proxy.

First, make sure that the users are logging into BOTH networks (Novell and NT). You may want to try installing the NovellClient supplied by Novell, instead of the default MS client (there are some known issues with this). Second, double check the Trusts between domains, and the user security that is required because of them. Third, make sure that the Proxy isn't blocking access to the NT Network (I saw someone do this once, and it took him almost a week to figure it out).

I like the idea of getting Wins to work. But as a short term trouble shooting technique I would use the LMHOSTS file in the \winnt\system32\drivers\etc. use the #PRE (Case sensitive) and NBTSTAT -R (case sensitive) to reload, then try ping the netbios name, if that works, then try run \\netbios (machine name).

This question was auto closed due to inactivity