We have a LAN consisting mostly of Mac OS X systems with a few XP systems. The XP systems on the LAN have no trouble connecting to our OSX file server. The LAN is behind a firewall, but port 548 is open so staffers can work from home and fileshare with the fileserver.
Port 445 is also open on the firewall so XPs can fileshare over the Internet (i.e. so staffers can work from home) -- except they can't. XP always tells us it can't find the address.
Of course the XP systems on the LAN are connecting to an internal address (192.168.x.x) and the XP systems outside are connecting to a static ip address on the Internet. These same XP systems can ping the file server and can find port 80 open at the ipaddress, but can't find port 445 for filesharing. Macs can find 548 and 80 at this address.
In fact, when we take down our firewall completely (for a few seconds, for diagnostic purposes only), the XP systems still can't find the file server, so presumably the problem is not how I've set up the firewall.
Or perhaps we're going about this the wrong way?
Any help is appreciated.
Port 445 is also open on the firewall so XPs can fileshare over the Internet (i.e. so staffers can work from home) -- except they can't. XP always tells us it can't find the address.
Of course the XP systems on the LAN are connecting to an internal address (192.168.x.x) and the XP systems outside are connecting to a static ip address on the Internet. These same XP systems can ping the file server and can find port 80 open at the ipaddress, but can't find port 445 for filesharing. Macs can find 548 and 80 at this address.
In fact, when we take down our firewall completely (for a few seconds, for diagnostic purposes only), the XP systems still can't find the file server, so presumably the problem is not how I've set up the firewall.
Or perhaps we're going about this the wrong way?
Any help is appreciated.
