IE5 & Netscape differences over ports

Hi,
We are using Weblogic 5.1 Service Pack 6 on Solaris 2.6, with Apache server acting as a bridge. Apache actually does not serve any content and just forwards ALL requests to WLS. We have a problem at the moment that if you use internet explorer with WLS then it is extremely slow serving up pages. Weblogic listens on port 7001. If we use Netscape to connect then it runs with no slow downs at all, about three second to serve a page but if we use IE it takes nearly a minute. This delay occurs when the request goes through apache. If we directly access WLS on port 7001 then there is no such delay.
Any ideas on what could cause that delay? Is it an Apache bridge problem or a WLS one?
Cheers,
Barnaby
[att1.html]

I don't know if this is of any help, but it seems sp6 is buggy.
I had problems with keep-alive with the apache-weblogicbridge when using sp6, but all was fine with sp5,7 and 8.
I would consider trying a newer sp.
Good luck.
Gunnar
wilsonba <[email protected]> skrev i meldingsnyheter:[email protected]..
Hi,
We are using Weblogic 5.1 Service Pack 6 on Solaris 2.6, with Apache server acting as a bridge. Apache actually does not serve any content and just forwards ALL requests to WLS. We have a problem at the moment that if you use internet explorer with WLS then it is extremely slow serving up pages. Weblogic listens on port 7001. If we use Netscape to connect then it runs with no slow downs at all, about three second to serve a page but if we use IE it takes nearly a minute. This delay occurs when the request goes through apache. If we directly access WLS on port 7001 then there is no such delay.
Any ideas on what could cause that delay? Is it an Apache bridge problem or a WLS one?
Cheers,
Barnaby
[att1.html]

Similar Messages

New WSUS install does not respond to clients over ports 8530 or 8531

I've recently installed WSUS on a Server 2012 machine, and am struggling to get it to respond to requests from other hosts. I cannot get it to respond to any host in any manner, except for requests from itself.
My setup is as follows:
WSUS installed on a Server 2012 domain controller, DC01.
Other roles installed include AD CS, AD DS, DNS, IIS, and Print Services.
WSUS is using all default settings.
The firewall has inbound and outbound exceptions for ports 8530 and 8531
A bit of information about what's happening:
IIS will respond over port 80. I can open a Web browser from my workstation and connect to http://dc01/. If I attempt to connect to http://dc01:8530 (which I know should not work, but
should respond with a 403 error), it times out. Identical behavior is observed over port 8531 with https.
IIS will respond with a 403 if I make this same connection in a browser on DC01, it will work if I connect using either the loopback IP or hostname, but will time out if I attempt to make the connection using the server's local IP (IPv4).
If I try to connect from my workstation using the WSUS configuration snap-in, I get an error: The remote server could not be contacted. Please verify that IIS on the server is correctly configured and is running.
If I try to connect from DC01 using the WSUS configuration snap-in, it works correctly.
The above is true for both http (8530) and https (8531).
IIS logs show inbound connections from my workstation and show that IIS is responding with a 200. However, Wireshark running on DC01 shows three attempts by my workstation to open a connection -- three SYN packets, one initial attempt then two identical
retries -- over a period of about ten seconds, with no responses from DC01. If IIS is responding, the responses are getting lost sometime before they hit the NIC.
Bindings in IIS are correct, 8530 for http and 8531 for https.
Given that everything works fine when making a local connection, I think I can safely assume that WSUS itself is running properly, and the issue is related to IIS. Nonetheless, in the hopes of this simply being a failed install, I have uninstalled and reinstalled
both IIS and WSUS multiple times. (One thing to note, though I doubt it's related: WSUS consistently fails to set the path for the local update cache, failing the post-deployment configuration. I have to manually edit the UpdateServices-Services.xml file to
include the path for the local cache. Everything goes fine after I do that.)
I'm pretty stumped on this, and would happily accept any help. Thanks!

I've recently installed WSUS on a Server 2012 machine, and am struggling to get it to respond to requests from other hosts. I cannot get it to respond to any host in any manner, except for requests from itself.
My setup is as follows:
WSUS installed on a Server 2012 domain controller, DC01.
Other roles installed include AD CS, AD DS, DNS, IIS, and Print Services.
Fundamentally you have two issues here:
The first is the question of co-existence between WSUS and AD CS.
The second is whether this machine was a DC before, or after, you installed WSUS.
With Windows Server 2003 systems, running 'dcpromo' after installing IIS (and WSUS) would break IIS (and thus WSUS). With Windows Server 2012, installing WSUS with the AD DS role present results in a broken WSUS installation (if not an outright installation
failure). This is because on a WS2012 Domain Controller, there are GPO restrictions on "Log On As A Service" which impact the ability of certain LOCAL accounts to do so ... one of which being the Network Service which is required for WSUS and another local
use account, which is used for WID.
Regarding ports and IIS -- WSUS is designed to work on port 8530 by default on a Windows Server 2012 box. It can also be made to work on port 80, but you have to use the correct utilities and procedures to make that change. As for your observation
that "port 6000" seems to be a cutoff.... I'll (re)direct your attention to the installation of Active Directory Certificate Services, which I suspect is a contributing factor, and in general firewall configuration rules -- which are probably the most likely
culprit on the port range of 6000+ (not including 8530 which I promise you is open by a rule explicitly created by/for WSUS).
So, here's my suggestion:
Install the WSUS role first.
Install the AD DS role if you must (but Domain Controllers should not also be web or application server).
Install the AD CS role elsewhere.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

ALSB 2.5 features and ALSB 2.6 features & differences and porting features

ALSB 2.5 features and ALSB 2.6 features & differences and porting features?:8}

Migration features for ALSB 2.6. and new features in 2.6 Please refer to the documentation:
http://e-docs.bea.com/alsb/docs26/upgrade/
http://e-docs/alsb/docs26/relnotes/relnotes.html#whatsnew
Gregory Haardt
ALSB Prg. Manager
[email protected]

Difference Between Port Forwarding and Port Triggering.

Hi guys,
I'm lost! The differences between port forwarding and port triggering is driving me nuts! It all seems very subtle to me. Can anyone explain to me (in a very simple way) what exactly are their differences. Thanks in advance!!

Port Forwarding
The big difference between this and port triggering is that forwarding is fixed.. you forward a port and it is always forwarded.. IE available to connection.. basically the forwarded port is excluded from the fire walling abilities of the router. Second it is static and applies to one machine only. Whereas you could set port triggering to the router and thereafter any machine on the LAN can trigger it unless its already in use.. port forwarding must be specified for each individual machine.
Port forwarding requires you to give each PC on the network its own unique static IP address.. Although there is ssh port forwarding that can be set dynamically. Most users only have the option of static ip port forwarding.
The real downside of port forwarding is that it can be very tricky to set up... You may have to allow a series of ports on a machine and have to do that for each machine you want to allow through. Also routers often have limited abilities and may not allow you the ability to forward a port or select the service you require.
Port Triggering
This is a way of Dynamically assigning a service to a port WHEN it is required by an outgoing service. The port is initially not allowed so nothing can get in and you are protected by your network.
A good example of this is when using Yahoo! voice .. the voice works fine for a few minutes after you connect to Yahoo! then Yahoo! sends some kind of packet that requires a response from your PC... The packet is allowed in through your router no prob but the outgoing reply is not authorized to open a port on the router and is thus blocked.
'ope this helps

Pppoe over port-channels on ios xe

has the ability to do pppoe and QinQ over port-channels been added to IOS XE? as of 2.6 it was not but I cannot find any documentation on 3.1-3.3 to say that it has or hasn't
Does any one use a asr1000 as a BRAS and if so how do you handle redundancy in case of the loss of a primary interface handling your pppoe sessions?

Hi Artyom,
Try removing "ipv6 nd managed-config-flag" and see if it helps.
Regards

Difference between Port Channel and VPc

Hi Friends,
Could you please provide the difference between Port Channel and VPC.
Regards,
Zaheer

Read :)
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-3000-series-switches/white_paper_c11-685753.html
Virtual PortChannel Technology
Virtual PortChannels (vPCs) allow links that are physically connected to two different Cisco® switches to appear to a third downstream device to be coming from a single device and as part of a single PortChannel. The third device can be a switch, a server, or any other networking device that supports IEEE 802.3ad PortChannels.
Cisco NX-OS Software vPCs and Cisco Catalyst® Virtual Switching Systems (VSS) are similar technologies. For Cisco EtherChannel technology, the term “multichassis EtherChannel” (MCEC) refers to either technology interchangeably.
vPC allows the creation of Layer 2 PortChannels that span two switches. At the time of this writing, vPC is implemented on the Cisco Nexus® 7000 and 5000 Series platforms (with or without Cisco Nexus 2000 Series Fabric Extenders).

Stratus tunneling over ports 443 and/or 80

Would it be possible to have Stratus listen on ports 443 and
80; and would Flash Player 10 indeed fall back to those ports, as
with FMS?
I am dealing with a customer who has difficulty opening 1935
due to corporate policies.
I have no information about port 10000+. Hopefully they pose
no problem.
Kind Regards,
Frans

The older RTMP operates over TCP port 1935 and falls back to
tunneling over 443 and/or 80.
The newer RTMFP uses UDP and requires the ability to make
outbound connections to 1935 and also higher port numbers in order
to establish a server connection.
Running over port 443 and 80 UDP wouldn't help, the firewall
is likely configured to open up TCP 443 (HTTPS) and TCP 80 (HTTP)
while still blocking UDP.
If your application needs to work in the presence of
UDP-blocking firewalls (and note that we do several things to get
through them, if they do allow internally-initiated UDP sessions),
you'll need to code your own fallback to a TCP protocol like RTMP
or HTTP.

Authenticated SMTP/SSL over port 465

Does Oracle E-mail support authenticated SMTP over SSL on port 465? - E

Yes,
both TLS and SSL are possible with 10.1.1. Tried myself. A little bit tweaking essmi's accordingly, applying certificates, and adjusting listener.ora for LISTENER_ES.
Note: essmi only.
- Torsten

Difference in port creation in idx1 and we21

i m in my ABAP stack of XI..
what is the difference in creating port in idx1 and we21

Hey
follow the below steps for IDOC to FIle
Configuration to be done on R/3 server
RFC destination(SM59):Pointing towards the XI server
Port(WE21):Use the RFC destination created above
Logical system(BD54):Logical system name for the XI server,it's advised to be of the form sid"CLNT"client(if ur sid is XD1,and client is 110,the it should be XD1CLNT110)
Partner Profile(WE20):use the same name as that of the Logical system name created above i.e. XD1CLNT110.
Configuration to be done on XI server.
Nothin need to be done here,jst make sure ur IDX2 (IDOC metadata) is correct.
SLD
Two business system's have to be created.
first Business system will use the Logical system name of the R/3 server and will be used as a sender service.configured of type Webaas ABAP
second business syatem will use the Logical system name u created in BD54 and will be used as a receiver service.Configured of type Third party.
Note:Most of the time RFC destination and ports are already created in both R/3 server and XI server,so u can use the existing ones rather than creatin ur own.
thanx
ahmad

USB redirect over port 443 only

I've done a little research on this issue, according to VMware (At least what I've read) there are 2 ports on our firewall which need to be opened to allow usb redirect, is there anyway to do this over 443 ONLY?
cheers,
-Steve

If you use PCoIP you need at least 3 ports open, 443/TCP, 4172/TCP, 4172/UDP.
That will also allow for USB redirection that is tunneled through 443 to the security server.
If you are using RDP then I think that only 443 is needed.
// Linjo

MPLS-TE over Port-channel on 7206

Hi Guys,
I need an information: on a 7206vxr (ios 15.2S) I tried to configure an mpls-te over an etherchannel link but it doesn't seems to work (the TE tunnel never go up and the "show mpls traffic-eng tunnel tunnel 0 det" show the reason as "invalid path" but I guarantee that it's absolutely valid).
I tried to search into feature navigator but I don't found any of that: It figure out as 7206 don't support it, it's right?
Thanks in advance
Giulio

Hi Giulio, can you please confirm that to me?
In the IOS feature navigator the feature "MPLS TE - Bundled interface support (EtherChannel and MLP)" seems to be available only in 7600 platform and not in 7200 series. And with 7200 series I have had some difficulty with MPLS TE in a port-channel interface.
Thankyou
Gianrico
Itesys srl

Portege R500 - anybody using DVI over Port Replicator II on WIndows 7 Beta?

Hi,
im using the WIndows 7 beta on my R500 and it's runnig everything well except the DVI-Port (over the Slim Port Replicator II).
All I have installed are the Fingreprint-Software, the bluetooth-stack (which were recommended as solution by the action-centre) and the "TOSHIBA Value Added Package" which adds the Power Management software, control over the 2 hardware Buttons and gives the FN-onscreen-menu to control the FN1-9 functions.
I think I can say it is definatively an driver issue, because if I start the R500 the windows loading-screen is shown on my external screen but when he switches to the desktop the external screen turns off and the desktop appears on the laptop screen. Also no chance to activate it via FN+F5.
I tried it with the buildin Windows 7 driver, the newest intel driver (15.8.3) and the vista driver provided by toshiba (7.14.10.1244), but unlucky none of them works :(
Btw: the vga output works, but only UNdocked :(
Has anyone a solution or a hint what to do or try?

Hello,
the second monitor does not appear in the display settings if the laptop is docked. Even connected to the vga it is not been recognized while this state.
Undocked the vga port works immediately and is shown in the display settings and over FN+F5!
With one driver (didn't remember which one exactely) the FN+F5 menu showed me all options (docked!) (Internal, vga+int, vga only, dvi+int, dvi only) but i couldnt switch to dvi. It was the same behaviour like under XP where I had to boot the Laptop with the DVI-TFT connected (i used Hibernation everytime i docked the r500). But under Win7 this worked, as I said before, only for the "pre-boot" sequence. The windows loading screen showed up, but during switching to the desktop the DVI-port got deactivated.
Recently i dont know my actual BIOS Version, I will check this and try the newest version.

Difference between ports

It appears that we can use either of these two ports in the URL to run web forms:
Oracle HTTP Server port = 7779
Oracle HTTP Server Listen port = 7780
Is only one of these the correct one to use ?
What is the difference ?

Kevin,
this seems to be very Application Server specific, so I am walking on thin ice here.
However, if you go to
<As Middletier Installation>\install\portlist.ini
then this gives you a list of all ports configured when installing Oracle Application Server.
In my case I have port 80 and port 7779 as the "Listen port". I also see that Webcache uses port 80, which means that all calls to port 80 will go through Webcache first.
I checked teh Webcache administration and this shows a log for all Forms that I run through port 80.
My assumption thus is that using port 7779 in your case means running Forms through Webcache, while using port 7780 will not use it.
Frank

Soft phone takes over port 80?

I'm using Cisco IP Communicator 2.0.1.1. When the software is running, it listens on port 80 (HTTP) and as a result my local IIS no longer gets any traffic because Communicator intercepts it. Is there any way to turn this off? I absolutely must have my local IIS working, and I'll be forced to go to a hard phone if this can't be solved.

Has anyone noticed that the app reads this key about every 10th of second while it's running? This doesn't seem normal to me. Plus it would be nice to figure out how to change the port.
Also, where should I go for updated versions of it? Mine keeps hanging my machine every now and then when I close it. Mouse keeps working but I'm not able to click or start any other progs. usually have to hard reset my box.
procmon shows this:
"Sequence","Time of Day","Process Name","PID","Operation","Path","Result","Detail"
"55282","1:27:02.6249521 PM","Communicator.exe","3012","RegQueryValue","HKLM\SOFTWARE\Cisco Systems, Inc.\Communicator\WebServerDisabled","SUCCESS","Type: REG_DWORD, Length: 4, Data: 1"
"55283","1:27:02.6249965 PM","Communicator.exe","3012","RegCloseKey","HKLM\SOFTWARE\Cisco Systems, Inc.\Communicator","SUCCESS",""
"55284","1:27:02.6250083 PM","Communicator.exe","3012","RegOpenKey","HKLM\SOFTWARE\Cisco Systems, Inc.\Communicator","SUCCESS","Desired Access: Read"
"55285","1:27:02.6250289 PM","Communicator.exe","3012","RegQueryValue","HKLM\SOFTWARE\Cisco Systems, Inc.\Communicator\WebServerDisabled","SUCCESS","Type: REG_DWORD, Length: 4, Data: 1"
"55286","1:27:02.6250731 PM","Communicator.exe","3012","RegCloseKey","HKLM\SOFTWARE\Cisco Systems, Inc.\Communicator","SUCCESS",""
"55312","1:27:02.6343363 PM","Communicator.exe","3012","RegOpenKey","HKLM\SOFTWARE\Cisco Systems, Inc.\Communicator","SUCCESS","Desired Access: Read"
"55313","1:27:02.6343835 PM","Communicator.exe","3012","RegQueryValue","HKLM\SOFTWARE\Cisco Systems, Inc.\Communicator\WebServerDisabled","SUCCESS","Type: REG_DWORD, Length: 4, Data: 1"
"55314","1:27:02.6344843 PM","Communicator.exe","3012","RegCloseKey","HKLM\SOFTWARE\Cisco Systems, Inc.\Communicator","SUCCESS",""
"55315","1:27:02.6344977 PM","Communicator.exe","3012","RegOpenKey","HKLM\SOFTWARE\Cisco Systems, Inc.\Communicator","SUCCESS","Desired Access: Read"
"55316","1:27:02.6345218 PM","Communicator.exe","3012","RegQueryValue","HKLM\SOFTWARE\Cisco Systems, Inc.\Communicator\WebServerDisabled","SUCCESS","Type: REG_DWORD, Length: 4, Data: 1"
"55317","1:27:02.6345681 PM","Communicator.exe","3012","RegCloseKey","HKLM\SOFTWARE\Cisco Systems, Inc.\Communicator","SUCCESS",""
"55318","1:27:02.6345801 PM","Communicator.exe","3012","RegOpenKey","HKLM\SOFTWARE\Cisco Systems, Inc.\Communicator","SUCCESS","Desired Access: Read"
"55319","1:27:02.6346014 PM","Communicator.exe","3012","RegQueryValue","HKLM\SOFTWARE\Cisco Systems, Inc.\Communicator\WebServerDisabled","SUCCESS","Type: REG_DWORD, Length: 4, Data: 1"

What is the Difference btwn PORT and SOCKET

Hai, what is the diff. between Port and Socket and is Port related to Hardware?

Or another way, A socket is the connection you make, the port is the channel that the socket connected on.
A lot of ports are assigned to a certain use eg 80 = http. So when you try to access a web page, your browser tries to make a connection to the server on port 80, the server software will listen on port 80 on the server computer for htp request.

IE5 & Netscape differences over ports

Similar Messages

Maybe you are looking for