Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Avoid '-36 errors' when connecting to Win2K servers' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Avoid '-36 errors' when connecting to Win2K servers
Authored by: leitch on Nov 11, '03 02:21:11PM

I am having the same problem as everyone here, but I hope this will shed some light on the topic.

We have a mixed network where I work. Some computers are running NT 4 service pack 6 and others are running 2000 service pack 4 with Active Directory running. I can connect to all the NT boxes perfect. I can connect to some of the 2000 boxes. Those that will not accept a connection can still be connected to using smbclient through a terminal session

smbclient //server/path -U username -W workgroup

When I connect to the server this way it works perfect. I don't know the primary difference between OS X smb connect and the smbclient. I hope this helps figure it out.



[ Reply to This | # ]
Avoid '-36 errors' when connecting to Win2K servers
Authored by: leitch on Nov 11, '03 05:13:56PM

I've been working on it and I have some more news to report.

I was able to mount the drive manually using mount_smbfs. Here is the command I used.

mount_smbfs -I fileserver -U user -W domain //server/path ./local_folder

It asked for the password and then returned to the prompt. I created the folder in my user directory. When I browsed to this folder in finder I was able to view the mount I couldn't make with Connect. I hope this helps figure out why it won't work the easy way.

To umount the drive use umount /path_to_folder



[ Reply to This | # ]