Moving files to new 2000 server

[Guest]

Archived from groups: microsoft.public.win2000.file_system (More info?)

When moving files from a Netware server to a 2000 server,
we've noticed an odd issue. When the files are moved with
Windows 98, there is no problem. However, when moved with
a Windows 2000 (professional) PC, none of the 98 boxes can
access the files. The problem persists, regardless if a
single file or a whole folder is copied. You can see the
file, but can't open it.

 

[Guest]

Archived from groups: microsoft.public.win2000.file_system (More info?)

Check the permissions on the 2k server.

Joe F. wrote:
> When moving files from a Netware server to a 2000 server,
> we've noticed an odd issue. When the files are moved with
> Windows 98, there is no problem. However, when moved with
> a Windows 2000 (professional) PC, none of the 98 boxes can
> access the files. The problem persists, regardless if a
> single file or a whole folder is copied. You can see the
> file, but can't open it.

 

[Guest]

Archived from groups: microsoft.public.win2000.file_system (More info?)

The long file names are available on all of the systems,
and the file names can be short and it still happens.
Network rights are also correct. I can copy the file with
both 98 and 2000. However, if I copy to the server with a
2000 workstation, only 2000 PCs can open. If I copy with a
98 PC, both 2000 and 98 can open. So somehow the copy with
2000 is changing something....maybe some sort of header on
the file (an added header field by the 2000 workstation
that can't be read by the 98 box??)


>-----Original Message-----
>When moving files from a Netware server to a 2000 server,
>we've noticed an odd issue. When the files are moved with
>Windows 98, there is no problem. However, when moved with
>a Windows 2000 (professional) PC, none of the 98 boxes can
>access the files. The problem persists, regardless if a
>single file or a whole folder is copied. You can see the
>file, but can't open it.
>.
>

 

[chen]

Archived from groups: microsoft.public.win2000.file_system (More info?)

Hm.... This is a bad theory, but, is "write short file names" enabled?

It should be enabled by default... And I don't know if Windows 98 needs it
or not (DOS needs it, though)...

// Chen

"Joe F." <anonymous@discussions.microsoft.com> skrev i meddelandet
news:27b101c4546f$77c6d940$7d02280a@phx.gbl...
> When moving files from a Netware server to a 2000 server,
> we've noticed an odd issue. When the files are moved with
> Windows 98, there is no problem. However, when moved with
> a Windows 2000 (professional) PC, none of the 98 boxes can
> access the files. The problem persists, regardless if a
> single file or a whole folder is copied. You can see the
> file, but can't open it.

 

[Guest]

Archived from groups: microsoft.public.win2000.file_system (More info?)

Joe F. wrote:
> The long file names are available on all of the systems,
> and the file names can be short and it still happens.
> Network rights are also correct. I can copy the file with
> both 98 and 2000. However, if I copy to the server with a
> 2000 workstation, only 2000 PCs can open.

What errors do they get?

> If I copy with a
> 98 PC, both 2000 and 98 can open. So somehow the copy with
> 2000 is changing something....maybe some sort of header on
> the file (an added header field by the 2000 workstation
> that can't be read by the 98 box??)

That doesn't make sense. Have you double-checked your NTFS permissions &
perhaps even re-applied them to all subfolders set for inheritance?
>
>
>> -----Original Message-----
>> When moving files from a Netware server to a 2000 server,
>> we've noticed an odd issue. When the files are moved with
>> Windows 98, there is no problem. However, when moved with
>> a Windows 2000 (professional) PC, none of the 98 boxes can
>> access the files. The problem persists, regardless if a
>> single file or a whole folder is copied. You can see the
>> file, but can't open it.
>> .