starriol
Joined: 16 Aug 2006
Posts: 1
|
 Posted:
Wed Aug 16, 2006 1:10 am Post subject:
I'm having several problems with a windows 2003 server. |
|
|
OK, the story is this: at our company we where using Windows 2000 server.
We decided to buy a shining new PC (Dual core P4, 1 GB of ram, 2 SATA disks in raid) and upgrade to windows 2003.
We did. But in the middle, things got quite complicated.
Now, the network works WORSE than it did before.
The server is the only one and it's a file server; all the files of the company are worked on it.
Word files, photos, Excel, everything is there...
It's also important that we connect to Internet with router, that is configured on every PC as the alternative DNS server, including the only server (Which is DNS and domain controller with active directory).
I read somewhere that this could be the cause of my troubles...
My problems are basically 3:
1) In some PCs of my network, when working with Word files the response time gets REALLY slow. That is, you type something in the keyboard and the cursor turns to the clock and 5 secs later you see the letter you typed. THAT bad. Tried changing from Office 2000 to Office 2003, nothing. Disabling the antivirus (nod 32, know to cause problems with networks), nothing. Even added ram to one of the PCs affected. NUTHING!
This happens ONLY when working with Word files on the server. If I copy THE SAME file to the affected PC, it's all good. On some other PC of similar specs, I don't have the same problem.
2) All the PCs take between 1 and 2 minutes to start the windows session after I log with user & pass. This didn't happen with Windows 2000 server (Which wasn't installed by me. I admit I'm a newbie and it was too eager from me to install windows 2003 personally. I'm taking classes now, so please help me out).
3) Some people report that the time when browsing through the files on the server or when opening a file are SLOWER, with a PC 5 years newer!
Anyway, as I said, some guy in another forum suggested that I should erase the router as the secundary DNS server on the client PCs and the server. I did that just to try it out, but then the PC wouldn't access to Internet!
So, what do you think about his idea?
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...
192.168.0.10 is the IP of the router; it's only function is to provide internet to all the PCs of the domain.
Ideas guys! I need them! |
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in
