Issue with Slow Login & connections Droping when connected to win2k3 Domain or sql server

Windows 2003 server(Domain Controller) Having 30 Nodes(clients WIndows XP)
The server have also installed sql server2000 Enterprise edition on it, and 10 of 30 clients use this sql server  to communicate whic have our own developed software in C#.Net
1-User take too long to login with WIndows 2003 server, to fix this I have alreday installed User Profile Hive tools but....IN VAIN
2-After some time of login when we start Application(Our Own Developed) it communicate and connect to SQL server 2000 but after few time when we close Application and try to reconnect to the SQL Server its fails we have to restart the computer or sometime LogOff and relogin but again same problem keep exist. When we ping the server it response but when we try to open some share on it, it take too long or sql server doesn't response any way.
Please help me to resolve this fix,
Abny Suggestion in this regard would be...............You Know (Plzzzzzzzzzzzzzzzzzz)

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Zuhir ElgmatiApplications and Systems AdministratorCommented:
are you sure that you configure DNS correctly ?
if yes try this
Aaron StreetInfrastructure ManagerCommented:
before i opened this i was going to suggest DNS.

only the other day i found someone had change a setting on ours. jsut one innocent little tick box and it meant that every DNS query ment a 5 second time out!!!

so i woudl check things liek this first.. a short opackcapture from a PC trying to access the server should show you if there are any network problem causing it..

jsut look for long delays in network conversations. DNS responces and acknolage packets shopuld be almost instance...
starboy42Author Commented:
Thanks for quick respons zuhairGmaty:
Yeah I've configured Prefered DNS Server as my Dafult Windows 2003 server(Domain Controller).
my main problem is with SQL connectivity becasue user can bear with slow login but not with drop connectivity with SQL server by Application. I can ping to Server(Domain Controller) which response positive its mean there is no problem with connectivity with windows server but when our clients try co communicate with SQL server it takes too long or not. I don't know which service is used to communicate with SQL server and how to fix this issue because without SQl server connectivity they can't perform any task regarding their job (Data Entry..etc...)and sometime it runs very well with very fast and quick speed.
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

Aaron StreetInfrastructure ManagerCommented:
rember DNS is cached on a pc.

i would still get ether real on the pc and do a capture while you are accessing the SQL server. and then look to see what is actuly happening and where the bottle next is.. sending to the server or responce from the server..

its very easy
Zuhir ElgmatiApplications and Systems AdministratorCommented:
i'm not a programmer acually but please try to make maintanice plan wizared by right click in your database server and follow up the wizerd, it will improve your DB connectivety

wish it's help
Aaron StreetInfrastructure ManagerCommented:
if log ons are taking a long time as well this wont be a SQL problem. so although Zuhair has a good idea. i would look for the route cause.

and if many things are taking a long time i would look first at the network to insure that is not the problem before looking at each application. You may find a simple network error that you can cure and fix all the problems. rahter then finding a work around for each one..
starboy42Author Commented:
Thanks you(All)
I'll try above suggestion(s).
Thanks Again to pay attention on my query.
I really appreciate  all of you. Hope one of the above would fix my problem.
Rob WilliamsCommented:
>>"I've configured Preferred DNS Server as my Dafult Windows 2003 server"
Preferred? You should ONLY point to your internal DNS server/s. If you have an external/ISP server as a secondary it will result in very slow logons, and delayed name resolutions. This is a very common DNS issue.
Aaron StreetInfrastructure ManagerCommented:
this is what was happening in our server and why i suggested you looked at it...

if our server could not resolve a name it would attempt to forward it to anotehr DNS server. but as it did not have right to do this any more (becasue of the tick box) it then waited 5sec for a responce (time out) before trying another server. and then finaly giving up and using a third that did work... this up to a 10 second pause while the DNS tried to do things it coulnt possible do.. unticked the box and every thing started to happen instantly...

having a look at the traffic as i sugested will let you see the dns queries and log on quieries happen in real time. (if you want a hand setting eather real  up let me know)

you will see if the DNS requests are successful and in waht order they are used.
starboy42Author Commented:
Thanks Again all of you...
when I created Domain Controller I also made it DNS server(While Running Wizard(DCPROMO))
My Domian Controller's (Internet ProtocolsTCP/ IP) Setting is as follow...
Ip Address=
Subnet Mask=
Preffered DNS Server=

Now on All Clintes...
Ip Address=,3,4,5,6,7,8,9,10
Subnet Mask=
Preffered DNS Server=

I don't know how to manually configure DNS server sorry I'm newbie I think(not sure) this(DNS Configuration) would be reason behind this.
Now can anyone of you please guide me step by step how to configure DNS Server and checking it either working properly????
I hope for your(s) quick and positive response.
Rob WilliamsCommented:
One of the simplest tests it to use netdiag. It is on the operating installation CD. An outline with some good links can be found here:

Following may help you verify your configuration (from an earlier post of mine):
Assuming you have completed the server installation, installed Active Directory, and joined the workstations to the Domain, make sure DNS is configured as follows, assuming a single network adapter:
-The server's NIC should be configured with a static IP, the Internet router as the gateway, and only the server itself as the DNS server. Do not use an ISP DNS server here
-Each workstation should be configured using DHCP (obtain and IP address and DNS automatically) or if configured with static addresses; a static IP in the same subnet as the server, same subnet mask as the server, the gateway pointing to your Internet router, and the DNS server pointing ONLY to the server/domain controller. Again do not put an ISP's DNS server here
-In the DNS management console under Administrative tools, right click on the server name and choose properties. On the Forwarders tab add your ISP's DNS servers
-If the workstations are using DHCP, open the DHCP management console on the server under Administrative tools and click on the server name to expand it, click on the scope to expand it, right click on scope options and choose configure options. On the general tab add the Internet router's IP in #003 router, the server's IP in #006 DNS Servers, and the domain name and suffix under #015 such as mydomain.local
-If  DHCP is enabled on the router, rather than the server, it should really be disabled on the router and configured on the server. Enabling DHCP on the server assists with dynamic updates to DNS for older clients, allows for central management, and far more scope options.
-The DHCP client service should be running on servers and workstations even where you are not using DHCP assignments. The DHCP client service controls the dynamic DNS updates
If you have been having DNS problems, on the workstations that have been having problems you should clear the DNS cache by entering at a command line  
  ipconfig  /flushdns
and then
  ipconfig  /registerdns

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
starboy42Author Commented:
Thanks RobWill:
I m really very thank full to you for your this kind act. I've mentioned in my last post regarding "Static" "IP" which we are currently using in our office. your step by step instructions , sent URL and commands have done great work for me Thanks.
 I m really very thank full to ALL OF YOU who took interest and pay attention on my query BUNDLE  OF THANKS (ALL OF YOU).
Rob WilliamsCommented:
Very welcome starboy42. Glad to try to help.
Cheers !
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.