• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

WinMe Client is faster than Win2k Client on Win2k Server Network???

Uclagamer_99

Platinum Member
I just upgraded our old office server from WinNT Server to Win2k Server but am having problems with the Win2k clients. The network is setup as a 8 computer workgroup (6 Win2k, 1 Win2k Server, 1 WinMe). However, the Win2k Clients are very slow when they access our customer application on the server but the WinMe client has no problem at all and accesses the shared drive off the server right away.

Please help, thanks.
 
Could be some name resolution problem.

Can you provide more specifics?
Domain controllers and if they are running hybrid mode?
What are the client and server WINS/DNS servers?
Do you have a connection to the internet?
What is the custom application and how does it operate, are the executibles/program files on the server or the client?
What means of communications do the clients and server use? What protocol?

I know it is a lot to ask but it will help narrow down your problem.
 

If you don't have WINS or DNS running, make sure you have the Server(s) listed in each workstations HOSTS file. Make sure you have the latest Service Pack and HotFixes on all machines. Check that you have the latest driver for your Network Card. Also make this registry change on all Win2K machines.




Speed up & Browse Windows 2000 faster.
April 9, 2002 - 10:55 am


By Rick E.J
Site - http://cyberwizardpit.cjb.net

This Tip is kindly contributed by Jason Edwards, a Snr. Network Engineer with a Large Network Firm.

Here's a great tip (a bug actually) to speed up your browsing of Windows 2000 machines. Its actually a fix to a bug that by default of a normal Windows 2000 setup that scans for shared files for Scheduled Tasks. And its turns out that you can experience a delay as long as 30 seconds when you try to view shared files across a network from as Windows 2000 is using the extra time to search the remote computer. Note that though the fix is originally intended for only those affected, Windows 2000 users will experience that actual browsing speed of both the Internet & Windows Explorers improving significantly after applying it since it doesnt search for the Scheduled Tasks anymore. Here's how :

Open up the Registry and go to :

HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/Current Version/Explorer/RemoteComputer/NameSpace

Under that branch, select the key :

{D6277990-4C6A-11CF-8D87-00AA0060F5BF} - and delete it.

This is key that instructs Windows to search for Scheduled Tasks. If you like you may want to export the exact branch so that you can restore the key if necessary. This fix is so effective that it doesn't require a reboot and you can almost immediately determine yourself how much it speeds up your browsing processes.

 
Spidey,
How do I know what the domain controllers are and if they're running in hybrid mode?

At first I tried to leave the DNS server blank but it auto assigned 127.0.0.1. When I put this address into the client computers it says that this is a loopback address?

There is NO connection to the internet.

The custom application is a inventory program along with a customer database.

Everything is running in TCP/IP and the IPs are manually assigned on each computer.


Wlee,
Tried your suggestion but it does not work.


One more thing, I installed the same program on my WinXP Professional and had the Win2k run it remotely and there is no lag. However, if I try to run it remotely off the Win2k from WinXP there is still that lag.

I also tried nslookup from the command prompt and it says:

*** Default servers are not available
Default Server: Unknown
Address: 127.0.0.1
 
Back
Top