It's really hard to give you any kind of a definitive answer on this, but observing what you've said, a couple things come to mind.
1. Things aren't what they seem to be.
2. Access to resources isn't what it should be.
Given those two statements, the places I would begin my search to figure out what's going on are in areas of access control. I'd check in three areas for starters -
File and directory names and permissions (access rights). Make sure that both the files and directoriesyou're interested in are named exactly what you expect and make sure that BOTH the files AND directories have sufficient access that you can get to them.
Account names and passwords - you state that you can telnet into the account(s) you're interested in, so this is unlikely to be your problem, but make sure the account you're telnetting into is the same account that owns the DIRECTORY you are interested in. If not, that could be the problem or it could at least point you closer to the problem.
Samba has quite a few settings of its own. On Windows, all of the choices in the Network Neighborhood are pretty much made for you. In
Samba, whether on UNIX or Linux, there are quite a few choices to consider. One would hope that the defaults are acceptable, but that may or may not be the case. I'd check the first two areas vigilantly FIRST, but after exhausting them, I'd locate a good Samba HOWTO and make sure you understand what you've set up.
I wish I could be more help thanthat, but hopefully I've given you a few ideas of places to start. Sure sounds like an access problem of some sort, so really check all access possibilities first. Clearly you can "see" the machine OK, so hardware and networking aren't the problem. Clearly you can even login, so access between the systems isn't the problem. Start with directory and file access, then check accounts and go from there.
Email me, masinick@y
