This is a rather odd problem. I recently upgraded Samba from what came with FC5 by default to the latest version using yum, (stupid me) and since then, when I access my FTP that is hosted from a Win2K3 computer on the same network, the ftp directory appears completely blank. Now on that Win2K3 machine, I can open a browser and access the samba share both by entering it's network address //server/fileserver and by entering it's mapped network drive with no problem at all. But for some reason, the once fully functional FTP program cannot view any network samba share. The FTP program (Serv-U) is pointing to //server/fileserver for it's home directory and nothing has changed with that machine at all, but for some reason, it refuses to display any of the contents of it's home directory. It just appears to be a empty FTP server. It allows me to log in with no problem at all, and it allows me to point to a local directory for the Serv-U home directory, but not the samba share. Clearly the problem lies with Samba, but I am at a loss because I can directly access the samba shares from every machine in the house, but Serv-U sees nothing. Anyone know where the problem is?

double check that Serv-U machine is in the same workgroup as the rest. and check permissions

They are definitely in the same workgroup and as I stated above, the FTP server machine hasn't been touched at all during this. The problem with permissions on the Samba machine is wouldn't Samba reject all connections to it if the permissions were wrong? I can connect to the Samba machine via the Windows Explorer (Both by typing \\server\ftpserver and by accessing the mapped network drive) and have it display the contents with no problems at all, but it seems when Serv-U tries to make the connection (by means I am not sure of), it must be rejecting it.

are the user for samba and ftp the same?

I assume that the FTP is using whatever the Windows login is at that moment, and yes, Samba has the same user.