Think of the positive side to this though... You'll only have one share space now for all users wether on Mac or PC... Simpler is better in this case no ?

Weird, when i make a copy of a folder and pasting it in the same location i can see the file types stay the same when i view in SMB. But the same folder has file type issues when i connect to the server by going to hard drive - network- PFW MAC SERVERS-PRODUCTION SERVER-MAC SHARE

The problem is multiple people use the same quark document and i forgot to mention that, so copying and pasting back on the server won't work, because they would overwrite each other. If two people have two different copies and are making changes to two different documents then that is when problems occur. UGGGHHH, i still need to contact quark.

If multiple people are editing the same document and then re-saving it to the same file, you have problems far beyond anything to do with filesystems and sharing. You need to establish some work-flow procedures that will prevent this. E.g. have a convention that files are always saved with a new name that includes a version number and user name (so that no files will overwrite each other).

Tha could indded be a problem... Normally through SMB it will lock the file if they work on it, but some times it may not properly "release" it afterwards and tell other useers that the resource is busy or something like that. Quark is not really network friendly because of the way it works (once again explained in the MacWindows link that fat_elvis posted) and ahven't seen any one get goo duspport on this from Quark as they just give them the same advice that is on the above mentionned site.

hum hum... add what hayne just posted as a very good work suggestion :)
(once again beaten to the finish line... I have to get used to using quick reply loll)

I hear you, now im just worried about creating copies of the orginal folders to SMB share, because once i do that...POOOOF...They can't access the same folders through the original way they were connecting. That means if the transfer to the SMB share doesn't work im in deep trouble.

Basically what im doing is opening up the file server by going to network in the hard drive. So i have that window open to my left, then i connect again to the same server and same share folder through SMB and put that to right of my screen. I then have to rename the folders i move, because obviously you can't have two of the same names on the same location. So im really hesitant on doing that cause once i rename it and copy it i have to delete the original folder in that location and the normal way they connect won't see the files right, but i can see everything again in SMB and saving in SMB seems to work.

Need some reassurance this will work :)

I would suggest you move the files directly on the server and not through the Mac... And what you can do so the users do not find the originals is to send a general email with the new procedure (or impliment a new script or what ever ,depends on your setup and the way you work), telling them that the server will become unavailable at x time so they have to disconnect from it by then and have data saved or they will lose it (or with Quark, it would get corrupted beyond repair actually most of the time), then at the specified time, check if users are connected to the AFP share, disconnect any that remained then tunr of the AFP service and SMB on the server (so users don't try to open a file in transfer or something). Move the files to the new SMB share on the server and then reactivate only SMB. At least thats how I'd do it. You can even call this server maintenance for the users ;)

Okay im gonna need some more info about this. You say disconnect AFP service? And SMB service? Is SMB a service running on 2000? Also, When i connect through AFP and SMB it is the same share that is why i have to copy to my desktop then rename it and copy it back through the SMB share and the file types stick.

But when i do the copy thing i the file types no longer show up correctly using the AFP method but are correct on the SMB side. Am i making sense hehe, i know this is confusing as hell and hard to explain.

I understand very well what your trying to explain and yes it isd confusing at times... So I'll try to rephrase... Forget all the Macs and the PCs in the office... I want you only on the Win2K server... think of it as standalone machine for now... Disconnect the users from it ideally son no one can access the folders while you work on them... Then, on the Win2K server, rename the files, give them the right extensions, fix the whole thing ! lol Then, stop the AFP service (and make sure its not set to start with a server reboot) and only have users reconnect all through smb both PC and Mac.
Hope this is clearer.

:o Going to sleep now... too much geek work :o

haha too much geek work, i like that. My windows users connect through windows networking and i just map the drives they need access too :)

So you are saying that i don't need the macintosh services when the macs connect through SMB?

Thanks again for all your help, i truly appreciate it and hope someone pays it forward to you :)

Its just fun to help... And to answer, no you don't need Mac services toi run for SMB. If you have Mac users logging on as network users from the server then you would still need those. But I don't think your running networked users... are you ?

Well they do log onto the network technically through SMB, they need to type in their active directory username and password. :) But they are not tied into active directory per say, since there machines are not tied to it. When they log into their machines it is a local logon.

Now, these files where i have to change the extensions, i can't change them on the 2000 server because the server doesn't know what types of files they are. I will have to transfer from a mac.

Took me 2 days, which came out to about 16 hours total to move the files for the second time to the SMB share folders. But since i moved them the quark files and everything else seems stable, so far so good. The only problem i came accross was when i was uploading files to the server it would crap out and i would receive a blue screen with the problem that resided in the macintosh services. The stop error i would get when the server crapped out when transferring was thesfmsrv.sys file. Now that im using SMB built into OSX i no longer needed the mac services installed, so i went ahead and stop the mac services and sure enough, no more server crapping out. Hope this helps somebody else out and i want to thank those on the forums that helped me out, BIG THANKS!