Problems after moving from novell to 2000

[fLy 0]

Hi, after moving a section of a company from an old

486 novell server to a new win2000 server a couple of problems

occured:

 

1)Share names are maximum 12 letters or else you won't

see them in win9x clients.

2)On the login script run, when you try to "net use" the

drive letter Z it says its already occupied although its not.

This also happens only on 9x clients.

 

Their system guy claims that another thing happend after the

data transfer between the servers(it was first transfered to a client and then to the win2000 server):

 

Another win98 thing...When he used the "include" command in a

C language file and linked to a long file name, thats what he claims, it worked.

Now, only short, bla~.bla names work.

As far as I know, long file names doesn't work in a win9x dos window...He claims it worked...Possible?

 

I personally think that something got f-cked during the data

transfer but I can't put my finger on it.

 

Has anyone encountered a similar situation, or problems?

 

 

Help please!

Thanks!

[clutch 1]

Actually, the limitation should only extend to DOS and Win 3.1 (can't remember anyone pushing that share name limit using "net share") and not affect Win9x/NT 3.x or above. Now I don't know a damn thing about C coding, but one thing you might try when referencing long filenames or files/directories with spaces in their names is using quotes around the path, such as:

 

"C:\Program Files\My Program\progfile.exe"

 

This way, the entire string will be referenced rather than being broken at "C:\Program" and the rest being considered an argument.

 

I can't remember the problems that you have ever showing up for me when using Win9X in any Windows network, be it Win9X peer-to-peer, NT Domain, or Win2K AD. What version of Novell were you running, v3.12? I thought that was the oldest one which was "Y2K Compliant" (haven't heard that in a while, eh?).

 

One more thing, there was a bogus "virus" scare going around telling people to delete a specific file if found on their Win9x systems, but the file enabled use on long file names. I don't suppose you would know if anybody fell for that hoax, do you?

[ryoko 0]

Look for the lastdrive statement. It is from the novell client, however I think it is placed in the autoexec or config.sys .

 

Clutch, The virus hoax you are refering to is sulfnbk.exe

I know people who fell for it just hours after I sent a warning not to delete that file. Oh well, I tried.

 

Happy new year everyone!

 

-RY

[fLy 0]

Thanks for replying.

They have NAV Corporate Edition installed and updated so a

possibility of trojan/virus/hoax or any abuse is, for now,

not considered.

The problem of the "Z" drive has got something to do with

W2K Server using that drive for the login procedure, after the

login script ends you can map the "Z" drive freely.

One option is to put a batch in the startup folder of the

relevant stations and one option ofcourse is to make windows

use a different drive letter for its operations.

 

The question is, ofcourse, is it possible?

 

 

Thanks and Happy New Year!

 

 

b.t.w

I know its annoying, you just tell yourself: "why *%^&^$&^ can't he just use a different letter..."

He just needs it because he used it on the novell and now things

are "connected" in the different mappings...