Connection Block

Hello friends
I am not able to see the <b>Connection block</b> on my Visual Composer desktop which shows the url for the portal

Hi Rishi,
Check this thread for all of the "Getting started" and documentation:
Getting started
Regards,
Natty

Similar Messages

[Solved]TCP connection blocked in SYN_SENT status

I set up openssh daemon on my host and try to ssh to localhost to ensure it working. However the connection blocked for minutes then get
ssh: connect to host localhost port 22: Connection timed out
I checked "netstat -antup" output, the daemon was started and the new connection was in SYN_SENT status before time out
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 1 127.0.0.1:38127 127.0.0.1:22 SYN_SENT -
I did not add any iptables rules on my host, here is the log of sysctl net.ipv4
net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_sack = 1
net.ipv4.tcp_retrans_collapse = 1
net.ipv4.ip_forward = 0
net.ipv4.ip_default_ttl = 64
net.ipv4.ip_no_pmtu_disc = 0
net.ipv4.ip_nonlocal_bind = 0
net.ipv4.tcp_syn_retries = 5
net.ipv4.tcp_synack_retries = 5
net.ipv4.tcp_max_orphans = 16384
net.ipv4.tcp_max_tw_buckets = 180000
net.ipv4.ipfrag_high_thresh = 262144
net.ipv4.ipfrag_low_thresh = 196608
net.ipv4.ip_dynaddr = 0
net.ipv4.ipfrag_time = 30
net.ipv4.tcp_keepalive_time = 7200
net.ipv4.tcp_keepalive_probes = 9
net.ipv4.tcp_keepalive_intvl = 75
net.ipv4.tcp_retries1 = 3
net.ipv4.tcp_retries2 = 15
net.ipv4.tcp_fin_timeout = 60
net.ipv4.tcp_syncookies = 0
net.ipv4.tcp_tw_recycle = 0
net.ipv4.tcp_abort_on_overflow = 0
net.ipv4.tcp_stdurg = 0
net.ipv4.tcp_rfc1337 = 0
net.ipv4.tcp_max_syn_backlog = 1024
net.ipv4.ip_local_port_range = 32768 61000
net.ipv4.icmp_echo_ignore_all = 0
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.icmp_ignore_bogus_error_responses = 1
net.ipv4.icmp_errors_use_inbound_ifaddr = 0
error: permission denied on key 'net.ipv4.route.flush'
net.ipv4.route.min_delay = 2
net.ipv4.route.max_delay = 10
net.ipv4.route.gc_thresh = 4096
net.ipv4.route.max_size = 65536
net.ipv4.route.gc_min_interval = 0
net.ipv4.route.gc_min_interval_ms = 500
net.ipv4.route.gc_timeout = 300
net.ipv4.route.gc_interval = 60
net.ipv4.route.redirect_load = 5
net.ipv4.route.redirect_number = 9
net.ipv4.route.redirect_silence = 5120
net.ipv4.route.error_cost = 250
net.ipv4.route.error_burst = 1250
net.ipv4.route.gc_elasticity = 8
net.ipv4.route.mtu_expires = 600
net.ipv4.route.min_pmtu = 552
net.ipv4.route.min_adv_mss = 256
net.ipv4.route.secret_interval = 600
net.ipv4.igmp_max_memberships = 20
net.ipv4.igmp_max_msf = 10
net.ipv4.inet_peer_threshold = 65664
net.ipv4.inet_peer_minttl = 120
net.ipv4.inet_peer_maxttl = 600
net.ipv4.inet_peer_gc_mintime = 10
net.ipv4.inet_peer_gc_maxtime = 120
net.ipv4.tcp_orphan_retries = 0
net.ipv4.tcp_fack = 1
net.ipv4.tcp_reordering = 3
net.ipv4.tcp_ecn = 0
net.ipv4.tcp_dsack = 1
net.ipv4.tcp_mem = 47808 63744 95616
net.ipv4.tcp_wmem = 4096 16384 2039808
net.ipv4.tcp_rmem = 4096 87380 2039808
net.ipv4.tcp_app_win = 31
net.ipv4.tcp_adv_win_scale = 2
net.ipv4.icmp_ratelimit = 250
net.ipv4.icmp_ratemask = 6168
net.ipv4.tcp_tw_reuse = 0
net.ipv4.tcp_frto = 0
net.ipv4.tcp_low_latency = 0
net.ipv4.ipfrag_secret_interval = 600
net.ipv4.ipfrag_max_dist = 64
net.ipv4.tcp_no_metrics_save = 0
net.ipv4.tcp_moderate_rcvbuf = 1
net.ipv4.tcp_tso_win_divisor = 3
net.ipv4.tcp_congestion_control = cubic
net.ipv4.tcp_abc = 0
net.ipv4.tcp_mtu_probing = 0
net.ipv4.tcp_base_mss = 512
net.ipv4.tcp_workaround_signed_windows = 0
net.ipv4.tcp_dma_copybreak = 4096
net.ipv4.tcp_slow_start_after_idle = 1
net.ipv4.cipso_cache_enable = 1
net.ipv4.cipso_cache_bucket_size = 10
net.ipv4.cipso_rbm_optfmt = 0
net.ipv4.cipso_rbm_strictvalid = 1
net.ipv4.tcp_available_congestion_control = cubic reno
net.ipv4.tcp_allowed_congestion_control = cubic reno
net.ipv4.neigh.default.mcast_solicit = 3
net.ipv4.neigh.default.ucast_solicit = 3
net.ipv4.neigh.default.app_solicit = 0
net.ipv4.neigh.default.retrans_time = 100
net.ipv4.neigh.default.base_reachable_time = 30
net.ipv4.neigh.default.delay_first_probe_time = 5
net.ipv4.neigh.default.gc_stale_time = 60
net.ipv4.neigh.default.unres_qlen = 3
net.ipv4.neigh.default.proxy_qlen = 64
net.ipv4.neigh.default.anycast_delay = 100
net.ipv4.neigh.default.proxy_delay = 80
net.ipv4.neigh.default.locktime = 100
net.ipv4.neigh.default.gc_interval = 30
net.ipv4.neigh.default.gc_thresh1 = 128
net.ipv4.neigh.default.gc_thresh2 = 512
net.ipv4.neigh.default.gc_thresh3 = 1024
net.ipv4.neigh.default.retrans_time_ms = 1000
net.ipv4.neigh.default.base_reachable_time_ms = 30000
net.ipv4.neigh.lo.mcast_solicit = 3
net.ipv4.neigh.lo.ucast_solicit = 3
net.ipv4.neigh.lo.app_solicit = 0
net.ipv4.neigh.lo.retrans_time = 100
net.ipv4.neigh.lo.base_reachable_time = 30
net.ipv4.neigh.lo.delay_first_probe_time = 5
net.ipv4.neigh.lo.gc_stale_time = 60
net.ipv4.neigh.lo.unres_qlen = 3
net.ipv4.neigh.lo.proxy_qlen = 64
net.ipv4.neigh.lo.anycast_delay = 100
net.ipv4.neigh.lo.proxy_delay = 80
net.ipv4.neigh.lo.locktime = 100
net.ipv4.neigh.lo.retrans_time_ms = 1000
net.ipv4.neigh.lo.base_reachable_time_ms = 30000
net.ipv4.neigh.eth0.mcast_solicit = 3
net.ipv4.neigh.eth0.ucast_solicit = 3
net.ipv4.neigh.eth0.app_solicit = 0
net.ipv4.neigh.eth0.retrans_time = 100
net.ipv4.neigh.eth0.base_reachable_time = 30
net.ipv4.neigh.eth0.delay_first_probe_time = 5
net.ipv4.neigh.eth0.gc_stale_time = 60
net.ipv4.neigh.eth0.unres_qlen = 3
net.ipv4.neigh.eth0.proxy_qlen = 64
net.ipv4.neigh.eth0.anycast_delay = 100
net.ipv4.neigh.eth0.proxy_delay = 80
net.ipv4.neigh.eth0.locktime = 100
net.ipv4.neigh.eth0.retrans_time_ms = 1000
net.ipv4.neigh.eth0.base_reachable_time_ms = 30000
net.ipv4.neigh.wlan0.mcast_solicit = 3
net.ipv4.neigh.wlan0.ucast_solicit = 3
net.ipv4.neigh.wlan0.app_solicit = 0
net.ipv4.neigh.wlan0.retrans_time = 100
net.ipv4.neigh.wlan0.base_reachable_time = 30
net.ipv4.neigh.wlan0.delay_first_probe_time = 5
net.ipv4.neigh.wlan0.gc_stale_time = 60
net.ipv4.neigh.wlan0.unres_qlen = 3
net.ipv4.neigh.wlan0.proxy_qlen = 64
net.ipv4.neigh.wlan0.anycast_delay = 100
net.ipv4.neigh.wlan0.proxy_delay = 80
net.ipv4.neigh.wlan0.locktime = 100
net.ipv4.neigh.wlan0.retrans_time_ms = 1000
net.ipv4.neigh.wlan0.base_reachable_time_ms = 30000
net.ipv4.conf.all.forwarding = 0
net.ipv4.conf.all.mc_forwarding = 0
net.ipv4.conf.all.accept_redirects = 1
net.ipv4.conf.all.secure_redirects = 1
net.ipv4.conf.all.shared_media = 1
net.ipv4.conf.all.rp_filter = 0
net.ipv4.conf.all.send_redirects = 1
net.ipv4.conf.all.accept_source_route = 0
net.ipv4.conf.all.proxy_arp = 0
net.ipv4.conf.all.medium_id = 0
net.ipv4.conf.all.bootp_relay = 0
net.ipv4.conf.all.log_martians = 0
net.ipv4.conf.all.tag = 0
net.ipv4.conf.all.arp_filter = 0
net.ipv4.conf.all.arp_announce = 0
net.ipv4.conf.all.arp_ignore = 0
net.ipv4.conf.all.arp_accept = 0
net.ipv4.conf.all.disable_xfrm = 0
net.ipv4.conf.all.disable_policy = 0
net.ipv4.conf.all.force_igmp_version = 0
net.ipv4.conf.all.promote_secondaries = 0
net.ipv4.conf.default.forwarding = 0
net.ipv4.conf.default.mc_forwarding = 0
net.ipv4.conf.default.accept_redirects = 1
net.ipv4.conf.default.secure_redirects = 1
net.ipv4.conf.default.shared_media = 1
net.ipv4.conf.default.rp_filter = 0
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.default.accept_source_route = 1
net.ipv4.conf.default.proxy_arp = 0
net.ipv4.conf.default.medium_id = 0
net.ipv4.conf.default.bootp_relay = 0
net.ipv4.conf.default.log_martians = 0
net.ipv4.conf.default.tag = 0
net.ipv4.conf.default.arp_filter = 0
net.ipv4.conf.default.arp_announce = 0
net.ipv4.conf.default.arp_ignore = 0
net.ipv4.conf.default.arp_accept = 0
net.ipv4.conf.default.disable_xfrm = 0
net.ipv4.conf.default.disable_policy = 0
net.ipv4.conf.default.force_igmp_version = 0
net.ipv4.conf.default.promote_secondaries = 0
net.ipv4.conf.lo.forwarding = 0
net.ipv4.conf.lo.mc_forwarding = 0
net.ipv4.conf.lo.accept_redirects = 1
net.ipv4.conf.lo.secure_redirects = 1
net.ipv4.conf.lo.shared_media = 1
net.ipv4.conf.lo.rp_filter = 0
net.ipv4.conf.lo.send_redirects = 1
net.ipv4.conf.lo.accept_source_route = 1
net.ipv4.conf.lo.proxy_arp = 0
net.ipv4.conf.lo.medium_id = 0
net.ipv4.conf.lo.bootp_relay = 0
net.ipv4.conf.lo.log_martians = 0
net.ipv4.conf.lo.tag = 0
net.ipv4.conf.lo.arp_filter = 0
net.ipv4.conf.lo.arp_announce = 0
net.ipv4.conf.lo.arp_ignore = 0
net.ipv4.conf.lo.arp_accept = 0
net.ipv4.conf.lo.disable_xfrm = 1
net.ipv4.conf.lo.disable_policy = 1
net.ipv4.conf.lo.force_igmp_version = 0
net.ipv4.conf.lo.promote_secondaries = 0
net.ipv4.conf.eth0.forwarding = 0
net.ipv4.conf.eth0.mc_forwarding = 0
net.ipv4.conf.eth0.accept_redirects = 1
net.ipv4.conf.eth0.secure_redirects = 1
net.ipv4.conf.eth0.shared_media = 1
net.ipv4.conf.eth0.rp_filter = 0
net.ipv4.conf.eth0.send_redirects = 1
net.ipv4.conf.eth0.accept_source_route = 1
net.ipv4.conf.eth0.proxy_arp = 0
net.ipv4.conf.eth0.medium_id = 0
net.ipv4.conf.eth0.bootp_relay = 0
net.ipv4.conf.eth0.log_martians = 0
net.ipv4.conf.eth0.tag = 0
net.ipv4.conf.eth0.arp_filter = 0
net.ipv4.conf.eth0.arp_announce = 0
net.ipv4.conf.eth0.arp_ignore = 0
net.ipv4.conf.eth0.arp_accept = 0
net.ipv4.conf.eth0.disable_xfrm = 0
net.ipv4.conf.eth0.disable_policy = 0
net.ipv4.conf.eth0.force_igmp_version = 0
net.ipv4.conf.eth0.promote_secondaries = 0
net.ipv4.conf.wlan0.forwarding = 0
net.ipv4.conf.wlan0.mc_forwarding = 0
net.ipv4.conf.wlan0.accept_redirects = 1
net.ipv4.conf.wlan0.secure_redirects = 1
net.ipv4.conf.wlan0.shared_media = 1
net.ipv4.conf.wlan0.rp_filter = 0
net.ipv4.conf.wlan0.send_redirects = 1
net.ipv4.conf.wlan0.accept_source_route = 1
net.ipv4.conf.wlan0.proxy_arp = 0
net.ipv4.conf.wlan0.medium_id = 0
net.ipv4.conf.wlan0.bootp_relay = 0
net.ipv4.conf.wlan0.log_martians = 0
net.ipv4.conf.wlan0.tag = 0
net.ipv4.conf.wlan0.arp_filter = 0
net.ipv4.conf.wlan0.arp_announce = 0
net.ipv4.conf.wlan0.arp_ignore = 0
net.ipv4.conf.wlan0.arp_accept = 0
net.ipv4.conf.wlan0.disable_xfrm = 0
net.ipv4.conf.wlan0.disable_policy = 0
net.ipv4.conf.wlan0.force_igmp_version = 0
net.ipv4.conf.wlan0.promote_secondaries = 0
I wrote another easy socket program by myself, strace it and find that the program blocked in the "accept" system call. How can I solve this problem, or what can I do to find out more clues? Thanks very much.
Last edited by henryouly (2007-06-16 12:17:34)

Lucke most likely nailed it. FWIW, all SYN_SENT means is that you weren't sent an RST and the SYN attempt silently failed for whatever reason. You can create the exact same state by sshing to a host that either doesn't exist on your network or is down. Probably if you were sniffing traffic on your network, what you'd see is several ARPs coming from your machine, and no answers, or an ARP request, and ARP reply, and then a SYN packet with no reply. In any case, it's most likely wrappers blocking access to the port.
Last edited by Snarkout (2007-06-08 14:32:02)

Remote desktop connection blocked by cisco security agent

Hi,
I have a deployment of a Management Center for Cisco Security Agents 6.0.2 and i just noticed that the agent is blocking the remote desktop connection to the hosts, the agent installed on the server shows me the event but i'm not able to see it logged on the Management Center (i can see logged any other events), i'm not sure what rule should i enable in order to allow this connection.
Do you have any ideas???
Thanks in advance...

Hi,
Remote desktop connection uses the highest possible security level encryption method between the source and destination.
In Windows Vista or later versions of Windows, the remote desktop connection uses the SSL (TLS 1.0) Protocol and the encryption is Certificate-based.
TS Gateway can also make the connection more secure, enhance security, see detailed information in this link
http://technet.microsoft.com/en-us/library/cc731264(WS.10).aspx
Don't forget some known offical antii-virus software, they can also protect the connetion from network attack.
Yolanda Zhu
TechNet Community Support

Jdbc connection blocks when run from jar

The following code establishes a connection EXCEPT when run from within a jar file:
String jdbcDriverName = "oracle.jdbc.driver.OracleDriver";
String dbConnectionURL = "jdbc:oracle:thin:@192.168.2.7:1521:PRISM";
String userName = "mdo";
String password = "mdpass";
// Load the JDBC driver and create a connection to the database
Class.forName( jdbcDriverName );
OracleDataSource dataSource = new OracleDataSource();
dataSource.setURL( dbConnectionURL );
dataSource.setUser( userName );
dataSource.setPassword( password );
connection = dataSource.getConnection();
When run from a jar file, the application does not execute beyond the line:
connection = dataSource.getConnection();
No exceptions are thrown, it just appears that getConnection never returns.
Do I need to do anything different to execute this code from within a jar file?
Thanks in advance,
Phil
<><

When building the JAR file, I inadvertently included files from two Oracle JDBC driver versions (1.2 and 1.4). I was building a single jar file with all files in it.
I am guessing same named files existed in both driver JARs and caused "confussion" when combined into the single JAR.
Still, I would have expected an exception to be thrown or a null connection to be returned instead if the thread just blocking.
Thanks for all replies,
Phil
<><

SSL connections blocking worker threads on DS 5.2 patch 4

Hi,
Is it normal for an idle SSL connection to consume a worker thread within the directory server?
We have recently enabled SSL on a number of our directory servers (5.2 patch 4) and have run into problems with the server hanging. We have a number of application servers, each opening a pool of connections to the servers via JNDI. It seems that once 30 SSL connections have been established to a give LDAP server, the server will hang. By hang I mean the server is accepting TCP connections, but not responding to LDAP requests.
The server can deal with a lot more than 30 non-ssl connections. I'm guessing that SSL connections need to maintain state, which is what is tying up the worker threads.
Is this normal, and is it docuemented anywhere? Currently I'm looking at terminating the SSL connections on a load balancer in front of the LDAP servers, or perhaps on an LDAP proxy. Any other suggestions as to how this is typically dealt with?
thanks,
R

Thank you Gautam.
On further testing yesterday, we discovered that the problem is just as you have described. Our application servers are opening an initial pool of five connections, but typically only using one of those connections. The one connection the server uses to make an LDAP request behaves 'normally', not tying up a thread on the LDAP server. The other four sit there blocking a thread each, until eventually we hit the nsslapd-threadnumber.
Based on that discovery, we're having the application changed so that its initial LDAP connection pool size is one, which appears to address the problem. That way connections are only established and added to the pool as they are required, resulting in well behaved connections to the LDAP server.
Thanks for the quick reply... The Sunsolve note is helpful, as is the info about the nsslapd-ioblocktimeout parameter.
kind regards,
R

How do I connect 16 strain gauges in quarter bridge arrangement to a SCXI 1322 connecter block?

Specifically, do I connect 4 bridge completion resistors to each VEX- channel or do I need to wire them together somehow first?

I have attached a bitmap image that explains how to wire a quarter-bridge strain gauge to the SCXI-1122 (with 1322 terminal block.) The 1122 only provides half-bridge completion, so you have to wire an extra resistor into the circuit to complete the bridge.
You can find this image in the SCXI-1122 User Manual, which is available for download at:
http://search.ni.com/search/query.html?col=alldocs&qp=%2Bcontenttype%3Aproductmanual&lk=2&layout=ProductManual&qt=1122
Attachments:
1122_strain.bmp ‏920 KB

Tranport.connect() blocks or if timeout is set builds unstopable threads

Hi,
I'am really in trouble while trying to build a simple "send an email" functionality in my software.
I'am trying to connect to a SMTP server that is unreachable (assume there is a firewall blocking the packets on there way to the SMTP server of my choice). The first problem was, that Transport.connect() does never finish. So this Forum told me: "set mail.smtp.connectiontimeout" and everything gets fine. This is true, as I get an exception when the connect takes to long.
So everthing was fine to me, as long as the application was running. But as I stopped the application (its a server app) I saw one Thread for each connect that failed. And these Threads are no deamon threads so they prevent the VM from exiting. Even when they are deamon threads it is a bad habit, because I will get masses of threads over the time.
Thats why I'am really in trouble. Does anybody knows a solution, where i can recognize that a timeout occured during connect and no "everlasting" is started?
Here are some code snippets from my app:
smtpServerProps.setProperty("mail.smtp.connectiontimeout", "10000");
smtpServerProps.setProperty("mail.smtp.timeout", "10000");
Session session = Session.getDefaultInstance(smtpServerProps);
Transport trans = session.getTransport("smtp");
trans.connect();
mail.saveChanges();
trans.sendMessage(mail, mail.getAllRecipients());
trans.close();

JavaMail 1.4 implements connection timeouts without needing an
additional thread. Upgrade to JavaMail 1.4.

A single fast connection blocks almost all other network activities

Hi!
If I have a single fast up/download (or enough smaller/slower ones), it is able blocks almost all other network activities:
Torrent without up/down limit => everything else is "timing out" (or something. P.e. load a single page in firefox or ping my router - doing nothing).
Pacman is fetching a package from a fast server => the same.
Pages in firefox don't load if I just stop the fast traffic - it keeps doing nothing until I hit [reload].
Tested a few other network applications (java stuff, wget, curl, whatever pacman uses), it all looks the same.
This hasn't been like this up until a while ago (1-2 weeks?)... during that time, I changed nothing in the whole network except for
1) the arch updates (normal mirrors, no testing)
2) added a debian machine to the network (problem persists if I shut it down though)
Now I don't know where to start searching. Any hints?
Thanks!

As I understand things you are saying one fast connection is blocking out all other connections right?
If so we need some more information.
1. Your basic setup, like are you using a cable modem and what router. wireless?
2. The result of speed tests on your connection both upload and download (e.g. testmy.net)
3. What is the "one" fast connection and how much bandwidth is it taking (bittorrent?)
One thing to look for is that certain routers cannot handle many connections. A few of my old WRT54G routers with stock firmware could only handle 200 connections or so before crashing. So now I use dd-wrt on a WRT54GL.
Some more info on what might be happening:
1. The torrent client is using all the connections so the router cannot handle more connections.
2. The torrent client is taking all the upload bandwidth so the behaviour you describe occurs.
3. The torrent client is taking up all the download bandwidth.
[less likely]
4. Some complex ISP shaping and/or bandwidth limiting?
5. Malfunctioning network hardware locally (i.e. router, NIC, etc.)
6. Wireless router encountering interference thus limiting bandwidth severely?
Some Possible solutions (assuming the common stuff is the case):
1. Get a Better router/firmware.
2. Configure the torrent client to limit connections/upload/download.
3. Setup complex limiting on the local box using iptables.
4. Ties in with #1. Configure router to implement QoS and/or bandwidth limiting based on Application layer protocol/port/Ip address/mac etc. dfepending on situation.
Last edited by davidm (2010-02-07 19:40:38)

Access Connections Block 1 Specific SSID

We are rolling out two wireless networks (guest and domain) at our home office and want to block our domain joined laptops from connecting to the guest SSID to avoid confusion and keep people connected correctly. We are planning on using Access Connections to load profiles on the domain joined laptops but would like to block users from manually connecting to the guest SSID but we still need to allow users to make other manually wireless connections when they are not at the home office, travelling, at home, etc. We basically need to block the machine from connecting to one particular SSID. Can Access Connections do this for us? Thanks.

I don't think Access Connections has this feature, and even if it did, it would be possible to use Windows wireless config to connect to the banned SSID (e.g. by not using Access Connections).
So I think you need to do this at a Windows level, not at an Access Connections level.
See if this helps:
http://www.grouppolicy.biz/2010/03/how-to-use-group-policy-to-blackwhite-list-wireless-networks-in-v...

Adobe Connect: block Caller ID f(x) for a presentor

We have a guest presentor in a webinar on adobe connect today, that would like to have his personal phone number NOT be displayed.
He noticed that as he speaks, his phone icons flashes, which would give particpants his personal number - should they choose to write it down
Could he block this feature when he calls in? We want him to use a landline, not the computer, for clarity of audio.
If he dialed *67 before dialing our 1-800 adobe connect conference number, would that work?
Thanks

The Caller ID blocking trick may work, but I would just merge his dial in with his user id. Just drag and drop his phone number onto his name and you should get a prompt asking if you want to merge the users. Accept the merge and then when he talks, the phone icon next to his name will show he is speaking, but his phone number will not be visible.

Risky connection blocked

I have a pop-up from McAfee stating that a Risky Connection is Blocked from 72.21.214.145 -- and a whoami research comes up blank. But the IP is trying to access ApplePhotoStreamsDownloader.exe.
I've tried to attach the error message, but for somereason the Apple "insert image" feature won't activate the "insert image" button once I browse the picture files. (???) Just another problem.
Is there any way to find out if this is a valid Apple IP, or is it really an intruder.

There's another article on The Register that confirms the AppleInsider article. It looks like this is McAfee's problem to fix. I'm about to chat with McAfee to see what they know.
https://discussions.apple.com/message/19921812#19921812

Socket connections blocked... (sandbox violation)

I'm having trouble with Flash Player 10, regarding opening of sockets. I have a socket server responding on port 843, my custom port and a web server hosting a crossdomain.xml file.
The problem is that when I try to run with the debugger, it won't even attempt to make a connection.
The policy log shows this:
OK: Root-level SWF loaded: file:///xxxxx/Main.swf
OK: Searching for <allow-access-from> in policy files to authorize data loading from resource at xmlsocket://xxxxx.com:53280 by requestor from file:///xxxxx/Main.swf
Error: Failed to load policy file from xmlsocket://xxxxx.com:53280
Error: Request for resource at xmlsocket://xxxxx.com:53280 by requestor from file:///xxxxx/Main.swf has failed because the server cannot be reached.
The error is this:
Security error: [SecurityErrorEvent type="securityError" bubbles=false cancelable=false eventPhase=2 text="Error #2048: Security sandbox violation: file:///opt/Develop/glig/Flash/Widgets/chat/Main.swf cannot load data from xxxxx.com:53280."]
The sandbox mode is: localWithNetwork
The flash player version is: 10,0,22,87
I also used the line Security.loadPolicyFile("xmlsocket://xxxxx.com:53280"), but without success.
The remote server is reachable and responding to <policy-file-request/>, but does not register any connection attempts.
This all worked perfectly fine with version 9, where it would do a http request for crossdomain.xml. According to all the documentation I've read, my approach should work, but the player isn't even attempting to connect.
Does anyone have an idea?

You may have already solved this, but here's a response anyways.
Is your socket server serving up the policy file, or your web server (i.e. through HTTP)? If you are connecting through sockets, then the policy file must be served up through the socket server, it doesn't care about an HTTP policy.
Good luck!
Taylor
4Point Solutions Ltd.
http://blogs.4point.com/taylor.bastien/

Crashed connection blocks connections from other pools

Setup:
WLS 8.1.0.0 with 2-node cluster
Sybase: 12.0 and 12.5
jConnect 5.5 (EBF11248)
Java HotSpot(TM) Client VM Version 1.4.2-b28
I have two databases (DB1 & DB2) and two connection pools (P1 & P2), each pointing
to a corresponding DB. The pools are created at WLS startup.
Later on, say, DB1 is disconnected (crashed or lost network connectivity). We
found that all connections, whether to DB1 or DB2, becomes extremely slow (on
the order of 10+ mins) to obtain. The stack dumps (see following example) indicate
the crashed one (Thread-36) was stuck at a socket connection and all the others
(for DB2/P2) were waiting for the lock (0xf26b1958) during DriverManager.getConnection
(eg. Thread-153).
While searching at BEA, I noticed a fix CR125320 for 8.1 sp2 that seems to be
relevant but I'm not sure that's the exact fix. That fix specifically mentions
JTSConnection.doClose() but our dump doesn't show that.
Please help.
Thanks,
Bill
"Thread-36" daemon prio=5 tid=0x00da23a8 nid=0x8a runnable [5e97f000..5e9819a0]
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
- locked <0x82db64c0> (a java.net.PlainSocketImpl)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at java.net.Socket.connect(Socket.java:402)
at java.net.Socket.<init>(Socket.java:309)
at java.net.Socket.<init>(Socket.java:124)
at com.sybase.jdbc2.timedio.RawDbio.doConnect(RawDbio.java:88)
at com.sybase.jdbc2.timedio.InStreamMgr.<init>(InStreamMgr.java:94)
at com.sybase.jdbc2.tds.Tds.login(Tds.java:375)
at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:221)
at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:198)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:177)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:129)
at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:175)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:111)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1092)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1029)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:320)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:253)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:339)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:78)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:85)
at weblogic.jdbc.pool.Driver.connect(Driver.java:144)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
- locked <0xf26b1958> (a java.lang.Class)
at java.sql.DriverManager.getConnection(DriverManager.java:193)
- locked <0xf26b1958> (a java.lang.Class)
"Thread-153" daemon prio=5 tid=0x00c46280 nid=0xff waiting for monitor entry [57480000..574819a0]
at java.sql.DriverManager.getConnection(DriverManager.java:187)
- waiting to lock <0xf26b1958> (a java.lang.Class)

For the crashed DB, when one tries to get a connection, it gets stuck on a socket
connection. This means all subsequent requsts will all take a long time to just
come out and say it didn't work.
"Slava Imeshev" <[email protected]> wrote:
"Bill" <[email protected]> wrote in message news:[email protected]...
Thanks, Slava. You are right - getConnection is "public static synchronizedConnection
getConnection(String url)". However, how would one reduce the timeouton the socket
read on the crashed DB?I'd fix this problem first. In case of failure you serialize recreation
of the
connections. Depending on number of concurrent requests the process
of recovery can be noticeably lengthy. Fix it and re-do the test.
Regards,
Slava Imeshev
"Slava Imeshev" <[email protected]> wrote:
Don't use DriverManager to obtain connections. DriverManager contains
a lot class-level synchronization and is not recommended for use in
J2EE
environment. The best option is using DataSource obtained via a JNDI
lookup.
Or, use
Driver driver = ((Driver)Class.forName("my.driver")).newInstance();
Properties props = new Properties();
Connection conn = driver.connect(url, props);
Regards,
Slava Imeshev
"Bill" <[email protected]> wrote in message news:[email protected]...
Setup:
WLS 8.1.0.0 with 2-node cluster
Sybase: 12.0 and 12.5
jConnect 5.5 (EBF11248)
Java HotSpot(TM) Client VM Version 1.4.2-b28
I have two databases (DB1 & DB2) and two connection pools (P1 &
P2),
each pointing
to a corresponding DB. The pools are created at WLS startup.
Later on, say, DB1 is disconnected (crashed or lost network connectivity).We
found that all connections, whether to DB1 or DB2, becomes extremelyslow (on
the order of 10+ mins) to obtain. The stack dumps (see following
example)
indicate
the crashed one (Thread-36) was stuck at a socket connection and
all
the others
(for DB2/P2) were waiting for the lock (0xf26b1958) during DriverManager.getConnection
(eg. Thread-153).
While searching at BEA, I noticed a fix CR125320 for 8.1 sp2 that
seems
to be
relevant but I'm not sure that's the exact fix. That fix specificallymentions
JTSConnection.doClose() but our dump doesn't show that.
Please help.
Thanks,
Bill
"Thread-36" daemon prio=5 tid=0x00da23a8 nid=0x8a runnable [5e97f000..5e9819a0]
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
- locked <0x82db64c0> (a java.net.PlainSocketImpl)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at java.net.Socket.connect(Socket.java:402)
at java.net.Socket.<init>(Socket.java:309)
at java.net.Socket.<init>(Socket.java:124)
at com.sybase.jdbc2.timedio.RawDbio.doConnect(RawDbio.java:88)
at com.sybase.jdbc2.timedio.InStreamMgr.<init>(InStreamMgr.java:94)
at com.sybase.jdbc2.tds.Tds.login(Tds.java:375)
at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:221)
at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:198)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:177)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:129)
at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:175)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:111)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1092)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1029)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:320)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:253)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:339)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:78)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:85)
at weblogic.jdbc.pool.Driver.connect(Driver.java:144)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
- locked <0xf26b1958> (a java.lang.Class)
at java.sql.DriverManager.getConnection(DriverManager.java:193)
- locked <0xf26b1958> (a java.lang.Class)
"Thread-153" daemon prio=5 tid=0x00c46280 nid=0xff waiting for monitorentry [57480000..574819a0]
at java.sql.DriverManager.getConnection(DriverManager.java:187)
- waiting to lock <0xf26b1958> (a java.lang.Class)

WRT610N (v2) USB connection blocks internet

Hello,
I recently decided to start from scratch again with my home network, a major part of which was resetting and upgrading the firmware on my linksys wrt610n.
The problem is that now when I connect a usb external hard drive (LaCie 500gb) to the router the internet completely stops working. This means that I can't use the router setup page and the window pc (XP) can't view the router or the external storage through windows explorer.
Any sugegstions would be great.
Thanks,
Cat

So we could eliminate possible issues, I would like to know if this was working before or you just recently acquire the HDD and you are connecting it for the first time? Another thing is, when the hard drive is connected to the pc, is it working fine? If none of the above mentioned has issues, therefore, it is the router. I would suggest, do another reset on the device (manually press the reset button for a minute), then reconfigure it. If it is still failing, I guess, better get a new one.

Why do multiple laptop connections block each others' connectivity?

HP 6000 Plus, XP
I set up my personal laptop and my work laptop to print to my HP 8600 printer. 1) If I print from my personal laptop, it disconnects (albeit temporarily) the VPN connection on my work laptop. 2) If I connect my work laptop to my company VPN, then I can longer print from my personal laptop. Why do these two situations occur?

Hello ratfink80,
These applications may be running when you shut down or restart the system. You can use Activity Monitor to determine if they are, and also quit or force quit them as necessary before shutting down or restarting.
Activity Monitor: Quit a process
http://support.apple.com/kb/PH5147
Cheers,
Allen

Connection Block

Similar Messages

Maybe you are looking for