Port conflict - remote access and passive ftp - other than active ftp, any other solution?
Posted on 2007-12-07
I'm running the latest MS Small Business Server, with 2 workstations and an FTP server for client art files.
I work via remote access from a site 50 kms away from the office, taking over one of the office machines. We have had to use ACTIVE rather than PASSIVE ftp connections. Unfortunately, there is a port conflict between remote terminal access and passive ftp, ie. the range of open ports required for passive ftp connections conflicts with the port required for remote access.
I provide PC clients with a preconfigured FTP client program for PC (WSFTP). At least 50% of clients contact us to say the FTP server isn't working. It *is* working of course, but we have to take them through how to use the preconfigured client program, despite the detailed notes we provide. Argh.
Is there any way to get PASSIVE FTP and REMOTE access working together? Any help would MOST greatly appreciated.