General discussion

Locked

W2K Client cannot save to fileserver

By mcambon ·
Hello,

I'm trying to isolate a problem with a W2K SP3 Client on our network of about 50 users, mostly win98. There's about four W2k clients, all except one have SP3. We recently moved from a NT4 domain to W2k (with SP#) domain with 1 fileserver and 2.
DC.

The W2K clients are at times abnormally slow considering their hardware specs. But it is one client in particular who has recently been unable to save to the fileserver. The error is Windows: Delayed Write Failed. Windows was unable to save all the data for the file. etc.

In the event log this is listed as ID 50 with a source of MrxSMB. I've tried the workaround from the Microsoft Knowledge base article for this issue, (article 321722), but it has not solved the problem. From my understanding, SP3 should have fixed this issue.

There is no disk quotas enabled.

Has anyone run into this before? I'm wondering if it could be a cabling issue, because our cables are a mess in the ceiling, some redirected by hubs, others going directly into the main high end switch. It does seem related to the new network setup however, as previuosly we did not have this problem.

Any help would be greatly appreciated!!!

Mariec

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

W2K Client cannot save to fileserver

by saihib In reply to W2K Client cannot save to ...

After doing some searching it seems that a lot of people are getting similar error messages. Go to google.com and search on: Delayed Write Failed. Windows was unable to save all the data for the file

Also look at www.eventid.net for error 50

Collapse -

W2K Client cannot save to fileserver

by mcambon In reply to W2K Client cannot save to ...

The question was auto-closed by TechRepublic

Collapse -

W2K Client cannot save to fileserver

by leehellcat In reply to W2K Client cannot save to ...

You say you are running W2K Servers (1 file and 2 DC), and 4 W2K Clients, that are running slowly.

Are you running Active Directory, or just DNS, DHCP ?

It could be a networking issue. Are the Win2K clients setup with the correct TCP/IP settings ?
Are you using Cat5 cabling at 100Mbps or 10Mbps ?

I do not think that is is likely to be a cabling problem, more likely to be a setup issue between the Win2K clients and the Servers. Are the clients able to save files to the other 2 servers okay ?

Collapse -

W2K Client cannot save to fileserver

by mcambon In reply to W2K Client cannot save to ...

The question was auto-closed by TechRepublic

Collapse -

W2K Client cannot save to fileserver

by mcambon In reply to W2K Client cannot save to ...

This question was auto closed due to inactivity

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Operating Systems Forums