|
Home > Archive > CCIE > November 2002 > Help with Sniffer trace
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Help with Sniffer trace
|
|
| pseudocyber 2002-11-08, 4:05 pm |
| 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. | |
| subnet__zero 2002-11-10, 11:19 pm |
| From viewing what your expert mode is saying, it appears that your web server is having a slow response time to your client requests. Either it's taking a lot of hits or it's just slow. This error would be listed as "minor" in the expert, but there could be more to it, ie: window freezing, for example. If you dig deeper in the expert you should be able to find out more. The other 2 lines should be self explanatory to you. In my opinion, this error isn't the reason for your clients getting "jibberish" in the clients browser. I'm not an expert in Java, but could there be a Java mismatch between what's on the server and on the client side?
HTH | |
| pseudocyber 2002-11-11, 1:58 pm |
| Cool subnet_zero. Thanks.
I had come up through research, that the web server was busy. Or possibly network congestion. I have a hard time with the congestion piece - maybe on the link from the server to the switch - it's probably 100 full and I don't know where it is or how much it's getting hit.
Maybe I'll go dig that up ... 
Thanks again. | |
| Justin2112 2002-11-12, 3:24 pm |
| Just another thought,
Aside setting your port settings for the web server at 100/full; if your web server is plugged into a Cat 4000,5000, or 6500, you can use:
set port level mod/port high
This gives whatever is on that port a priority access to the switching backplane.
It's more of a tune-up ( fine-tune ) thing.
PEACE,
Justin | |
| pseudocyber 2002-11-13, 8:51 am |
| Hmm. I wonder if Nortel has the same command ... It's plugged into a Nortel passport 8600.
We think we identified the problem - btw. The app is Siebel7 and it doesn't like being cached on a transparent proxy ... |
|
|
|
|