This is not the answer, but we will find it soon. You have the benefit of being there and seeing first hand what is, and I am at a disadvantage for that. Know that communication is the key to all ...
Given: The LAN uses the LinkSys box as a gateway, and for DHCP. An NT4 Server is providing RAS to dialups.
By the way this comment is very contradictory and points to the problems and so to the solutions -> {I only have TCP/IP protocol configured for RAS. I configured an IP scope for RAS clients within the DHCP scope of the router. The RAS has WINS running on it. I'm not using DNS on the LAN.} WINS is not part of tcp-ip, and DNS is required for even simple access to tcp-ip based resources ...
Have you reserved the ip numbers for RAS with the linksys box, and told all the machines to use DHCP for WINS reolution? See, you really have two dhcp servers and possibly two WINS servers running. When they co-respond properly the trouble will go.
Have you searched the server for hosts and lmhosts files, no longer needed or out of date? IF that doesn't straighten it out then let's get physical; I am trying to map this out to understand the layout. Where is the linksys box in relation to the server? (ie: connected to the server on nic2, connected to a hub on an MDX or WAN port, connected to somewhere else ...). OK, now to path not found - You say the RAS client can auto-create the drive mapping to the server but not access the path afterwards. What is auto-create in this context or what procedure is followed? Even in a small network it can take five minutes or more for the shares to be enumerated and distributed, (depending on a few things that are irrelevant at this stage but could prove interesting later as you tune the systems). Also, I have seen where a win3x or win9x machine running Client for MicroSoft Networks needed to make a shared directory and offer it on the network before it could browse i