-
All replies
-
Helpful answers
-
Aug 8, 2011 10:32 AM in response to logicdwby douglaswardacn,Are you connecting as a local user on Lion Server, or a Open Directory/access only user?
-
Aug 10, 2011 12:02 PM in response to logicdwby crwoo,I have the same issue, every program works besides solidworks, and i cant fiund solution.
-
Aug 11, 2011 10:42 PM in response to crwooby techgal,@ logicdw:
How are you connecting your windows 7 to server shares? Please share your configuration as None of my shared folders on the lion server are accessible from windows xp home, pro, 7 any longer. We have dual boot imacs and they were configured to access mac osx shares using od accounts. Now they will not connect. This was working with 10.5 adn 10.6. Now with 10.7 the mapped drives will not connect.
Thanks for your insight.
-
Aug 12, 2011 9:28 AM in response to techgalby Jaymanswiss,techgal...
I have the same issue as you saw and replied on my post... you obviously can connect to an XP machine but how... my issue is the same as yours... I connected once but can never again.
Someone help before I send it back to apple (mac mini server).
Thanks in advance fore any help..
Tony
-
Aug 12, 2011 9:33 AM in response to Jaymanswissby crwoo,you need to enter the server name before user EG SERVER\john otherwise it will use CLIENT\John and that will not work. But our issue is something else. File sharing and everything works besides Solidworks and SMB scanning with a canon IR copier
-
-
Aug 18, 2011 2:42 AM in response to logicdwby Darren2473,I am having similar issues connecting to 2 internal raids we use as a server on our Mac Pro. Many disk permissions have been changed to READ ONLY and access is very buggy!
Works if I change the individual files manually back to Read & Write, but only sometimes.
-
Aug 18, 2011 4:46 PM in response to douglaswardacnby logicdw,I'm not sure. I connect through windows explorer and type in the credentials of a Lion Server user account.
-
Aug 18, 2011 4:50 PM in response to techgalby logicdw,techgal,
I can connect as I did before Lion. To connect, I type in the IP address in to my explorer bar "\\xxx.xxx.xxx.xxx" and then hit enter. It prompts me for my credentials and I type in username with the server name in front of it in the form "SERVER\username"
-
Aug 18, 2011 4:52 PM in response to logicdwby logicdw,UPDATE
I am thinking there might be a problem creating temporary files on the network drive. Still searching for a solution.
-
Aug 19, 2011 3:42 AM in response to logicdwby rickblackdog,I agree logicdw, seems to be with the temp file created. We're using office 2003 at the mo, it's files are probably prefixed with a ~ modifier. As it's on a share the temp file is created in the same directory the folder is opened in. I imagine this should be simple to fix... anyone any suggestions?
Or does anyone happen to have an actual lion server where your able to open M$ office docs on an SMB share? Mine was an upgrade from snow leopard server also running SMB.
-
Aug 19, 2011 8:10 AM in response to logicdwby techgal,@logicdw..
I have ~25 windows machines (mixture of xp home, pro, vista, and 7) that are connecting automatically to smb shares on both 10.5 and 10.6 servers. They were configured using your suggestion. I do not know how your server is configured but we use the following services: afp, web, radius, ical, ichat, open directory, dhcp, and dns utilizing protocols ftp, smb, and afp. We use extensively mobile accounts and mcx on our mac clients. On lion server, I get the following error (a special logon session does not exist it may have already been terminated) which seems to be pointing to a kerberos issue.
Techgal ACTC, ACSP, Network+, A+
-
Aug 23, 2011 7:38 AM in response to logicdwby rickblackdog,logicdw did you find any solutions to this yet?
-
Aug 30, 2011 3:27 AM in response to rickblackdogby rickblackdog,I've found the root of the error and raised a bug report with apple. The packet reads the following error when you try and access an office 2003 file from an XP machine...
Header checksum: 0x0000 [incorrect, should be 0x19e4 (maybe caused by "IP checksum offload"?)]