Bill, Thank you for the prompt response. Here's what I see:
>Check the Event Log for any error messages when you are starting the >server. If there is a problem starting the server, it will be logged >there. You mention problems with Telnet and Web servers; these use >low-numbered ports. You might try changing the servers to use port >numbers greater than 1024. If the higher port numbers work, it would >indicate a problem with InterMapper's use of the 'intermapperauthd' >tool to open privileged ports. According to the Event Log, servers start normally, no matter what port I put them on >Check that you haven't inadvertantly activated the firewall on your >mac. In the Terminal , type "sysctl net.inet.ip.fw.enable". If the >firewall is enabled, the value will be 1. You can double-check the >configuration of the firewall by typing "sudo ipfw list". In 10.2, >the system preferences control panel allows you to configure the >firewall; I believe you need a product like BrickHouse to do this on >10.1.5. Here are the entries I see for net.inet.ip.fw: net.inet.ip.fw.debug: 1 net.inet.ip.fw.one_pass:0 net.inet.ip.fw.verbose: 0 net.inet.ip.fw.verbose_limit :0 for ipfw list: 65535 allow ip any from any >Finally, you can verify which programs are listening on which ports by >typing 'lsof -i' in the Terminal. Type 'sudo lsof -i' to get a listing >which includes programs from all users. lsof -i shows servers listening on whatever port I set the servers to I can launch a browser on the Mac that's running InterMapper and I am prompted for a login, and I get the expected pages. Pat
<<winmail.dat>>
