Help!! Slow access to Win2k3 Server!!

  • Thread starter Thread starter Ron Sparks
  • Start date Start date
R

Ron Sparks

We installed a Windows 2003 server running Active Directory at a client
site. Had it configured at the office using 2 nics. When we got to the
client site, found there was only one connection for the server. The hub
and the DSL modem are in another location in the office. I disabled one of
the nics, DNS is using the IP address for the functioning NIC. The DSL
router is runing DHCP. Having a problem with dental software. The db is
on the server, when they try to move around in the db it takes minutes
sometime to change screens. We have the same dental software running
elsewhere on Win2k servers and do not seem to have problems. Does anyone
know a solution for this problem?

Thanks for your help in advance!

Candace Sparks
 
In
Ron Sparks said:
We installed a Windows 2003 server running Active Directory at a
client site. Had it configured at the office using 2 nics. When we
got to the client site, found there was only one connection for the
server. The hub and the DSL modem are in another location in the
office. I disabled one of the nics, DNS is using the IP address for
the functioning NIC. The DSL router is runing DHCP. Having a
problem with dental software. The db is on the server, when they try
to move around in the db it takes minutes sometime to change screens.
We have the same dental software running elsewhere on Win2k servers
and do not seem to have problems. Does anyone know a solution for
this problem?

Thanks for your help in advance!

Candace Sparks
Click to expand...

Rule No. 1 in an Active Directory environment, all members and DCs must use
the DNS server that has the records for the Active directory domain ONLY in
there TCP/IP properties. No ISP's DNS allowed in any position, doing so can
cause errors and slow network performance.

If you are using the DSL router for DHCP it is probably assigning the ISP's
DNS. Also, make sure the server with DNS has a statically assigned IP
address and that all members are using this address for DNS ONLY.

Post an ipconfig /all for the server and client and the name of the AD
domain from Active Directory Users and Computers.
 
I worked on the server this weekend, and started with basics according to
your suggestions. Still having problems. I replaced the client's 10/100
hub with a 10/100 switch and problem solved. Thank you very much for your
help!

Candace Sparks
 
Back
Top