Issue : - Accessing the server from client via any running application software is too long to respond.
Common Causes of Connectivity problems:-
1). Network adapters and switch ports with mismatching duplex levels or transfer speed settings.
2). Network adapters or switches with transmission rates of 10/100 or
10/100/1000 megabits per second (Mbps) not functioning switch over
correctly.
3). The network adapter is incompatible with the motherboard or other hardware or software components and drivers.
4). Firewall software not functioning properly, due to bugs in its network connectivity check segment.
Cases to Check:-
1). Check for connectivity responses between Server and Client's using PING
2). Check system event logs for network card/connectivity related errors
3). Check for networking devices between Server and Client i.e swithces,lan cables, lan card.
Typically occur because of incorrect network adapters, incorrect switch settings, faulty hardware, or driver issues.
4). Check for Windows Firewall / Special Antivirus Software Firewall installed in both Server and Clients.
TroubleShooting steps:-
1). Ping the Server from Client's with issue or From Client's to the Server (use domain name or IP to ping)
Ex. ping WindowsServer -t
-"t"- for continuos ping
Sample Output:-
"ping WindowsServer -t"
Pinging 192.168.6.4 with 32 bytes of data:
Reply from 192.168.6.4: bytes=32 time<1ms TTL=64
Reply from 192.168.6.4: bytes=32 time<1ms TTL=64
Reply from 192.168.6.4: bytes=32 time<1ms TTL=64
Reply from 192.168.6.4: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.6.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Ex. ping LinuxServer
The response time in millisecond should less than or equal to 1 or 2,
rarely sometimes other lower latencies would come without any data
transmission.(Environment: Server and Clients's in the same network).
There should not be any LOSS.
Also check with preloaded data for server client reponses by the following:
"ping WINDOWSSERVER -l 45000 -t "
Pinging kmuadmin [192.168.6.74] with 45000 bytes of data:
Reply from 192.168.6.74: bytes=45000 time=9ms TTL=128
Reply from 192.168.6.74: bytes=45000 time=9ms TTL=128
Reply from 192.168.6.74: bytes=45000 time=9ms TTL=128
Reply from 192.168.6.74: bytes=45000 time=9ms TTL=128
Ping statistics for 192.168.6.74:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 9ms, Average = 9ms
2). Check the systems event logs using eventvwr (Windows) or dmesg/syslog (Linux)
3). Check for whether the network adapter is compatible with Microsoft Windows or Linux Operating systems
-Check the link http://winqual.microsoft.com/HCL/Default.aspx?m=x
4). Check computers that use the correct gateway that are plugged into the same hub or switch.
5). If the computers do not experience network connectivity problems,
the problem may be a faulty network adapter on one computer.
6). Check for Server's/Client's motherboard must be updated with latest
BIOS from vendor's Web site or contact your hardware vendor
7). Make sure that all complementing network resources (network
adapter, hub, and switch) are set to the same speed and duplex level.
Force it to use full-duplex.
8). Reset the switch, restart the client, and test the connectivity.
9). Manually set the network adapter of the computer that has
connectivity problems to half-duplex and a lower speed 10mbps , whether
connection can be established at a lower transmission speed.
10). To increase performance, increase the speed settings manually to
100 Mbps, and then restart the computers. Test for network connectivity
loss, increase the setting to full-duplex, and then restart the
computers. If network loss occurs, reduce the duplex setting and the
speed to the previous settings.
11). Swap the network cable between the failing system and the hub or switch.
12). Replace the network adapter with a network adapter that has been
tested and proven reliable. To do this, follow these steps:
-a)Remove the network adapter diagnostics program.
-b)Remove the network adapter in Network properties.
-c)Install the new network adapter.
13). Disable the network adapter settings and Enable it .
Right click network properties on desktop, choose the correct LAN connection, right click disable,enable it .
If this is the case, there would be issue with Software Firewall
installed, contact software firewall service provider to get them fixed.
14). Put the continuous ping's from Server to Client/Client's by adding
successive manner, Disable the Software Firewall install and check
whether response time is feasible in all ping OUTPUT'S(ref:attachments)
If this is the case contact software firewall service provider to get them fixed.
Analysis Pending:
Free tools(Network Monitor) available to sort out this issue , followed by evaluation later.
Attachments:
Sample network choking ping screenshot attached.
Note:
Please contact system-administrator for firewall issue.Disabling any
antivirus/firewall services without knowledge of them is restrictable,
which leads to crash the windows operating system.
