Mattski2000
Member
- Joined
- Jun 1, 2008
- Messages
- 2
Hello , I hope this is the correct forum to post this question.
I installed server 2008 60 day trial last week.
OS installed without any issues, I added the role of file server all OK.
Added the server to my current sbs2003 domain without an issue.
I wanted to test how fast server 2008 is at basic file serving.
I setup a share with full permissions for the everyone account.
I then copied files from our 2003 server to the share on the 2008 server.
Network speed was good, all files copied across successfully.
I can browse the share from any windows machine on the domain.
I then opened a solidworks assembly from that share using a Windows XP client, the assembly opened faster than on the server 2003 machine.
I was impressed, I then made a change to the assembly and pressed save, the client machine just sat there on egg timer. I checked task manager to see if solidworks was responding to find that it was showing as not responding. I had to end task.
I tested this on a couple assembly's getting the same result every time.
I then tested creating a word doc on the server 2008 share and then saved the document, didnt have a problem with that at all.
I copied a fairly large rar file to the server without any issues.
Does anyone have any suggestions or thoughts on why when saving It would crash solidworks.
I can do the same process using a 2003 server and it doesn't crash solidworks.
I have check permissions on the share and files, I have gone to the extent of adding the 3 users to the share and giving them full access.
Hardware is
Quad core CPU
8GB mem
Server 2008 Std 64bit
160GB IDE OS drive
Raid card with 3 HD's for Data
Intel NIC
thanks for any help
I installed server 2008 60 day trial last week.
OS installed without any issues, I added the role of file server all OK.
Added the server to my current sbs2003 domain without an issue.
I wanted to test how fast server 2008 is at basic file serving.
I setup a share with full permissions for the everyone account.
I then copied files from our 2003 server to the share on the 2008 server.
Network speed was good, all files copied across successfully.
I can browse the share from any windows machine on the domain.
I then opened a solidworks assembly from that share using a Windows XP client, the assembly opened faster than on the server 2003 machine.
I was impressed, I then made a change to the assembly and pressed save, the client machine just sat there on egg timer. I checked task manager to see if solidworks was responding to find that it was showing as not responding. I had to end task.
I tested this on a couple assembly's getting the same result every time.
I then tested creating a word doc on the server 2008 share and then saved the document, didnt have a problem with that at all.
I copied a fairly large rar file to the server without any issues.
Does anyone have any suggestions or thoughts on why when saving It would crash solidworks.
I can do the same process using a 2003 server and it doesn't crash solidworks.
I have check permissions on the share and files, I have gone to the extent of adding the 3 users to the share and giving them full access.
Hardware is
Quad core CPU
8GB mem
Server 2008 Std 64bit
160GB IDE OS drive
Raid card with 3 HD's for Data
Intel NIC
thanks for any help
