G
Graham Webber
Hello,
I am having a problem with FTP browsing issues via a SBS2003R2 server -
using RRAS.
If I try to connect to an FTP site from internet explorer on any LAN client,
i get:
"Windows cannot access this folder. Make sure you typed the file name
correctly and that you have permissions to access the folder.
Details:
The connection with the server was reset"
I have changed the Passive FTP settings of IE, but it has not fixed the
issue.
I have also tried accessing from the command line FTP as soon as I type
anything in to the User prompt and press enter i get Connection closed by
remote host.":
"ftp ftp.microsoft.com
Connected to ftp.microsoft.com.
220 Microsoft FTP Service
User (ftp.microsoft.comnone)): Anonymous
Connection closed by remote host."
Ftp browsing is working from the server console, which is multihomed and set
up as a
RRAS router
All other internet traffic appears to be working from clients including
HTTP, IM, SMTP,
etc.
We are not getting any errors in the event logs on the server or
workstation.
Has anybody seen anything like this before?
Regards
Graham
I am having a problem with FTP browsing issues via a SBS2003R2 server -
using RRAS.
If I try to connect to an FTP site from internet explorer on any LAN client,
i get:
"Windows cannot access this folder. Make sure you typed the file name
correctly and that you have permissions to access the folder.
Details:
The connection with the server was reset"
I have changed the Passive FTP settings of IE, but it has not fixed the
issue.
I have also tried accessing from the command line FTP as soon as I type
anything in to the User prompt and press enter i get Connection closed by
remote host.":
"ftp ftp.microsoft.com
Connected to ftp.microsoft.com.
220 Microsoft FTP Service
User (ftp.microsoft.comnone)): Anonymous
Connection closed by remote host."
Ftp browsing is working from the server console, which is multihomed and set
up as a
RRAS router
All other internet traffic appears to be working from clients including
HTTP, IM, SMTP,
etc.
We are not getting any errors in the event logs on the server or
workstation.
Has anybody seen anything like this before?
Regards
Graham