Folks, Installing samba 2.2.8a on a Solaris 2.8 machine for the purpose of mounting shared Unix file systems on W2K clients.
Completed basic install, and tested OK on the same network. However, when the W2K boxes are on a separate network, mapping the drive or using net use on the W2K box results in the dreaded "The network path was not found." message.. Traffic travels through at least four routers and two firewalls between the W2K box and the Solaris server. Physically, these machines are in different cities. I can ping both ways using ports 137-139, and 445. Ftp and telnet work fine. I am very light in the network knowledge area. What needs to be open on the routers and firewalls to allow samba traffic through? I do not have access to the firewalls or routers - I need to contact other folks in security organizations in two different companies to get updates made. Thus, I have limited ability to "try" something to see if it works. Is there a definitive document on how to troubleshoot network problems like this, or does someone have a step by step algorithm they use when facing this issue. Grateful advance thanks. I have been fighting this beast for four days now, and am now pleading for help. Steve Sims KBM -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
