jdscudder

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2013-06-11
19:13
508 views
OES 11 SP1 unable to browse Internet from desktop
I have two OES 11 SP1 servers that exhibit the same behavior. I cannot browse the Internet from the desktop. I can use the browser to ftp, but when I try http, it says it connects to the site, but it eventually times out. I can ping the sites, I can resolve the host names, I can do everything but http. I have other OES 2 servers on the same subnet that have no problems. Has anyone else experienced this. Have you found a solution. Thanks.
3 Replies


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2013-06-11
19:31
Get a LAN trace and post it. Also, can you access any internal things
(like iManager or iMonitor on an OES 2 box, or another internal website)
from those boxes? Post that LAN trace too. What about testing with
something like curl?
Code:
----------
sudo /usr/sbin/tcpdump -n -s 0 -i eth0 -w /tmp/http0.cap port
#Use Ctrl+c to stop the trace when done, then post the /tmp/http0.cap
----------
Curl test:
Code:
----------
curl -v http://www.google.com/
----------
Good luck.
(like iManager or iMonitor on an OES 2 box, or another internal website)
from those boxes? Post that LAN trace too. What about testing with
something like curl?
Code:
----------
sudo /usr/sbin/tcpdump -n -s 0 -i eth0 -w /tmp/http0.cap port
#Use Ctrl+c to stop the trace when done, then post the /tmp/http0.cap
----------
Curl test:
Code:
----------
curl -v http://www.google.com/
----------
Good luck.
jdscudder

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2013-06-12
22:24
Thanks for your reply. I get tcpdump syntax errors. The curl test gives me a couple of pages of code. Do you need that posted also?


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2013-06-12
23:07
Doh! Left an invalid option there... my bad:
Code:
----------
sudo /usr/sbin/tcpdump -n -s 0 -i eth0 -w /tmp/http0.cap
#Use Ctrl+c to stop the trace when done, then post the /tmp/http0.cap
----------
The curl output would be nice to have, in particular if you redirect the
regular stuff away and just show the debugging pieces:
Code:
----------
curl -v http://www.google.com/ >/dev/null
----------
The idea is to get information about what's going on near the wire.
Good luck.
Code:
----------
sudo /usr/sbin/tcpdump -n -s 0 -i eth0 -w /tmp/http0.cap
#Use Ctrl+c to stop the trace when done, then post the /tmp/http0.cap
----------
The curl output would be nice to have, in particular if you redirect the
regular stuff away and just show the debugging pieces:
Code:
----------
curl -v http://www.google.com/ >/dev/null
----------
The idea is to get information about what's going on near the wire.
Good luck.