Windows Forum

Ask something
Discussion Locked

ME and a Windows 2000 Server network

0 helpful
5 replies

by hhernandez

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Ok, I have a good one for you guys out there so pay attention. I have a Windows ME client connecting to Windows 2000 Network. This is the only ME client I have. I know that ME is like 98 and all but is there something I need to know or do differently? Here is what I have so far. I can connect to the network. The user has no issues logging in. There is no issues with pinging nor trace routing. When the user flows the network shares there is no delays until he opens a MS Word doc. I checked the network protocol (TCP/IP) and everything seem fine. Everything is binded and all. No conflicts anywhere. He can eventually open the doc but it takes a long time. My other users have no issues opening this doc especially me. I can open it and it opens fast but on this ME machine (laptop from Dell) it takes an extra moment to open the document. I even reinstalled MS Office 2000 Pro. I also check for new drivers and all. Is it a Windows ME thing. Shouldn't it work the same as my 98 machines? Or is there something I need to do to the ME laptop to speed it up. The laptop has plenty of resources(256MB of RAM). What boggles me is that there is no delays in surfing the Network shares only when it attempts to open the file. PLEASE HELP!!!

5 replies

by ann777

Yes, Word should open the document as fast on a WinME computer as it does on a Win98 computer. The only reson why it might not is that there's something else happening on the WinME computer. It does not sound to me as if it is a "network" issue.

Have you deleted the normal.dot file from the WinME computer? The template default (normal.dot) file sometimes gets corrupt and creates problems.

Have you deleted all *.tmp files and anything within the Temporary Internet Files folder? Sometimes a Word user opens document attachments from e-mail and that tends to cause slowdowns. Also sometimes the file will be partially created as a temporary file and cause problems as well.

When is the last time this computer was scanned for errors? Or viruses? When is the last time it was defragged?

by shanghai sam

I failed to mention that I already did these steps. Deleted the temp files on the ststem. Ran Defrag and check the system for errors. Good answer. I also went ahead deleted the normal.dot and it did not work. It was checked for viruses...in fact that was the first thing I did.

I am running out of options. He can open the docs and the attachments in email do attach but it takes a long time. His laptop is a power laptop. It is better than mine. When he opens files on his desktop it is fast.
I really think it is something with the way the laptop is communicating with the network. BTW, I already tried reinstalling the protocol and the adapters.

PLEASE HELP!!!

by hhernandez

It is me again. I just wanted to add some more notes on this. This laptop has PCI card slots so I installed drivers for a network figuring that it might be an issue with the internal network adapter or driver. Guess what! It still happens. So We know it is not the network adapter or the drivers.

I remember reading something once about ME coming in two versions. One is home use and the other I can not remember (it might be for business). Any ideas on this?

I am very close to reinstalling the OS. Please help.

by hhernandez

***This just in!!!***

There is a glitch from MS. Go figure. Go to Article Q272594.

This problem occurs because the Windows 2000-based server rejects your logon password when the client computer does not correctly de-allocate an internal structure that is used to track the logon session. The client attempts to reuse the expired encryption key that is passed to it by the server during the original logon.

This problem does not occur in conjunction with Microsoft Windows NT-based clients because the client does not attempt to use Distributed File System (DFS) because the session that is reused is against a DFS referral from the Windows 95-based or Windows 98-based client.

I am in the process in getting the fix from MS. I will letyou know if it works.

by maxwell edison

This problem occurs because the Windows 2000-based server rejects your logon password when the client computer does not correctly de-allocate an internal structure that is used to track the logon session. The client attempts to reuse the expired encryption key that is passed to it by the server during the original logon.

This problem does not occur in conjunction with Microsoft Windows NT-based clients because the client does not attempt to use Distributed File System (DFS) because the session that is reused is against a DFS referral from the Windows 95-based or Windows 98-based client.

See the following link:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q272594

(REMOVE SPACES from the pasted URL.)

Maxwell

This discussion is closed to new replies.