Question Locked

Mac's can not FTP with SBS 2003 server

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello all,

I have a problem with FTP. No macintosh machines are successfully connecting with my SBS 2003 server's ftp sites. None, that is except one.

The one that can connect is using MAC OS 10.5. It cannot connect through Safari, but will using FETCH.

Other Macs are on 10.4 os and won't connect at all. I've installed FETCH and Internet Explorer 5.2.3 for Macintosh. Nothing works here.

Any Windows based computer will connect successfully anytime.

I've tried:

Turning off Windows Firewall on the server. Can't do...another service is controlling ipnat.sys... assuming that WF is already disabled.

Reinstalling Appletalk - failed

Creating a new FTP site - Failed

using the ftp://username:password@domain connect - failed

Changing the FTP directory listing to Unix from MS Dos - Failed

Opened anonymous access - failed

Used a different port than 21 - failed

confirmed hardware firewall was allowing port 21

Any suggestions? I've searched for days to find a blog/forum that helps with this, but can't find anything that gives a good answer. I am guessing it's probably a server side issue, possibly protocols, but can't seem to find the fix.

I'm open to any advise that you may have.

Thanks!

3 replies

by cg it

hopefully your not using IPX on the Macs

you want to use TCP/IP.

There's nothing different in SBS than any other Windows 2003 Server Edition that would preclude Mac computers running TCP/IP protocols from accessing a published FTP site in SBS.

by t. hans

Hey CG IT,

Thank you for the input. Unfortunately, most of those connecting to my FTP from a MAC are Clients and 2 out of three of my graphics editors. The one editor using 10.5 is only successful using FETCH.

The other two editors were finally able to connect using FILEZILLA.

I am unable to determine whether my clients are using IPX (don't know how to and they don't either). I would prefer that they (the clients) were not forced to use a 3rd party software too as I don't like the unprofessional image that presents. Not to mention that would add another element to the mix of troubleshooting problems should they occur.

Can you give me an easy step-by-step way to check on IPX vs. TCP/IP? I can then filter that info to a few clients and see if that works better.

Thanks!
Ted

This discussion is closed to new replies.