I've done this, no problems. Id like something that sends larger files and logs the results.
Main Topics
Browse All TopicsEvery so often, all of my machines drop their connection to the server for an instant. It isn't really noticeable in any program but the accounting package since it accesses the network so often.
The server (2003 Standard) has no errors in the logs, nor do the workstations. When I do quick network tests, everything is fine.
However, the accounting package randomly reports problems connecting to its data.
It's not the accounting package. The previous accounting package had the same problems.
How do i tell where the problem is? Is there a tool that will constantly send and receive files to and from the server and report dropped connections?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi,
Also you can sniff network traffic from your network and check for possible errors. Wireshark is handy utility for such purpose;
www.wireshark.org
Incase you are new to Wireshark;
wiki.wireshark.org
Try
ping -t -f -l 1472 <ipaddress>
Where -f is DO NOT Fragment
and -l is declaring the packet size.
What time period are the drops? Do they occur 24 hours a day, 7 days a week? Or just during business hours. Is the accounting app on its own server? Is that on a gigabit port? What do the switch logs have to say?
I let a ping run overnight.
Sent = 34685, Received = 34651, Lost = 34
I can only say for certain that the drops occur during business hours as they are only reported by users of the accounting app. That is why I would like to find an app that simulates that kind of usage and keeps a log.
The app is not on its own server. This is a small network with only 8 clients. The server runs AD, DNS, DHCP and File Sharing. It is a GB network card, but the switch is 10/100
The switch isn't managed.
I would suggest Wireshark as per the above user or MRTG. But if this is that small you might want to try just adding an additional network card to the server or upgrading the switch to a managed 8 port gig switch. You can get the HP Procurve 1800-8G Switch for < $200 and it's web managed. can't complain about that. Seems like a cheap trial and will increase overall network communciations between your clients and the server(s)
Yes, wireshark will only capture packets. It will only capture what is being sent to your NIC, so if you cannot manage that switch and program a monitor port then I suggest switching to a managed switch per my comment above. You are probably only capturing packets coming to your PC if you installed it on your PC. If you installed it on the main server then you would need to examine the packets around the time that there was a drop and see what was going on in your network. You would need to do some packet diving, some real details detective work....
Again, for $200 bucks put a managed switch in there with gig ports
You clue is the 34 lost packets. We need to find out why those packets are getting lost.
I would agree that upgrading the switch is not a bad idea since you have GB NIC but I would check the settings on the server and the switch (if the switch is managed) , specifically I would make sure the duplex settings are correct (both should be full-deplex connections.
If the duplex settings are both set to auto or full-duplex then we should look into what wireshark is finding when the packets are getting lost. Also record the times when you get a lost packet and look in the Windows System log to see if there were any issues during that time, you may find that the system is logging some information entries (you are looking for the source to be "Tcpip" and possibly event id's of 4201 and 4202) that show the network card disconnecting and reconnecting which could be a network card going bad.
I ran wireshark all day today, I'm getting a lot of this:
"281864","35897.095884","1
"281865","35897.095955","1
"281866","35897.095991","1
"185788","32164.014982","1
"571025","51520.910126","1
"571026","51520.910474","1
"744145","53983.909503","1
"744146","53983.909614","1
"195956","32484.026545","1
"195957","32484.048277","1
It looks to me like your problem could be DNS related by looking at the first couple of packets which are DNS failures. I would check your DNS server for any issues and maybe set one of the clients that is having a problem to access the server using the IP address rather than a name and see if the problem goes away on that machine.
The third packet looks like a ping failure due to a firewall blocking the port.
The rest of the trace looks like Samba server errors which could also be the problem if the server/clients are using Samba shares.
I'm still working on this problem....
No DNS errors with DCDIAG.
I've replaced the Server's: NIC, CABLE, SWITCH, ROUTER.
When I move the accounting application to a workstaton, everything is fine.
There is no firewall on the server at this time. I am using McAfee on the workstations though. McAfee has a firewall portion that is dissabled.
The advise to access the server via IP is interesting. Is there a way that I can test server-workstation connection to a shared folder without using IP? I don't want to put the accounting package back on the server until I have this sorted out.
If you want to test that a share is accessible all you need to do is map a network drive or use Windows Explorer to see if you can view the share. To map a network drive using the command line you can issue the following command...
net use X: \\SERVERNAME\SHARENAME
Just
You can also just type \\SERVERNAME\SHARENAME into a Windows Explorer window and it should either show up or ask for the username/password if the share is protected.
Business Accounts
Answer for Membership
by: johnb6767Posted on 2009-01-18 at 21:33:48ID: 23408348
Easiest thing to do, from an accounting machine....
ping -t server'sipaddress
And let it run...If the package drops, but the pings dont, then you might need to look at the app, or vice versa....