Prev: Maximum Threads supported on Windows server 2003
Next: Folder Permission frustration
From: steve on 4 Feb 2010 09:24
Well I decided to do a chkdsk /f on the C and D drives. and then
reboot.

Once I did that the file that I had been trying to delete was gone and
now I could delete the tree above it. So Im guessing there was some
sort of pointer problem in the file system.

Solved now.

From: Phillip Windell on 4 Feb 2010 09:59
"steve" <stevesemple(a)lycos.com> wrote in message
news:347f1d7f-407c-43e3-adaa-d85e5b296ced(a)d27g2000yqn.googlegroups.com...
>I do not think that it has been compromised. We are behind a firewall
> (watchguard) and we have virus protection on all machines. I have

You could have 50 firewalls and 37 AV products on the machine,...it would
not matter.

But glad to hear the CHKDSK fixed it.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


From: Ace Fekay [MVP-DS, MCT] on 5 Feb 2010 02:33
"steve" <stevesemple(a)lycos.com> wrote in message
news:db435f3d-4bce-48f7-9fea-041511840611(a)k19g2000yqc.googlegroups.com...
> Well I decided to do a chkdsk /f on the C and D drives. and then
> reboot.
>
> Once I did that the file that I had been trying to delete was gone and
> now I could delete the tree above it. So Im guessing there was some
> sort of pointer problem in the file system.
>
> Solved now.
>


Good to hear!

The link I provided was to help remove folders that were created by using
ASCII characters, which Windows supports through FTP for cross compatibility
with Unix. However, Windows Explorer uses ANSI. If there were folders
created with ASCII, and special characters used, such as "/.../" etc, in the
path, which would be created by specifying a full path using FTP, then it
would also act like some permission problem, too. This is because you can't
see the child folders. WIndows Explorer will not be able to read it to
display it.

That was just an FYI. Firewall or not, AV or not, if you are allowing FTP
anonymous uploads, and that allows anything in the FTP root, so any FTP
server is prone to this.

But I am glad to hear a chkdsk did the trick.

Ace


First  |  Prev  | 
Pages: 1 2
Prev: Maximum Threads supported on Windows server 2003
Next: Folder Permission frustration