![]() |
![]() |
![]() |
|||||
![]() |
![]() |
![]() |
![]() |
![]() |
|||
| Welcome
to Tech Support Forum home to more then 136,000 problems solved. Issues
have included: Spyware, Malware, Virus Issues, Windows, Microsoft,
Linux, Networking, Security, Hardware, and Gaming Getting your
problem solved is as easy as: 1. Registering for a free account 2. Asking your question 3. Receiving an answer Registered members: * See fewer ads. * And much more..
|
| Want to know how to post a question? click here | Having problems with spyware and pop-ups? First Steps |
|
|||||||
| Networking Support General Networking Support Forum |
![]() |
|
|
Thread Tools |
|
|
#1 (permalink) |
|
NetEngr/Geek
Join Date: Sep 2002
Location: Earth\US\NC\Charlotte
Posts: 1,394
OS: Win2K
|
Help with Sniffer trace
I'm trying to troubleshoot a problem that is occurring randomly on my network.
I have users going to a webpage (internally) and logging onto a web server which will load the front end of a Siebel7 db. I have nothing to do with this other than to prove it is NOT a network related issue. I don't work with the servers, the app dev, or the desktops. NAI Sniffer Pro captures from multiple machines having the problem have one error in common: Expert: HTTP Slow Server GET Response Time HTTP: R Port=1088 HTTP/1.O Status=OK text/html.charset=win What does this mean? The symptom is the user logs in on a '98 Laptop with IE 5 and 6 (both do it) and they'res supposed to get a bunch of javascripted "home page" on the Siebel7 machine. Instead, they get jibberish. This is happening on multiple VLAN's, multiple switches, multiple laptops and desktops.
__________________
AM = :coffee: PM = :cheers: CCNA, NNCSSx2, MCSE (NT), A+, CNA |
|
|
|
|
|
#2 (permalink) |
|
Registered User
Join Date: Dec 2002
Posts: 6
OS: 98
|
sniffer noob....
I only registered to answer this question...lol
Problem Description: An HTTP server response to a GET request has taken longer than the threshold value to reach the sender. ( these usually are values you have set or have been pre set by sniffer.) __________________________________________________________________ Probable Cause(s): 1. The server was very busy. 2. The server is overloaded. 3. The path to the sender from the receiver has long delays. 4. There may be an overloaded switch or router in the path. __________________________________________________________________ Recommended Action(s): 1. Upgrade the server’s CPU and /or memory. 2. Reduce the number of connections to the server. 3. Load balance your network. Are you in a switched enviroment? (Switched to the desktop?) If so log into the switch and look at the counters of that port where the server lives... |
|
|
|
![]() |
| Thread Tools | |
|
|