When using word files on a file, Microsoft Word becomes terribly slow

S

Starriol

Limp Gawd
Joined
Jan 3, 2006
Messages
191
I installed a new Windows 2003 server to make it a file server.

When some people here work with word documents on the server, the Microsoft Word slows down a lot. You type and then see the letter 5 secs later on the screen. This didn't happen with an old Windows 2000 server we had, neither happens when working with documents on the desktop.
It happens with both Office 2000 & 2003 and it happens with 2 PC with very similar specs (around 1.2 Ghz processor, windows 2000 sp4 and 128 of ram).

Any ideas ? Problem on the server? Perhaps the new switch I used? Low ram to work from the server? Thanks.
 
OK... the changes that I did after installing the new server were moving the router & cable modem to a spot near the server.
It looked like this:

Switch 1 ----- Switch 2 ----Router ---- ADSL

, the "-" signs mean an UTP cable connecting the devices. Also, switch one went to the server directly, without any other switch or router in between.

Now, it looks like this where we have the most switches:

Swtich 1---- Switch 2

And the server is connected to switch 1 via a cheap switch and the router is connected to the switch too.

Perhaps that new switch is the problem?

I'll check it out right now. Any more ideas guys?
 
Is it happening for all your users, or only some? Are all your clients using the same client OS?
 
I tried that, connecting the server directly to Switch 1, where the clients PCs connect and the same problem ocurred.

Does the fact that the windows sessions takes around 2 minutes to start after entering the user and pass have anything to do with it? Why could be this? I'm using a Windows 2003 server and I'm not too expert at configuring it... I'm taking classes now...

It's happening to all the users and on 3 clients that have this problem, the OS is Windows 2000 SP 4.

I didn't try any other office program... I'll check it out tomorrow...

Oh, and adding 128 more ram didn't help one of the machines
 
Is the Windows 2003 server acting as a domain controller? If so, you have a DNS issue if it is taking your clients 2 minutes to log on to their workstations versus the domain.
 
nessus said:
Is the Windows 2003 server acting as a domain controller? If so, you have a DNS issue if it is taking your clients 2 minutes to log on to their workstations versus the domain.
Click to expand...
When using Netdiag from Microsoft's Windows Support Tools, I get the following errors:

DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for the name
'server.ces.'. [RCODE_SERVER_FAILURE]
The name 'server.ces.' may not be registered in DNS.
[WARNING] The DNS entries for this DC cannot be verified right now on DNS
server 192.168.0.151, ERROR_TIMEOUT.
[WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '192.168.0.10'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.


DC list test . . . . . . . . . . . : Failed
'CES': No DCs are up.

CES is the name of my domain.

192.168.0.151 is the IP of my only server. It SHOULD be working as active directory, DNS and active directory server... but I'm getting problems...

Ah! I read in some post in another forum that with one domain controller I should have only one DNS server. 192.168.0.10 is the alternative DNS server since that is the router, so that is used in the clients and the server.
Could that be a problem? If I stop using it I lose access to the Internet.

Thanks. This may seems offtopic to some, but I believe it could be the cause of my troubles.
 
Yes, that's your problem.

Only DNS server your clients should have is your DC. In a single DC scenario, the DC should use itself for DNS resolution (in TCP/IP properties).

In the DNS Server properties on your DC set up your router as forwarder.
 
You must log in or register to reply here.
Back
Top