SecurityException after making client request

Hi,
I have a web application that makes an HTTPS client request to another server
using SSL/certificates. I'm using WebLogic classes for the client calls and modelled
my code off the WebLogic examples. After making the request (successfully), I
get a SecurityException when instantiating an InitialContext (see stack trace
below).
The exception indicates that the user is "null", but if I call Security.getCurrentUser()
just before and after the exception occurs, it reports my user correctly. If
I remove the HTTPS call, I no longer get the exception.
Is there a known problem, or is there something I could be doing wrong to cause
this?
Regards,
Paul
javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
Authentication for user null denied in realm weblogic
at weblogic.security.acl.Realm.authenticate(Realm.java:212)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:522)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:366)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:338)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:211)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:178)
at com.asa.pcss.business.BeanDataUtility.getResources(BeanDataUtility.java:265)

Hi Paul,
I've just encountered exactly the same problem. Did you find a solution?
Regards,
Fran
"Paul Canavese" <[email protected]> wrote:
>
Hi,
I have a web application that makes an HTTPS client request to another server
using SSL/certificates. I'm using WebLogic classes for the client calls
and modelled
my code off the WebLogic examples. After making the request (successfully),
I
get a SecurityException when instantiating an InitialContext (see stack
trace
below).
The exception indicates that the user is "null", but if I call Security.getCurrentUser()
just before and after the exception occurs, it reports my user correctly.
If
I remove the HTTPS call, I no longer get the exception.
Is there a known problem, or is there something I could be doing wrong to
cause
this?
Regards,
Paul
javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
Authentication for user null denied in realm weblogic
at weblogic.security.acl.Realm.authenticate(Realm.java:212)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:522)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:366)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:338)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:211)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:178)
at com.asa.pcss.business.BeanDataUtility.getResources(BeanDataUtility.java:265)

Similar Messages

Inconsistant transport requests after local client copy

Dear experts,
our IT department just made a local client copy with profile SAP_ALL, by which all the transport requests had been copied, too, including quite a lot of workbench and customizing orders in status changeable. I'm supposed to do some basic setup and cleanup in the new client, but I'm confronted with problems like objects being locked in orders/requests that cannot be changed in the new client, as they belong to the original source client.
How can I get rid of those inconsistencies? I'd preferred the new client without transports and without locked objects. Is it really necessary that I clean up this mess manually? Would it have been better to clean this up before the client copy? Or could we just do the client copy with another profile in order to avoid those problems?
Thanks for your appreciated help
Andreas

Hello,
Transports are NEVER part of a client copy.
In fact all the data of your transports is stored in tables that are client independent (E07* tables).
This means that you can view (not edit) always all transports from all clients in a specific system.
When you want to edit or release a transport the source client is important (in which client was the transport originally created).
This is stored in table E070C for all transports and can not be overruled.
So I recommend that you don't clean anything related to transports after a client copy because this will also impact the other clients !
Success.
Wim

Transport Request number missing after Remote client copy

Hi,
I have done a remote client copy with SAP_ALL .but after completing client copy i can find transport request numbers are not showing (SE10,SE09) for all the functional consultants. Plese help me to solve this issue, suggest me any solution
Thanks
Jyothish

> I have done a remote client copy with SAP_ALL .but after completing client copy i can find transport request numbers are not showing (SE10,SE09) for all the functional consultants. Plese help me to solve this issue, suggest me any solution
If you did client specific customzing in those they are of course not found.
Markus

WebLogic is not responding to client request under heavy load

Under heavy loading, our WLS 6.0 SP2 will be not be responding to client requests
after some time, say, 1 hour. From the administration console, the request throughput
is 0 while request waiting accumulates to over 1,000. Even the clients stop making
request to the server, the request waiting will not drop. It seems that WLS blocked
on some threads and unable to serve the requests (see attached thread dump for
details).
Our configuration is as follow:
OS: SunOS 5.7
Database: MS SQL Server 7.0 running on NT4 Enterprise Edition.
(JDBC Driver is the one bundled with WLS 6.0)
We know that using 'DriverManager.getConnection()' can cause deadlock in number
of cases but we have gone through all the code but all of our Database connections
are obtained through datasource. And the connection is closed properly in finally
block.
Moreover, the application is originally running on WLS 4.51 but no problem is
encountered.
Does any expert know what the problem and solution are?
Thanks!
[session.log]

It appears that some threads were possibly blocked at some jDriver calls
initially (ExecuteThread 0,10,15,23 of the default thread pool). WLS JTA
subsequently timed out and rolled back the transactions asynchronously. The
first rollback attempt was blocked at the jDriver level (ExecuteThread 18 of
the default thread pool). Each subsequent rollback retry blocks an
additional execute thread (due to a JTA bug that is fixed in WLS 6.1, but
not 6.0 SPs) - ExecuteThread 1-9,11-26 of the default thread pool.
Eventually, the server ran out of execute threads and became unresponsive.
It is unclear that whether the initial blocking of threads by the jDriver is
a jDriver issue or an application issue. Please report to BEA support at
[email protected] for further assistance.
Regards,
Priscilla
Gary Mok <[email protected]> wrote in message
news:[email protected]..
>
Under heavy loading, our WLS 6.0 SP2 will be not be responding to clientrequests
after some time, say, 1 hour. From the administration console, the requestthroughput
is 0 while request waiting accumulates to over 1,000. Even the clientsstop making
request to the server, the request waiting will not drop. It seems thatWLS blocked
on some threads and unable to serve the requests (see attached thread dumpfor
details).
Our configuration is as follow:
OS: SunOS 5.7
Database: MS SQL Server 7.0 running on NT4 Enterprise Edition.
(JDBC Driver is the one bundled with WLS 6.0)
We know that using 'DriverManager.getConnection()' can cause deadlock innumber
of cases but we have gone through all the code but all of our Databaseconnections
are obtained through datasource. And the connection is closed properly infinally
block.
Moreover, the application is originally running on WLS 4.51 but no problemis
encountered.
Does any expert know what the problem and solution are?
Thanks!

Using sharepoint designer 2013 - connected to sharepoint online - but getting " data source file cannot be saved" after making a new linked datasource

using sharepoint designer 2013 - connected to sharepoint online - but getting " data source file cannot be saved" after making a new linked datasource

Hi,
Based on your description, I have done a test and I can’t reproduce your issue.
I have used SharePoint Designer 2013 to open a SharePoint Online site and there are no issues.
I’d like to clarify whether you encounter any issues when accessing SharePoint Online sites. If there are no issues during the accessing procedure, SharePoint Online service should be working fine at your side. The issue may be caused by specific SharePoint
Designer client or network. I suggest you refer to the following steps to troubleshoot the issue.
1. Use SharePoint Designer to open another site and check whether it is successful.
2. When you are prompted to enter Office 365 account and password, try other users’ accounts and select the remembering the credential.
3. Perform the connection procedure under another environment and verify whether the issue is resolved.
If the issue persists, can you provide related screenshots for further troubleshooting?
Best Regards,
Lisa Chen
Lisa Chen
TechNet Community Support

Input credit on Service tax after making payment to vendors

Dear Friends,
Vendor invoice has been entered with Input service tax and payment has been made to the vendor. After making the payment, it is only clearing the vendor balance and not the input service tax G/L accounts entered on the invoice.
We tried to implement deferred tax functionality (RFUMSV50 program), but here most of the input tax codes are based on the combination of Service tax with VAT. Hence we couldnt proceed further as deferred tax functionality is not applicable for VAT portion and applicable only for Service Tax here as it is a service based industry. In short, the requirement is Input credit can be taken for Service Tax only after making payment to the vendor.
Could you please let me know is there any mechanism where we can identify whether vendor invoice has been paid or not from the Input Service Tax GL accounts (either in FBL3N or FAGLL03 tcode). Based on that if the document is cleared, then my client will only take all the cleared documents' input service tax amounts and will set off with the output service tax.
Regards,
Dwarak.

HI,
Kindly go through the SAP note no.921634 & do the configuration accordingly.
Regards
Anuj

How can I have my servlet accept 100 concurrent client requests?

 My servlet extends HttpServlet so it is multithreaded. Then I have written a java
 client which starts 100 concurrent threads that try to contact the servlet.
 There are always lots of threads which are refused by the Weblogic Server 6.0.
 They get a 'Connection refused' exception. Sometimes there are 50 refused connections,
 sometimes there are 0 refused connections (not very often), sometimes there are
 80 refused connections (usually).
 I have checked the 'Servlet' documentation and the 'J2EE Design Considerations
 for Weblogic Server' which recommends not to exceede the execute thread count
 number of 15. I have not changed that value, I do not even know if it still exists
 in Weblogic 6.0 as the document refers to the 5.0 version.
 Does anybody know how to solve this problem? How can I have the client requests
 waiting rather than being refused? Of course the main goal is to serve all the
 client requests, not to refuse.
 This is the code that the client thread uses to contact the servlet:
 URL url = new URL("http://localhost:7001/examplesWebApp/myServlet");
 URLConnection conn = url.openConnection();
 conn.setDoInput(true);
 conn.setDoOutput(true);
 DataOutputStream os = new DataOutputStream(conn.getOutputStream());
 os.writeBytes()
 os.writeBytes()
 Thanks for your time,
 David


 The key is
 KKEY_LOCALMACHINE\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters
 There you may need add a value "MaxUserPort" as REG_DWORD (5000 is default), also
 change "TcpTimedWaitDelay" to small number (30 is minimum). You may have trouble
 to find them. Just add them.
 You can also use Microsoft Web Application Stress Tool to test your Weblogic applications.
 As a free test tool, it is really powerful, although not so flexible.
 I guess you write your own test tool with java.net.URLConnection. I am not sure
 about the power of this class. In my case, I wrote my stress test tools with Java
 Socket. I can test application on Weblogic 6 with 1000 threads with my own tool
 and Microsoft tool, depending on memory and CPU of the machines I use. I run my
 tests on both Windows 2000 professional and Solaris.
 Check your CPU and memory usage with task manager.
 On the other hand, you should check log message on Weblogic 6. Try to turn on
 HTTP debug by add the following in your config.xml in tag <Server>.
 <ServerDebug DebugHttp="true" DebugURLResolution="true"
 JDBCConn="true" JDBCSQL="true" ListenThreadDebug="true" Name="myserver"/>
 "David Ruana" <[email protected]> wrote:
 >
 >Xiang, I really appreciate your help. I changed my Weblogic server configuration
 >from the console but I still experience the same problems.
 >
 >I start my 100 threads, and from about the 20th onward all them get the
 >'Connection
 >refused' exception in the URLConnection::getOutputStream() function,
 >always after
 >a successful URLConnection::openConnetion().
 >
 >My system is Windows 2000 Professional (Spanish version). I tried to
 >check the
 >open client socket descriptor limit but I was not able to find the TCPIP/MAXUSERPORT
 >in the registry. Do you know how is this entry called in Windows 2000?
 >
 >At this point I am not sure whether my problems are related to the Weblogic
 >server
 >or to the operative system. I will keep trying... I would appreciate
 >any other
 >suggestion.
 >
 >Thank you very much.
 >
 >
 >
 >"Xiang Rao" <[email protected]> wrote:
 >>
 >>It is better to use Weblogic 6 console to configure Weblogic server.
 >>In the console,
 >>there is tab Servers->myServer->Congiguration->Tuning, you can find
 >execute
 >>length
 >>and backlog.
 >>
 >>If you use Windows as test client, note Windows have a 5000 open client
 >>socket
 >>descriptors limit. You need change Windows Registry (TCPIP/MAXUSERPORT)
 >>to change
 >>this parameter.
 >>
 >>On the other hand, during test, you should monitor your test via Weblogic
 >>console
 >>(myServer->Monitoring->Performance), here you can see the change of
 >wait
 >>queue.
 >>If the queue keeps increaing, you are in trouble.
 >>
 >>Since you know how to use MBean, try to write customized (servlet, for
 >>example)
 >>to collect the following data: opened socket number, open socket number,
 >>opened
 >>session number and open session number. The two "open" numbers will
 >give
 >>you some
 >>clue. Also record your CPU and memory usage.
 >>
 >>BTW, what is the output you get from your test in terms of number of
 >>requests
 >>per second, response time and number of bytes downloaded/uplodaed per
 >>second?
 >>Are your test client and Weblogic running on the same machine?
 >>
 >>
 >>
 >>"David Ruana" <[email protected]> wrote:
 >>>
 >>>By the way, this is a piece of the config.xml file where you can see
 >>>my Server
 >>>configuration. It is the configuration which is installed in the examplesServer
 >>>in the free evaluation of Weblogic 6.0. I only modified the AcceptBacklog
 >>>value,
 >>>and added the ThreadPoolSize="15" line which was missing (I copied
 >from
 >>>the petstoreServer).
 >>>
 >>> <Server AcceptBacklog="1000" AdministrationPort="0" ClusterWeight="1"
 >>> ConsoleInputEnabled="false" DGCIdlePeriodsUntilTimeout="2"
 >>> DefaultProtocol="t3" DefaultSecureProtocol="t3s"
 >>> HttpdEnabled="true" JavaCompiler="C:\bea\jdk130/bin/javac"
 >>> ListenPort="7001" Name="examplesServer" NativeIOEnabled="true"
 >>> ThreadPoolSize="15"
 >>> SocketReaderTimeoutMaxMillis="10"
 >>> TransactionLogFilePrefix="config/examples/logs/"
 >>> TunnelingClientPingSecs="45" TunnelingClientTimeoutSecs="40"
 >>>XMLRegistry="examplesXMLRegistry">
 >>> <ServerDebug Name="examplesServer"/>
 >>> <WebServer DefaultWebApp="DefaultWebApp_examplesServer"
 >>> LogFileName="./config/examples/logs/access.log"
 >>> LoggingEnabled="true" Name="examplesServer"/>
 >>> <Log FileName="./config/examples/logs/weblogic.log" Name="examplesServer"/>
 >>> <KernelDebug Name="examplesServer"/>
 >>> <SSL Enabled="true" ListenPort="7002" Name="examplesServer"
 >>> PeerValidationEnforced="0"
 >>> ServerCertificateChainFileName="./config/examples/ca.pem"
 >>> ServerCertificateFileName="./config/examples/democert.pem"
 >>> ServerKeyFileName="./config/examples/demokey.pem" TrustedCAFileName="./config/examples/ca.pem"/>
 >>> </Server>
 >>>
 >>>
 >>>
 >>>
 >>>
 >>>"Xiang Rao" <[email protected]> wrote:
 >>>>
 >>>>You only need to change Weblogic HTTP configuration. Give the server
 >>>>a big socket
 >>>>Backlog number. Since you test with 100 threads, you can think 1000
 >>>to
 >>>>5000, i.e.,
 >>>>1000 to 5000 requests will be in queue before got served. Aslo, you
 >>>might
 >>>>need
 >>>>to change your OS TCP/IP settings (both test clients and servers),
 >>such
 >>>>as maximum
 >>>>number of sockets and timeout value(so closed sockets will release
 >>socket
 >>>>descriptors
 >>>>immediately).
 >>>>
 >>>>On the other hand, the number of executive threads can be much larger
 >>>>than 15
 >>>>(50-200 is a normal number), depending on the features of your application.
 >>>>You
 >>>>can try your stress test tools to find a reasonable number by analyzing
 >>>>the relationships
 >>>>among (throughtput, response time, number of executive threads, etc).
 >>>>
 >>>>
 >>>>"David Ruana" <[email protected]> wrote:
 >>>>>
 >>>>>My servlet extends HttpServlet so it is multithreaded. Then I have
 >>>written
 >>>>>a java
 >>>>>client which starts 100 concurrent threads that try to contact the
 >>>servlet.
 >>>>>
 >>>>>There are always lots of threads which are refused by the Weblogic
 >>>Server
 >>>>>6.0.
 >>>>>They get a 'Connection refused' exception. Sometimes there are 50
 >>refused
 >>>>>connections,
 >>>>>sometimes there are 0 refused connections (not very often), sometimes
 >>>>>there are
 >>>>>80 refused connections (usually).
 >>>>>
 >>>>>I have checked the 'Servlet' documentation and the 'J2EE Design Considerations
 >>>>>for Weblogic Server' which recommends not to exceede the execute
 >thread
 >>>>>count
 >>>>>number of 15. I have not changed that value, I do not even know if
 >>>it
 >>>>>still exists
 >>>>>in Weblogic 6.0 as the document refers to the 5.0 version.
 >>>>>
 >>>>>Does anybody know how to solve this problem? How can I have the client
 >>>>>requests
 >>>>>waiting rather than being refused? Of course the main goal is to
 >serve
 >>>>>all the
 >>>>>client requests, not to refuse.
 >>>>>
 >>>>>This is the code that the client thread uses to contact the servlet:
 >>>>>
 >>>>>URL url = new URL("http://localhost:7001/examplesWebApp/myServlet");
 >>>>>URLConnection conn = url.openConnection();
 >>>>>conn.setDoInput(true);
 >>>>>conn.setDoOutput(true);
 >>>>>
 >>>>>DataOutputStream os = new DataOutputStream(conn.getOutputStream());
 >>>>>os.writeBytes()
 >>>>>os.writeBytes()
 >>>>>...
 >>>>>
 >>>>>Thanks for your time,
 >>>>>David
 >>>>>
 >>>>
 >>>
 >>
 >

Workflow for PO-Event Linkage get unchecked after making Purchase Order

Hi,
I have a client reqiirement for setting Workflow for Purchase Order.
I have done all the settings for PO Workflow. I am getting the mail for the first time but from the second PO onwards I am not getting the mail.
When I checked the settings, the Event linkage in SWETYPV gets unchecked for BUS2012 Object Type automatically after making the first PO.
Again when I activate that, I am able to get mail for the first PO only. From the second onwards, no mail is triggered.
Could anyone suggest?
Thanks,
S.Raghavan
Hi,
I now have changed the "Behavior Upon Error Feedback" to "Mark Linkage as having Errors" in SWETYPV
After this change if I make a PO, the link doesn't get break but "Receiver Status" shows "Errors".
I could also see the overview of errors in Transaction code SWEQADM. It shows 3event with Errors and 1 linkage with errors.
I do not know in which event error is there and in which linkage error is there?
Can anyone help to see the events and linkage where error persists?
Edited by: S.Raghavan on Aug 30, 2011 6:22 PM
Hi all,
Any suggestion for the issue posted?

In SWDD select WS 20000075 in the first task assign agents(users, ie create u r own users),
without user IDs(as u r step 2).if u design "organization plan" then userID's r assigned (like manager,supervisor, clerk etc.,)
try it

Return the user to the original point in the template after making selectio

Hi,
Can u suggest one solution for this problem
Return the user to the original point in the template after making selections/returning back from the select views . While using the select list in middle of the page or some other point of the page, the page will be getting refreshed and it will be returned to the start of the page. My requirement is make it return to the same position after the refreshed page.
Thanks,
Ramky

Hi Vikas,
I have done the same setup as your sample application. I am using
 
Branch URL : 
f?p=&APP_ID.:&APP_PAGE_ID.:&APP_SESSION.::::::#&P1_ANCHOR.
 
Computation for P1_ANCHOR: 
case :REQUEST
WHEN 'P1_A_SCN' THEN 'P1_A_SCN'
ELSE NULL
end
 
Anchor Code in region header for item P1_A_SCN: 
< a name="P1_A_SCN">< /a >
 
When I use the select list it wont come back to the region where the select list P1_A_SCN is located. I checked for the value in P1_ANCHOR in the session state and it correctly shows as 'P1_A_SCN'. But the page URL after the submit does not show the anchor like 
......f?p=206:1:14418154115565883485::::::#P1_A_SCN it shows 
......f?p=206:1:14418154115565883485::::::
 
When I but the branch URL as 
f?p=&APP_ID.:&APP_PAGE_ID.:&APP_SESSION.::::::&P1_ANCHOR. without the '#' it shows the page URL as 
......f?p=206:1:14418154115565883485::::P1_A_SCN
 
Do you what is causing the anchor to not show up in the page URL and thereby the intra page branch to not work.
Thanks,
Swaroop

Controllers not re-directing client requests to ISE

Please find attached a simple BYOD/ISE document I uploaded to kick start my new Wireless setup. Its all configured on my ISE sever and Controller as per doc.
My setup:
3600 AP's
Internal 5508 Controller
DMZ 5508 Controller (acts as a DHCP server for wireless clients)
Controllers have established connectivity (mobility acnhors), as a client I can connect fine to my new SSID get a DHCP IP address back from DMZ WLC and at the moment can connect out to the Internet fine (using no WLAN Security as a test). So this part is working.
I have now followed the document configured ISE, enabled AAA on the Internal WLC only and used the AAA override setting on WLAN as in the attached document.
I connect to SSID expecting to be redirected to my ISE Guest Portal, nothing happens other than connecting to Internet WebPages.
My question is, if I have followed this document correctly why is the Internal WLC not redirecting client requests to ISE, is this because my mobility anchors need to be re-configured, perhaps the AAA/ISE config needs to be applied to my DMZ WLC not internal WLC?
I would prefer the Internal WLC to redirect the login to ISE, doesn't make sense to traverse through the DMZ Firewall onto DMZ WLC back into the Internal Network again to the ISE to authenticate.
Or am I missing something additionally to this document to make sure clients are directed to the ISE Guest portal login.

After you configure web authentication, if the feature does not work as       expected, complete these troubleshooting steps:
Check if the client gets an IP address. If not, users can uncheck             DHCP Required on the WLAN and give the wireless client a             static IP address. This assumes association with the access point. Refer to the             IP addressing issues section of Troubleshooting             Client Issues in the Cisco Unified Wireless Network for troubleshooting DHCP             related issues.
On WLC versions earlier than 3.2.150.10, you must manually enter             https://1.1.1.1/login.html in order to navigate to the web             authentication window.
The next step in the process is DNS resolution of the URL in the             web browser. When a WLAN client connects to a WLAN configured for web             authentication, the client obtains an IP address from the DHCP server. The user             opens a web browser and enters a website address. The client then performs the             DNS resolution to obtain the IP address of the website. Now, when the client             tries to reach the website, the WLC intercepts the HTTP Get session of the             client and redirects the user to the web authentication login page.
Therefore, ensure that the client is able to perform DNS resolution             for the redirection to work. On Windows, choose Start >             Run, enter CMD in order to open a command window, and             do a “nslookup www.cisco.com" and see if the IP address comes back.
On Macs/Linux: open a terminal window and do a “nslookup             www.cisco.com" and see if the IP address comes back.
If you believe the client is not getting DNS resolution, you can             either:
Enter either the IP address of the URL (for example,                 http://www.cisco.com is http://198.133.219.25)
Try to directly reach the controller's webauth page with                 https:///login.html. Typically this is                 http://1.1.1.1/login.html.
Does entering this URL bring up the web page? If yes, it is most             likely a DNS problem. It might also be a certificate problem. The controller,             by default, uses a self-signed certificate and most web browsers warn against             using them.
For web authentication using customized web page, ensure that the             HTML code for the customized web page is appropriate.
You can download a sample Web Authentication script from             Cisco Software             Downloads. For example, for the 4400 controllers, choose             Products > Wireless > Wireless LAN Controller > Standalone             Controllers > Cisco 4400 Series Wireless LAN Controllers > Cisco 4404             Wireless LAN Controller > Software on Chassis > Wireless Lan Controller             Web Authentication Bundle-1.0.1 and download the             webauth_bundle.zip file.
These parameters are added to the URL when the user's Internet             browser is redirected to the customized login page:
ap_mac—The MAC address of the access point to which the wireless                 user is associated.
switch_url—The URL of the controller to which the user                 credentials should be posted.
redirect—The URL to which the user is redirected after                 authentication is successful.
statusCode—The status code returned from the controller's web                 authentication server.
wlan—The WLAN SSID to which the wireless user is                 associated.
These are the available status codes:
Status Code 1: "You are already logged in. No further action is                 required on your part."
Status Code 2: "You are not configured to authenticate against                 web portal. No further action is required on your part."
Status Code 3: "The username specified cannot be used at this                 time. Perhaps the username is already logged into the                 system?"
Status Code 4: "You have been excluded."
Status Code 5: "The User Name and Password combination you have                 entered is invalid. Please try again."
All the files and pictures that need to appear on the Customized             web page should be bundled into a .tar file before uploading to the WLC. Ensure             that one of the files included in the tar bundle is login.html. You receive             this error message if you do not include the login.html             file:
Refer to the             Guidelines             for Customized Web Authentication section of             Wireless             LAN Controller Web Authentication Configuration Example for more             information on how to create a customized web authentication window.
Note: Files that are large and files that have long names will result                 in an extraction error. It is recommended that pictures are in .jpg                 format.
Internet Explorer 6.0 SP1 or later is the browser recommended for             the use of web authentication. Other browsers may or may not             work.
Ensure that the Scripting option is not blocked on             the client browser as the customized web page on the WLC is basically an HTML             script. On IE 6.0, this is disabled by default for security purposes.
Note: The Pop Up blocker needs to be disabled on the browser if you                 have configured any Pop Up messages for the user.
Note: If you browse to an https site, redirection does                 not work. Refer to Cisco bug ID                 CSCar04580 (registered customers only)          for more information.
If you have a host name configured for the             virtual interface of the WLC, make sure that the DNS             resolution is available for the host name of the virtual interface.
Note: Navigate to the Controller > Interfaces menu                 from the WLC GUI in order to assign a DNS hostname to the                 virtual interface.
Sometimes the firewall installed on the client computer blocks the             web authentication login page. Disable the firewall before you try to access             the login page. The firewall can be enabled again once the web authentication             is completed.
Topology/solution firewall can be placed between the client and             web-auth server, which depends on the network. As for each network             design/solution implemented, the end user should make sure these ports are             allowed on the network firewall.
Protocol Port
HTTP/HTTPS Traffic
TCP port 80/443
CAPWAP Data/Control Traffic
UDP port 5247/5246
LWAPP Data/Control Traffic (before rel 5.0)
UDP port 12222/12223
EOIP packets
IP protocol 97
Mobility
UDP port 16666 (non secured)                       UDP port 16667 (secured IPSEC tunnel)
For web authentication to occur, the client should first associate             to the appropriate WLAN on the WLC. Navigate to the Monitor >             Clients menu on the WLC GUI in order to see if the client is             associated to the WLC. Check if the client has a valid IP             address.
Disable the Proxy Settings on the client browser until web             authentication is completed.
The default web authentication method is PAP. Ensure that PAP             authentication is allowed on the RADIUS server for this to work. In order to             check the status of client authentication, check the debugs and log messages             from the RADIUS server. You can use the debug aaa             all command on the WLC to view the debugs from the RADIUS             server.
Update the hardware driver on the computer to the latest code from             manufacturer's website.
Verify settings in the supplicant (program on             laptop).
When you use the Windows Zero Config supplicant built into             Windows:
Verify user has latest patches installed.
Run debugs on supplicant.
On the client, turn on the EAPOL (WPA+WPA2) and RASTLS logs from a             command window, Start > Run > CMD:
netsh ras set tracing eapol enable
      netsh ras set tracing rastls enable
In order to disable the logs, run the same command but replace             enable with disable. For XP, all logs will be located in             C:\Windows\tracing.
If you still have no login web page, collect and analyze this             output from a single client:
debug client
debug dhcp message enable
debug aaa all enable
debug dot1x aaa enable
debug mobility handoff enable
If the issue is not resolved after you complete these steps,             collect these debugs and use the             TAC Service Request Tool (registered customers only)          in order to open a Service             Request.
debug pm ssh-appgw enable
debug pm ssh-tcp enable
debug pm rules enable
debug emweb server enable
debug pm ssh-engine enable packet

I have a problem with the apple service team after making a payment. Where do I take the issue up?, I have a problem with the apple service team after making a payment. Where do I take the issue up?

I have a problem with the apple service team after making a payment. Where do I take the issue up?, I have a problem with the apple service team after making a payment. Where do I take the issue up?

If you are dissatisfied with the Service you have received and wish to Contact Apple...
India
Start your support request online and we'll connect you to an expert.
(91) 1800 4250 744
www.apple.com/in/support/
From the above Link...
To Contact Apple World Wide for Support and Service
http://support.apple.com/kb/HE57

Howto prepare RMI objects before clients request

Hi, here is what I intend to do on the server side.
Server Roles:
- provide authentication.
- have a queue of data ready to deliver to clients requests. (to build this queue the server must get information from the DB, do some filtering and priority)
- Keep record of logged clients (this will affect the queue as well)
- on clients responses (do some processing and insert data to DB
my worries are how should I prepare this queue before clients start requesting. Here is my approach
Use some flag mechanism to prevent delivery until objects are ready.
Execute an application (queue controller) on same rmi server (or other) that actually prepares this queue objects, once prepared set flags ready for delivery.
The queue controller would need to act as a daemon or service and keep an eye on the queue, acting on it if necessary.
How does this sound?
any suggestions
Thanks

Don't export the server until the queue is ready. Don't extend UnicastRemoteObject: instead, call UnicastRemoteObject.exportObject(remote, port) after you have made the queue ready for service.

Arrowpoint Cookies, Reverse Proxy and Multiplexed Client Requests

Hi,
I have a reverse proxy which is performing SSL offload and making backend connections to two web servers. Between the reverse proxy and the two webservers, a CSS is in place to load balance between the web servers. There is a requirement for session stickiness on the web servers and since client IP details are lost through the reverse proxy I have used the arrowpoint-cookie method to load balance connections.
However, the reverse proxy seems to make only a handful of connections to the servers compared to the number incoming client connections and we have noticed that stickiness is broken. Now, I would assume this is correct if arrowpoint-cookie makes a load balancing based on the first HTTP get in a tcp stream and not on a per transaction basis AND our reverse proxy is multiplexing client requests. However, I can not convince myself of how the arrowpoint-cookie method actually works.
I wondered if anyone had any insight on this or had experienced similar issues with arrowpoint cookies?

Hi Gilles,
I have implemented this today, and we are still seeing issues with requests hitting the wrong server.
A bit more info, the reverse proxy is an AXG Web Aopplication Firewall. I have been looking at this and am considering disabling connection re-use on here.
However I am also wondering if this might be to do with the flow timeout multiplier I am using which is 5 (80 seconds). Perhaps this is too low?
Thanks, David.

Iteratively accept client requests

Hi,
My server has to accept client requests iteratively. Below are my codes. However, I find that a request is processed twice and after which error of file not file which is somewhere else of my codes is printed non stop. Not sure is it due to the loop. Can someone please advise?
the file not found codes is somelike. if file does not exist then print file not found error.
Socket connectionSocket;
while(true) {
          connectionSocket = null;
          try {
              connectionSocket = listenSocket.accept();
              // Read client request & initialize output to reponse to client.
              BufferedReader inFromClient = new BufferedReader
               (new InputStreamReader(connectionSocket.getInputStream()));
              outToClient = new DataOutputStream(connectionSocket.getOutputStream());
              String requestMessageLine = "";
              requestMessageLine = inFromClient.readLine();
              StringTokenizer tokenizedLine = new StringTokenizer(requestMessageLine);
              System.out.println("requestLine");
              request(tokenizedLine);
          } catch (Exception e) {
              System.err.println("Error: " + e);
          finally {
              if(connectionSocket != null)
               connectionSocket.close();
         }

Your code references external classes and methods that you did not include.
Also, it is VERY RUDE to 1) Not be an English speaker, and 2) Post code without asking first.

High CPU with error "%ADJ-3-RESOLVE_REQ:" in Catalyst 4500-X VSS after making L3 function (static routing)

We have a VSS based on 2x WS-C4500X-16., The VSS is used as Layer 2 Switch for diffrents Vlan in our DC.
After making the VSS as a Layer 3 gateway for our production VLAN and added 2 routes for routing purposes, we encountered a network down time with high CPU in the VSS and a huges log messages :
.May 14 12:11:25.947: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.7.22 Vlan100
.May 14 12:11:34.516: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.7.22 Vlan100
.May 14 12:11:40.072: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.1.1.254 Vlan100
.May 14 12:11:49.682: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
.May 14 12:11:55.079: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.1.1.254 Vlan100
.May 14 12:12:00.926: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.7.40 Vlan100
.May 14 12:12:06.701: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.8.32 Vlan100
.May 14 12:12:12.624: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.7.40 Vlan100
.May 14 12:12:21.627: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.7.40 Vlan100
.May 14 12:12:32.261: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.8.32 Vlan100
.May 14 12:12:41.801: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.2.105 Vlan100
.May 14 12:12:49.633: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
.May 14 12:12:54.831: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.1.1.254 Vlan100
.May 14 12:12:59.960: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.1.1.254 Vlan100
.May 14 12:13:08.745: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
.May 14 12:13:16.138: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
.May 14 12:13:22.393: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
.May 14 12:13:31.415: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.141 Vlan100
.May 14 12:13:38.944: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.2.215 Vlan100
.May 14 12:13:45.972: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
Bellow are the show version of our VSS,
Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500e-UNIVERSALK9-M), Version 03.04.00.SG RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Wed 05-Dec-12 04:38 by prod_rel_team
ROM: 15.0(1r)SG10
S_C4500X_01 uptime is 33 weeks, 1 day, 14 minutes
Uptime for this control processor is 33 weeks, 1 day, 16 minutes
System returned to ROM by power-on
System restarted at 11:59:10 UTC Tue Sep 24 2013
Running default software
Jawa Revision 2, Winter Revision 0x0.0x40
Last reload reason: power-on
License Information for 'WS-C4500X-16'
License Level: ipbase Type: Permanent
Next reboot license Level: ipbase
cisco WS-C4500X-16 (MPC8572) processor (revision 9) with 4194304K/20480K bytes of memory.
Processor board ID JAE173303CF
MPC8572 CPU at 1.5GHz, Cisco Catalyst 4500X
Last reset from PowerUp
4 Virtual Ethernet interfaces
32 Ten Gigabit Ethernet interfaces
511K bytes of non-volatile configuration memory.
Configuration register is 0x2101
Can you help please,

Hi,
thanks for your reply, but there is no hsrp configured, just an interface vlan. with 2 static routes and the problem was there for more than an hour before we decided to rollback.
Is there a BugId with this problem in Cisco DataBase.
here is a show ip route
S_C4500X_01# show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is 10.2.1.253 to network 0.0.0.0
S* 0.0.0.0/0 [1/0] via 10.2.1.253
10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 10.0.0.0/8 is directly connected, Vlan100
L 10.1.1.250/32 is directly connected, Vlan100
172.31.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.31.0.0/16 is directly connected, Vlan120
L 172.31.0.1/32 is directly connected, Vlan120
S 192.1.0.0/16 [1/0] via 10.1.1.254
and the show ip cef:
_C4500X_01# show ip cef
.May 14 12:13:57.859: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.158 Vlan100 f
Prefix Next Hop Interface
0.0.0.0/0 10.2.1.253 Vlan100
0.0.0.0/8 drop
0.0.0.0/32 receive
10.0.0.0/8 attached Vlan100
10.0.0.0/32 receive Vlan100
10.1.1.6/32 attached Vlan100
10.1.1.17/32 attached Vlan100
10.1.1.40/32 attached Vlan100
10.1.1.41/32 attached Vlan100
10.1.1.50/32 attached Vlan100
10.1.1.60/32 attached Vlan100
10.1.1.99/32 attached Vlan100
10.1.1.121/32 attached Vlan100
10.1.1.122/32 attached Vlan100
10.1.1.124/32 attached Vlan100
10.1.1.125/32 attached Vlan100
10.1.1.126/32 attached Vlan100
10.1.1.225/32 attached Vlan100
10.1.1.227/32 attached Vlan100
10.1.1.250/32 receive Vlan100
10.1.1.254/32 10.1.1.254 Vlan100
10.2.1.3/32 attached Vlan100
10.2.1.4/32 attached Vlan100
10.2.1.6/32 attached Vlan100
10.2.1.8/32 attached Vlan100
10.2.1.9/32 attached Vlan100
10.2.1.18/32 attached Vlan100
10.2.1.23/32 attached Vlan100
10.2.1.24/32 attached Vlan100
Prefix Next Hop Interface
10.2.1.26/32 attached Vlan100
10.2.1.28/32 attached Vlan100
10.2.1.29/32 attached Vlan100
10.2.1.31/32 attached Vlan100
10.2.1.103/32 attached Vlan100
10.2.1.108/32 attached Vlan100
10.2.1.109/32 attached Vlan100
10.2.1.124/32 attached Vlan100
10.2.1.129/32 attached Vlan100
10.2.1.137/32 attached Vlan100
10.2.1.139/32 attached Vlan100
10.2.1.143/32 attached Vlan100
10.2.1.144/32 attached Vlan100
10.2.1.159/32 attached Vlan100
10.2.1.167/32 attached Vlan100
10.2.1.174/32 attached Vlan100
10.2.1.175/32 attached Vlan100
10.2.1.176/32 attached Vlan100
10.2.1.181/32 attached Vlan100
10.2.4.38/32 attached Vlan100
10.2.4.39/32 attached Vlan100
10.2.4.43/32 attached Vlan100
10.2.4.47/32 attached Vlan100
10.2.4.51/32 attached Vlan100
10.2.4.63/32 attached Vlan100
10.2.4.65/32 attached Vlan100
10.2.4.69/32 attached Vlan100
10.2.4.71/32 attached Vlan100
10.2.4.73/32 attached Vlan100
10.2.4.102/32 attached Vlan100
10.2.4.106/32 attached Vlan100
10.2.4.107/32 attached Vlan100
10.2.4.113/32 attached Vlan100
10.2.4.116/32 attached Vlan100
10.2.4.119/32 attached Vlan100
10.2.4.120/32 attached Vlan100
10.2.4.122/32 attached Vlan100
10.2.4.141/32 attached Vlan100
10.2.4.148/32 attached Vlan100
10.2.6.7/32 attached Vlan100
Prefix Next Hop Interface
10.2.6.16/32 attached Vlan100
10.2.6.31/32 attached Vlan100
10.2.7.14/32 attached Vlan100
10.2.7.22/32 attached Vlan100
10.2.7.24/32 attached Vlan100
10.2.7.34/32 attached Vlan100
10.2.7.37/32 attached Vlan100
10.2.7.41/32 attached Vlan100
10.2.7.48/32 attached Vlan100
10.2.8.18/32 attached Vlan100
10.2.8.32/32 attached Vlan100
10.2.8.59/32 attached Vlan100
10.2.8.70/32 attached Vlan100
10.2.8.85/32 attached Vlan100
10.2.8.88/32 attached Vlan100
10.2.8.104/32 attached Vlan100
10.2.8.135/32 attached Vlan100
10.2.99.10/32 attached Vlan100
10.2.99.54/32 attached Vlan100
10.255.255.255/32 receive Vlan100
127.0.0.0/8 drop
172.31.0.0/16 attached Vlan120
172.31.0.0/32 receive Vlan120
172.31.0.1/32 receive Vlan120
172.31.0.5/32 attached Vlan120
172.31.0.29/32 attached Vlan120
172.31.255.255/32 receive Vlan120
192.1.0.0/16 10.1.1.254 Vlan100
224.0.0.0/4 drop
224.0.0.0/24 receive
Prefix Next Hop Interface
240.0.0.0/4 drop
and show ip arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.1.1.1 0 aa00.0400.c286 ARPA Vlan100
Internet 10.1.1.6 0 0050.5689.24b8 ARPA Vlan100
Internet 10.1.1.10 0 0050.5694.7d20 ARPA Vlan100
Internet 10.1.1.11 0 0050.5694.7d20 ARPA Vlan100
Internet 10.1.1.12 0 0050.5694.6ae7 ARPA Vlan100
Internet 10.1.1.13 0 0050.5694.6ae7 ARPA Vlan100
Internet 10.1.1.14 0 0050.568a.6321 ARPA Vlan100
Internet 10.1.1.16 0 0050.5694.0ab5 ARPA Vlan100
Internet 10.1.1.17 0 0050.5694.493d ARPA Vlan100
Internet 10.1.1.40 0 0013.19b0.9c40 ARPA Vlan100
Internet 10.1.1.41 0 1c17.d35a.c840 ARPA Vlan100
Internet 10.1.1.50 0 0002.b9b4.a5c0 ARPA Vlan100
Internet 10.1.1.60 0 000a.410f.e500 ARPA Vlan100
Internet 10.1.1.71 - 0008.e3ff.fc28 ARPA Vlan100
Internet 10.1.1.96 0 e02f.6d12.4df3 ARPA Vlan100
Internet 10.1.1.98 0 0050.5696.6d86 ARPA Vlan100
Internet 10.1.1.99 0 0050.5696.6d88 ARPA Vlan100
Internet 10.1.1.121 0 e02f.6d12.4dea ARPA Vlan100
Internet 10.1.1.122 0 e02f.6d12.4e61 ARPA Vlan100
Internet 10.1.1.123 0 e02f.6d5b.c10e ARPA Vlan100
Internet 10.1.1.124 0 e02f.6d17.c869 ARPA Vlan100
Internet 10.1.1.125 0 e02f.6d5b.c217 ARPA Vlan100
Internet 10.1.1.126 0 e02f.6d17.c8ec ARPA Vlan100
Internet 10.1.1.127 0 e02f.6d17.c876 ARPA Vlan100
Internet 10.1.1.128 0 e02f.6d5b.bef3 ARPA Vlan100
Internet 10.1.1.202 0 0000.85b7.9031 ARPA Vlan100
Internet 10.1.1.222 0 000f.f84d.2ca9 ARPA Vlan100
Internet 10.1.1.225 0 000f.f84d.3963 ARPA Vlan100
Internet 10.1.1.227 0 00c0.ee26.9367 ARPA Vlan100
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.1.1.250 - 0008.e3ff.fc28 ARPA Vlan100
Internet 10.1.1.254 0 0000.0c07.ac07 ARPA Vlan100
Internet 10.2.1.2 0 0011.4333.bcda ARPA Vlan100
Internet 10.2.1.3 0 0050.5689.5d38 ARPA Vlan100
Internet 10.2.1.4 0 0050.5689.0404 ARPA Vlan100
Internet 10.2.1.6 0 0050.5689.6d3b ARPA Vlan100
Internet 10.2.1.7 0 1cc1.def4.6940 ARPA Vlan100
Internet 10.2.1.8 0 0050.5689.330e ARPA Vlan100
Internet 10.2.1.9 0 0012.793a.3ccc ARPA Vlan100
Internet 10.2.1.10 0 0012.7990.e5d3 ARPA Vlan100
Internet 10.2.1.13 0 0050.568a.6dcf ARPA Vlan100
Internet 10.2.1.15 0 0050.568a.60ff ARPA Vlan100
Internet 10.2.1.18 0 0050.5689.091b ARPA Vlan100
Internet 10.2.1.20 0 0050.5689.451c ARPA Vlan100
Internet 10.2.1.21 0 0050.568a.0cf4 ARPA Vlan100
Internet 10.2.1.22 0 0050.5689.6c59 ARPA Vlan100
Internet 10.2.1.23 0 0050.5696.6d9e ARPA Vlan100
Internet 10.2.1.24 0 0050.5689.76c4 ARPA Vlan100
Internet 10.2.1.26 0 0050.5689.2f4e ARPA Vlan100
Internet 10.2.1.27 0 0050.5689.0632 ARPA Vlan100
Internet 10.2.1.28 0 0050.5689.1ce9 ARPA Vlan100
Internet 10.2.1.29 0 0050.5689.6aaa ARPA Vlan100
Internet 10.2.1.31 0 0050.5689.0d1a ARPA Vlan100
Internet 10.2.1.37 0 0050.5696.6d81 ARPA Vlan100
Internet 10.2.1.103 0 d4be.d9be.8eef ARPA Vlan100
Internet 10.2.1.106 0 14fe.b5e1.c595 ARPA Vlan100
Internet 10.2.1.107 0 0023.ae7d.a966 ARPA Vlan100
Internet 10.2.1.108 0 d4be.d9c8.6770 ARPA Vlan100
Internet 10.2.1.109 0 14fe.b5e9.c5b5 ARPA Vlan100
Internet 10.2.1.110 0 14fe.b5ea.5f9d ARPA Vlan100
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.2.1.111 0 001e.c959.d4f0 ARPA Vlan100
Internet 10.2.1.114 0 b8ac.6f48.4538 ARPA Vlan100
Internet 10.2.1.115 0 14fe.b5e1.ed89 ARPA Vlan100
Internet 10.2.1.116 0 7845.c409.1959 ARPA Vlan100
Thanks
Lotfi

SecurityException after making client request

Similar Messages

Maybe you are looking for