IOS 4.3 - Authenticated Proxy + Wireless issues

Okay, I can see a lot of similar titled posts, but none quite have the same issues as we are facing here, so I decided to create a post of my own.
What we have is an 802.1X (AD/RADIUS) wireless network configured (on the iDevices) as a "WPA2 Enterprise" network and using a self-signed certificate. Once configured we also specify an authenticated proxy for the connection. Now, we've supported iDevices here for quite some time without too many issues (aside from the other occassional issue with updated phones, etc). We have everything on our network from "iPhone OS 3.1.2" through iPads with "iOS 4.3" and have been very successful in supporting these devices in the past... until v4.3.
With the new update, we have devices that worked perfectly before (and have been correctly configured) now asking for a username and password when browsing in Safari. We have devices that, on entering the correct information, give us messages such as "Incorrect username or password" or "Unable to join the network <name>". The same devices worked perfectly with iOS 4.2.1 installed. We've tried;
a) Forgetting the networks and setting them up again.
b) Changing the user's password and setting things up again.
c) Resetting network connections and trying again.
d) Resetting the entire phone and trying again.
But to no avail. If you can get wireless configured without either of the above errors messages, it will simply fail to work with the proxy server and cause issues in Safari, etc.
This is emmensly frustrating. We've had to put out a notice to all users to NOT update to v4.3 until this is resolved... which is not cool.
Interestingly, we also had a 3G rock up to the helpdesk today. It had iOS 4.2.1 installed (the latest availaqble for that odel, apparently) and it was exhibiting the same sort of behaviour (and is the only non-4.3 device to do so).
Any thoughts. Do we just need to wait until iOS 4.3.1 to get this fixed (like last time)?

So, I updated a couple of iPads and a few more iPhones yesterday and today. Around 50% success rate - which is weird. Tried the hard-off, reset network, forget network type stuff again, and no joy. Here's an intersting thing though;
a) We can now tap on the SSID and it figures out that it's an enterprise network. Saves chosing the options after tapping the "Other" setting. This also appears to improve the success of accepting the certificate as well. Neat. This didn't used to work.
b) Although the setup looks good, and Exchange just works... we were STILL getting an authentication box in Safari and things were not working correctly. As a test we entered credentials (using email address format - which also appears more successful) and it didn't appear to fix anything, or so we thought. on entering the auth details in Safari, the page that requested it stayed 75% loaded and didn't looks to be working. On closing that window and trying others like "Apple", etc, it appears to work.
I have done this on all the devices that failed and so far so good. So, forget your current network, set up the new enterprise wireless by tapping on the SSID (don't configure using "Other"), enter credentials as email addresses, and authenticate in Safari when you are asked the first time. Reload the page and test.
While this shouldn't make any difference (and is similar to what we tested in v4.3.0), it appears to work for us at the moment.

Similar Messages

  • Exchange 2010 to 2013 Migration: Authentication/Proxy Settings Issue

    I'm in the final stages of preparing for our Exchange 2010 to 2013 migration. I'm noticing minor authentication issues on mobile devices (android & ios) and proxy setting issues with Outlook that require user intervention. In an effort to make the migration
    as smooth as possible for our internal users, I'd like to get these settings ironed out before starting the migration.
    Symptoms:
    Outlook - I'm aware that internal Outlook usage has changed its connection protocol from RCP/TCP to RCP/HTTP, but it appears that Outlook isn't updating its settings in the "Microsoft Exchange Proxy Settings" after a users mailbox has been migrated
    from 2010 to 2013. Currently, 2010 users with Outlook 2013 have the following settings configured in Outlook's Exchange Proxy Settings:
    URL to connect to my proxy server for Exchange: webmail.domain.com
    Connect using SSL only: Checked
    Only connect to proxy servers that have this principal name in their certificates: Unchecked
    On fast networks, connect using HTTP first, then connect using TCP/IP: Unchecked
    On slow networks, connect using HTTP first, then connect using TCP/IP: Checked
    After migrating a user's mailbox from 2010 to 2013, the above settings remain the same in Outlook and their client disconnects from Exchange and isn't able to reconnect. After manually enabling the checkbox for "On fast networks, connect using HTTP
    first, then connect using TCP/IP", Outlook clients are able to connect to Exchange via their newly migrated mailbox.
    Is there a way to automatically updating these 2 proxy settings in Outlook during the migration instead of having to manually change each user's configuration in Outlook?
    Android & iOS - Currently, users on Android & iOS with Exchange 2010 mailboxes have the following configuration:
    domain: blank
    username: their AD username
    server: webmail.domain.com
    After migrating a mobile users mailbox from 2010 to 2013, neither OS (Android or iOS) is able to connect due to an authentication failure. On iOS, if I manually change the domain from blank to my company's domain, authentication succeeds and their 2013 mailbox
    begins to update. On Android, the option to change the domain name from null is grayed out, requiring the user to delete the Exchange profile and re-add it with the domain name intact. Is there a way to configure Exchange 2013 to not require the domain name
    for mobile users in the same way that it's been working for us with Exchange 2010?
    Please let me know if you require cmdlet print outs of my virtual directories to help troubleshoot the issue.

    Hi,
    Generally, when the user mailbox is moved from Exchange 2010 to Exchange 2013, the Autodiscover service would detect the changes and update the new configuration automatically.
    Please make sure the autodiscover service in your new Exchange 2013 is configured correctly. We can create a new mailbox in Exchange 2013 and check whether the new Exchange 2013 user can setup account successfully in Outlook or not. If the new user works
    fine, it indicates the autodiscover service in Exchange 2013 should be proper for internal user.
    Please restart the following Exchange service to have a try:
    Microsoft Exchange RPC Client Access
    Microsoft Exchange Mailbox Replication
    Restart IIS service by running IISReset in a Command Prompt window.
    Then check whether the Outlook client can connect to Exchange 2013 or not.
    As for Android & iOS issue, I suggest we can ask a question in ActiveSync forum for more suggestion:
    https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
    Regards,
    Winnie Liang
    TechNet Community Support

  • IOS 5/iPad 2 proxy settings not being remembered

    I recently upgraded one of my iPad 2's to iOS 5, but I seem to be having an issue the Wi-Fi connection in work. The wireless network has a hidden SSID and it requires some Manual proxy settings being put into the wireless config.
    When I input the relevant information it seems to hold fine for a few seconds but when I go into Safari it prompts for an https:// proxy username and password, if I input the correct details it just prompts again and no matter how many times I input the correct information it still prompts for it over and over again, to the point that you just have to switch the wireless off to stop the message from flashing up.
    I have an iPad 2 on iOS 4.3.5 and the same setting work perfectly fine on this iPad 2 but will not work on iOS 5.
    I have even tried a Linksys Wireless Access Point plugged into the network with no hidden SSID etc and I still get the same thing on the iOS 5 iPad 2 it continually prompts for the proxy details, but the iOS 4.3.5 iPad2 works fine.
    Is this a known glitch or am I just being a total idiot  : (  ?

    There are no work-arounds, there are no fixes, and no... updating to iOS 5.0.1 will not help you. This is broken and Apple needs to fix it. No "consumerisation" will not win, and our Network admin will NOT remove proxy authentication from the network to make it work. That's what Apple want me to do, and it's not happening. Here's the deal:
    1. There is a difference between a HTTP proxy and a HTTPS proxy, of course, and Apple ONLY let you supply a configuration (using "Manual") for a HTTP connection. Not HTTPS. That's the problem.
    2. As such, any request to a secure site (which a LOT of apps use, including Apple's own in-built ones) will fail. As soon as the connection for HTTPS is required, you will get an authentication prompt. The iPhone/iPad CAN NOT use the credentials assigned to the HTTP Proxy for the HTTPS Proxy... they are different. On a Mac (running OSX), these are definately two separate items you need to configure in the network settings and store in the KeyChain. Aple either need to write the "Manual" Proxy setting as both a HTTP and HTTPS connection (using the same KeyChain entry), or allow a HTTPS Proxy to also be specified. I favour the first option for simplicity - though it is not "standard".
    3. In iOS4, Apple also supplied a "Manual" setting with a "HTTP Proxy" setting. The big difference in that case is that requests to HTTPS sites, which would require a HTTPS Proxy connection (which was not supported), were simply IGNORED or attempted to get the data using ANONYMOUS access... which in almost all enterprises with proxy servers is flat-out denied. In iOS4 your app would have a spinning wheel forever or would crash when trying to hit a HTTPS site for updates etc. In iOS4 more apps simply didn't work, but failed in a nice and quiet way. This has changed to "allowed" in iOS5, as it now is HTTPS aware and attempts to respond to Proxy auth challenges... but Apple have not provided a way to store a username and password for that connection, so you get an authentication box.
    After I installed iOS5, I had my iPad on my desk all day but didn't get a chance to use it. That night I had about forty (40) of those prompts to cancel before I could use the device. Very frustrating. Even if you enter the correct username and password the million times it asks for it, you STILL get prompts... all the time. There is no good answer. If you're lucky enough to fluke a configuration and set of apps that only require HTTP connections, then you'll have no issues. That, from my experience, would be exceedingly rare.
    There are three (3) possible answers here;
    a) Get the network administrator to turn off authenticated proxy for the entire site. Good luck with that one.
    b) Implement a solution using DHCP/TMG/Websense (or whatever your network and security products may be), or use a product like NetBox Blue. If you don't have a solution like NetBox, you'll need to set DHCP reservations for each device by MAC Address, then configure that IP Range to be "unauthenticated" in terms of the proxy server/firewall, and then specify the range an a set of categories for that new typ of conenction (if using web filtering). That will let you do MAC address authentication and bypass the authenticated proxy. This is what we've had to do - and it *****.
    c) Wait for Apple to fix the issue. Like I said earlier, they'll either need to repurpose the "HTTP Proxy" option as "HTTP(S) Proxy" and allow HTTPS challenge responses to proxies via the one KeyChain item... or supply a second "HTTPS Proxy" option we can specify under "Manual". It's a fault in their software. To be honest... I preferred it when HTTPS traffic was just blocked (as in iOS4).

  • Profiling Problem & Web Authentication Proxy

    Dear All,
    I am facing problem with profiling of workstation over wireless network as ISE is marking these workstations as 'Unknown'. Whereas if I connect same workstation using wired connection then it gets profiled in the right category.
    Profiling for wireless network was working fine initially but as soon as I pointed AAA towards ISE in the employee SSID then ISE started marking any new workstation as 'Unknown'. Before enabling AAA in the WLAN (SSID) the profiling was working fine using 'Radius NAC' setting in advanced tab of the same SSID. Becasue of the unknown category, workstation gets authorization rejection as per the authorization policy.
    I have another query reagrding enabling 'web authentication proxy' on Cisco WLC. I have guest wireless setup using dedicated anchor controller and ISE is providing the guest sponsor and guest portal services. So when a guest user comes in and if the user already has some proxy configured in the browser then url redirection for guest portal doesn't work and guest user must remove the proxy.
    So this requires someone to enagage with guest user but the client want this process to be automatic. I have gone through following document,
    http://www.cisco.com/en/US/products/ps10315/products_configuration_example09186a0080b8a909.shtml
    but I am not sure if this solution will also work if the guest portal service is through ISE instead of WLC itself ??
    Thanks & Regards,
    Mujeeb

    Not a problem the reason your profiling is failing for wireless users is that the profiling information for dhcp isnt hitting the ise nodes. For the wired devices are you using the dhcp probe to profile the users? If so, then your issue is with the dhcp proxy setting on the controller. Even through you have the ip helper statement on the svi, essentially your controller is proxying the dhcp broadcasts from the client straight to the dhcp server, so even you enable the ip helper statements on the svi for the ISE nodes it will not work.
    You are correct for the guests, typically if a guest has enabled proxy settings before they should know that they should probably disable this setting when the connect to a new network.
    Also I can not remember but arent the proxy settings configured under the network settings tab? Meaning the only time you would experience this issue is if the ssid you are broadcasting is the same as the ssid they have connected to previously?
    Thanks,
    Tarik Admani
    *Please rate helpful posts*

  • Authentication proxy with Apps !!!!

    How can the iPhone doesn't support authentication proxy access for 3rd party apps ??? does anyone know how to get over that ?

    @luvlabs - As much as one wouldn't think that the iPhone is the problem (or in my case, the iPad), I actually think it is.
    It appears that iOS does not have support for system-wide proxy settings. That is why I experience certain applications that ask for proxy settings, which have been coded into the application, and some applications just fail completely to access the internet under proxy authenticated networks, because developers have not included a system to ask for proxy settings for the respective application.
    I have a thread over in the iPad forums, which I hope will grab some answers. Feel free to keep an eye on it should someone provide an official answer to this issue:
    http://discussions.apple.com/thread.jspa?threadID=2807623&tstart=0
    MrP.

  • Proxy Autoconfiguration File, Authenticated Proxy and iTunes iPad/iPod updates

    Hi All,
    Please can someone advise if there is anything that can be done to get iPad/ Ipod updates working using iTunes and an authenticating proxy server?
    Scenario is as follows:
    1. Proxy settings in IE is configured using a proxy autoconfiguration file (PAC file).
    2. The URLS *.apple.com is allowed to bypass authentication on the Proxy server.
    3. Itunes is used to update the devices from a PC running windows as OS.
    When Itunes is opened, the connection to the Itunes store works 100%. The iOS downloads using iTunes is also successfull.
    Issue:
    As soon as the downloaded iOS is being extracted and communicated to the devices, iTunes fails with an error code of 3004..
    It seems like the PC is trying to make direct connections out instead of using the proxy settings in the PAC file.
    Any advice / ideas to get this working?
    Regards

    HI,
    From the Safari Menu Bar, click Safari / Empty Cache. When you are done with that...
    From the Safari Menu Bar, click Safari / Reset Safari. Select the top 5 buttons and click Reset.
    If you have Safari 3rd party plugins, they may not be compatible with 10.6. Go here for trouble shooting.
    If you use GlimmerBlocker by chance, that could be the culprit. Check out this thread.
    http://discussions.apple.com/thread.jspa?messageID=10589731
    http://support.apple.com/kb/TS1594
    Same with any Input Managers. Move any files in the /Library/InputManagers folder to the Trash
    If you are running Safari in 64 bit mode, try running in 32-bit mode instead. Right or control click the Safari icon in the Applications folder, then click: Get Info In the Get Info window click the black disclosure triangle next to General so it faces down. Select 32 bit mode. Also, (in that same window) make sure Safari is NOT running in Rosetta.
    Go to ~/Library/Cookies and move the Cookies.plist file to the Trash.
    Try Open DNS - Free / Basic
    If Safari still can't open web pages, go to the Menu Bar, click Safari/Preferences. Make note of all the preferences under each tab. Quit Safari. Now go to ~/Library/Preferences and move this file com.apple.safari.plist to the Desktop. Relaunch Safari. If Safari loads web pages then that .plist file needs to be moved to the Trash.
    Carolyn

  • Ipad Mini doesn't load authentication proxy login

    Hi Guys,
    Im new using ipad mini. I am working in a private firm and the internet use system here is to login in the authentication proxy login page.
    I already have my proxy login account and I can login successfuly from my laptop. But when I try to use my Ipad Mini to access the net, Safari loads, and I can see the login page is loading but is like skipping the page and finally says "Safari cannot open the page becasue the network connection was lost".
    Thank you in advance.

    Do you happen to have Private Browsing Mode enabled in Safari on the iPad mini?  If so, you might try turning that off, then try to log in to the proxy again.
    Other things to try:
    What is Settings > Safari > Block Cookies set to?  It defaults to "From third-parties and advertisers", but try setting it to "Never" to see if that makes a difference when logging in.  (Do not leave it set at "Always" or that will make most web sites stop working that require cookies to function.)
    Does the authentication proxy use a pop-up window on your laptop's web browser?  If so, and if Settings > Safari > Block Pop-ups is ON, then you may need to turn that setting OFF to allow Safari to log in to the proxy.
    If you enable Private Browsing Mode on Safari on your laptop (I'm assuming you have a Mac), can you still log in successfully to the proxy?
    Does Google Chrome on the iPad mini let you log in to the proxy successfully?  (Chrome uses a different network stack on iOS.)

  • WLAN Authenticated Proxy, Nokia 5630

    Hello,
    I am using Nokia 5630 which has wireless feature.
    I have defined a wireless access point. In advanced settings of this wap, we can define a proxyort which let us use internet on on an access point which is behind a proxy server.
    BUT , we can not define a proxy username and password at all. In many places especially in university, accessing to internet needs a proxy username and password.In other words, there is an authenticated proxy instead of open proxy server.
    Please add this feature to advanced settings so that we would be able to define a proxy username and password in it.
    Best Regards

    I would suggest to backup all your important data like contacts, messages etc and goto Nokia Care for software reinstall or update.
    Hope this helps you.
    -------------------If this post helped you, click on accept as solution.------------------
    -----------------------------Appreciate by clicking on white star.----------------------------

  • IPad 2 WIFI (ios 4.3) Safari+proxy problem

    I have a problem with my new iPad 2 WIFI (4.3). With my iPhone 4 (4.1) I have no problem to connect to my authenticating proxy (squid) in my college. With my iPad, it's impossible... Safary is very slow and can't connect to websites. The settings are the same on both devices.
    What's wrong ?
    It seems that 4.3.1 is not a solution (??) can you confirm please ?
    Thanks.

    Safari on my iPad2 is super slow. I use the iPhone 3GS right next to it, and the iPhone just zips. Both show two bars of signal strength. Both are running iOS 4.3.1. The iPad2 is a Verizon 3G with 64 gb.
    I have noticed the problem in other apps too. In iTunes when I try to preview a song, the wheel on the song spins, but the wheel next to the wifi symbol showing the bars does not come on. I've noticed the same behavior in the Zite app as well.
    Also, the bars showing wifi signal strength will sometimes show up as two bars in the wifi setup screen, but none at all in the upper left hand corner.

  • Telnet Authentication Proxy

    Hi,
    For telnet ip authentication proxy, is it true that the router only sends username and password to Radius servers? Not the ip source address of the initiated host. So how does source ip of initiated host get added to the downloaded acl from the Radius server? The router adds it?
    Thanks.

    The Cisco IOS Firewall Authentication Proxy for FTP and/or Telnet Sessions feature in specific versions of Cisco IOS software is vulnerable to a remotely-exploitable buffer overflow condition.
    Devices that do not support, or are not configured for Firewall Authentication Proxy for FTP and/or Telnet Services are not affected.
    Devices configured with only Authentication Proxy for HTTP and/or HTTPS are not affected.
    http://www.cisco.com/en/US/products/products_security_advisory09186a00805117cb.shtml

  • Custmizing Authentication Proxy

    We want to use auth-proxy on a Cisco 836 with IOS 12T3 in order to provide WLAN access as if in an airport lounge or a hotel. The login page sent to the browser is to be customized with regard to look and feel. I've been able to do that with "ip auth-proxy banner file flash://login.html" and "ip adminission auth-proxy banner file flash://login.html", but the actual FORM is created on the fly by the router with a hidden time form element. Can you give us details on how the HTML form can be customized with the regard to the individual fields on the form?

    I have read that guide before, but it says it that auth proxy works with vpn and that
    If a VPN client initiates an HTTP connection, the authentication proxy first checks for prior client authentication. If the client is authenticated, authorized traffic is permitted. If the client is not authenticated, the HTTP request triggers the authentication proxy, and the user is prompted for a username and password.
    If the user authentication is successful, the authentication proxy retrieves the user profile from the AAA server. The source address in the user profile entries is replaced with the IP address of the authenticated VPN client from the decrypted packet.
    The only way I could make an impact with auth proxy on the vpn behaviour was when I configured a split-tunnel rule for the vpnclient which points only sends traffic to a non-existent internal network via the vpntunnel. Only then would auth-proxy insert additional rules that allow access to more destinations.
    As VPN without split-tunnel already allows access to all destinations I don't see how
    auth-proxy can make a difference
    Doro

  • New MacBook Pro 13 i5 Wireless Issues.

    I got the new MacBook Pro i5 2.3 the day it came out. So maybe a week and half ago.
    I`m having intermittent wireless issues. I have done some testing and even replaced my older AirPort Base Station with the new Dual-Band one, but still seeing a drops from the network. I have a ping going to my router and to the ABSE. I tried changing the channel and using 5GHZ or 2.4GHZ. I also have a AirPort express and seen similar results. I tried reseting the PRAM, repairing permission, I did not reinstall the OS but I dont see how this would help. I think there is a hardware issue with the wireless card/antenna.
    I did upgrade RAM and HDD was changed to SSD (intel G2 SSD). There are no other issues, machine is fast, no lock ups. Other devices on the network do not seem to drop any connections (ATV, ATV2, iPhone4, iPad etc..)
    The network drop outs are short but are noticeable and if a ping is going I can see the drops
    *-- 192.168.1.1 ping statistics ---*
    *1527 packets transmitted, 1505 packets received, 1.4% packet loss*
    *round-trip min/avg/max/stddev = 0.779/12.203/396.084/42.274 ms*
    Any help is appreciated as I`m really frustrated but this issue.

    Here are some of the pings.
    +*64 bytes from 192.168.1.3: icmp_seq=2190 ttl=255 time=1.138 ms*+
    +*Request timeout for icmp_seq 2191*+
    +*Request timeout for icmp_seq 2192*+
    +*64 bytes from 192.168.1.3: icmp_seq=2193 ttl=255 time=1.701 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2194 ttl=255 time=1.653 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2195 ttl=255 time=1.723 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2196 ttl=255 time=1.470 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2197 ttl=255 time=1.435 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2198 ttl=255 time=1.217 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2199 ttl=255 time=1.115 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2200 ttl=255 time=1.433 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2201 ttl=255 time=1.002 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2202 ttl=255 time=1.057 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2203 ttl=255 time=1.222 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2204 ttl=255 time=0.769 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2205 ttl=255 time=0.821 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2206 ttl=255 time=0.723 ms*+
    +*Request timeout for icmp_seq 2207*+
    +*64 bytes from 192.168.1.3: icmp_seq=2208 ttl=255 time=54.892 ms*+
    +*Request timeout for icmp_seq 2209*+
    +*Request timeout for icmp_seq 2210*+
    +*64 bytes from 192.168.1.3: icmp_seq=2211 ttl=255 time=1.313 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2212 ttl=255 time=0.936 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2213 ttl=255 time=1.839 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2214 ttl=255 time=0.879 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2215 ttl=255 time=63.446 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2216 ttl=255 time=24.384 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2217 ttl=255 time=105.923 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2218 ttl=255 time=41.322 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2219 ttl=255 time=1.853 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2220 ttl=255 time=0.811 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2221 ttl=255 time=0.721 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2222 ttl=255 time=0.791 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2223 ttl=255 time=3.816 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2224 ttl=255 time=1.052 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2225 ttl=255 time=0.688 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2226 ttl=255 time=89.272 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2227 ttl=255 time=49.459 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2228 ttl=255 time=15.891 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2229 ttl=255 time=0.745 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2230 ttl=255 time=0.724 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2231 ttl=255 time=0.680 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2232 ttl=255 time=1.950 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2233 ttl=255 time=0.600 ms*+
    +*Request timeout for icmp_seq 2234*+
    +*64 bytes from 192.168.1.3: icmp_seq=2235 ttl=255 time=0.725 ms*+

  • How to use Axis to access a web service through Authentication  proxy

    Using axis access internat web service is success,but access a web service through Authentication proxy is failure.But other java classes connect through a proxy to the internet which works very well:
    please help me ,thank you!!!
    import org.apache.axis.client.Call;
    import org.apache.axis.client.Service;
    import javax.xml.namespace.QName;
    //this is my access webservice faliure   codes
    public class TestClient
       public static void main(String [] args) {
           try {
                System.getProperties().setProperty("http.proxySet", "true");
                System.getProperties().setProperty("http.proxyHost","proxy.com");
                System.getProperties().setProperty("http.proxyPort", "8080");
                System.getProperties().setProperty("http.proxyUser", "username");
                System.getProperties().setProperty("http.proxyPassword","password");
               String endpoint =
                        "http://nagoya.apache.org:5049/axis/services/echo";
               Service  service = new Service();
               Call     call    = (Call) service.createCall();
               call.setTargetEndpointAddress( new java.net.URL(endpoint) );
               call.setOperationName(new QName("http://soapinterop.org/", "echoString") );
               String ret = (String) call.invoke( new Object[] { "Hello!" } );
               System.out.println("Sent 'Hello!', got '" + ret + "'");
           } catch (Exception e) {
               System.err.println(e.toString());
       }I get an "(407)Proxy authorization required" error?

    I am also looking for a solution. Does any one know how to do through code instead of jvm settings?
    Thanks in advance!

  • If you have a Blue Screen / Error due to Wireless issues (B110a), fix in here.

    For the original thread created by somebody else, please see here:
    http://h30434.www3.hp.com/t5/Printer-All-in-One-In​stall-and/B110a-network-connection-problem/m-p/319​...
    Here's a youtube video of what happened to me: http://www.youtube.com/watch?v=adE1kq36ld4
    I'm reposting it here so it can hopefully help some of you guys if anybody else stumbles across this. In short, my printer was fresh out of the box and I attempted to connect it to the wireless network. It would throw a blue screen on the LCD with an error of B8126AD6.
    I narrowed it down to an issue with DHCP. For some reason the printer connects to the wireless access point but as soon as it tries to get an IP address from the DHCP server it crashes with that blue screen and the error code in the first post above. This look like a massive bug in the printers firmware! For reference my router is a Billion 7401VGPR3 which is acting as my default gateway and DHCP server. I have a Linksys WRT54G as my Access Point for the house. 
    To solve it, I turned DHCP off on my router and then tried connecting the printer to the wireless network. This time it connects fine but you still can't talk to it because it doesn't have a proper IP address. If it still doesn't connect properly, try turning WPA/WPA2/WEP off on your Access Point. Leave it completely open for a moment until you can reach the web interface (as below). 
    To fix the IP issue, I then went into the Settings menu on the printer and printed the "HP Network Configuration Page". Note that under the Wireless menu option there are a couple of different "Print Network Test Page" options. I believe it's the 2nd one that I selected. You'll know you have the right one when it prints out the page with the following info:
    IPv4 IP Address
    Subnet Mask
    Hostname
    Default Gateway
    Primary DNS
    etc, etc.
    Take note of the IP Address from the printout above and the Subnet Mask. My IP was 169.254.73.5 and subnet mask 255.255.0.0. Now I manually configured my computers IP address to be similar (within the same subnet): 169.254.73.10 with the same subnet mask.
    Now you can load up the web interface of the printer using http://169.254.73.5 in my case. (You should also be able to ping the printer at this point too). In here you have a Network tab where you can now manually set the IP Address of the printer. Set the address you want it to be in your network (in my case 192.168.0.3 with a subnet mask of 255.255.255.0 and default gateway 192.168.0.1 and dns server 192.168.0.1).
    Once I clicked OK I changed my PC's IP back to normal, and I can now reach the printer on its IP address set above. YAY!
    The great thing is, in the web interface you get a million more options to play with. You can manually set the IP address, gateway, DNS, wireless settings such as WPA1/WPA2 AES/TKIP Encryption, WPA Passkey, etc. So if you had to set the Access Point to completely Open, setup the encryption again and put the passkey in here. When I did this I had to go back into the Settings menu on the printer LCD and select "Disable Wireless" then "Enable Wireless" to force it to re-join the network.
    Finally I went into the Settings menu again and Updated the software on the printer. I don't know if the new software fixes the bug or not - I haven't tested it (can't be bothered!).
    Hopefully this will help some of you guys out there too!
    EDIT: I've just stumbled across another couple of posts with similar results to mine:
    - http://h30434.www3.hp.com/t5/Printer-networking-an​d-wireless/How-to-install-Photosmart-B109n-z-on-a-​...
    - http://forums.techguy.org/networking/627989-hp-698​0-printer-wireless-problem.html

    Many thanks to gardz for an exhaustive overview on this critical problem with the B110a printer!
    I am happy to report that I have managed to set the printer to a static IP and am now able to connect to it wirelessly from my home computers, and also able to use the web apps and ePrint features on the printer. The printer shows the IP address and I am able to use the EWS (Embedded Web Server) to connect to its IP address from my PC's internet browser. The Wireless Network Test Report also showed no problems. I have also completed the Product Update on the printer, and there are no more pending updates now.
    However, the core wireless problem is still not satisfactorily resolved.
    I get the BSOD and blinking-lights error ("Please turn off printer and then on"), only if I start the printer when Wireless is enabled on the printer. If wireless is disabled prior to printer boot, there is no error. 
    The workaround I have adopted for now, is to always switch off the printer's wireless, before switching off the printer, and enabling the wireless setting only when I need to print/scan.
    Is this happening with anyone else? Why would the printer crash if it boots with wireless enabled? If it is already set to a static IP, why would it still conflict with the DHCP on the router?
    My router is perfectly working, it is in the same room as the printer, so the signal strength is good. The printer itself is quite stable except for this crash-after-boot-if-wireless-was-enabled issue on the printer.
    I made the mistake of connecting the USB cable to my primary computer before installing the printer drivers, so even the USB option is not working (Windows recognizes the printer as an unknown USB device). If anyone can point me to the printer drivers (inf files), I would be grateful. The CD does not have the driver files in a convenient location. It seems to be embedded within the setup package somewhere.
    Gardz and PrintDoc, I hope you can help us out on this one. I know many B110a users are struggling with the wireless issues, so HP needs to release a firmware fix and driver update soon. Wireless ought to work out-of-the-box, as this product is aimed at the SOHO users.

  • Error authenticating proxy while running agent job

    I am trying to schedule a SSIS2014 package via SQL Server Agent job. Both SSIS and SSMS are running on my local machine in the same domain. I am running SSMS with the same user
    Domain\Admin which is the creator of the SSIS package. SSMS 32-Bit and SSIS 32-Bit are running on Windows 7 64-Bit machine. I can run the package within SSIS without problems.
    When I use a proxy account to run the job step, the following message occurs:
    Unable to start execution of step 1 (reason: Error authenticating proxy `Domain\Admin`, system error: Logon failure: unknown user name or bad password.). The step failed.
    The proxy account uses the credentials identity Domain\Admin. Since the password fields for credential properties in SSMS cannot be left blank, I typed any password although my corresponding windows account has no password. So as mentioned above
    it's the same user account that created the SSIS package since Domain\Admin is stated in the CreatorName property of the SSIS package.
    With this proxy, I tried to run SSIS jobs using the package ProtectionLevel's
    EncryptSensitiveWithUserKey and EncryptSensitiveWithPassword. Running the package manually within SSDT without problems, but from SSMS agent job the same error message appears. I tried the package sources "File System" and, after
    importing the package to MSDB, "SQL Server" and "SSIS Package Store". But exactly the same error message appears with each method.
    Task manager shows that SSMS is running in administrator mode. Using Windows Component Services I added DCOM permissions for
    Domain\Admin to start and activate "Microsoft SQL Server Integration Services 12.0" from local. But the same error message appears. So in my opinion it's a problem with SSMS user account permissions (???) but unfortunately I don't know
    what exactly to do here. I tried the following:
    In the system database MSDB (full path: Databases / System Databases / MSDB / Security / Logins) I assigned all available role memberships (Including db_ssisoperator, db_ssisltduser, db_ssisadmin) to
    Domain\Admin.
    In server security (full path: Security / Logins) I assigned all available server roles. In the tab User Mapping, I assigned the MSDB database.
    Still the same error message appears when I try to run the job. Does anybody have some ideas what I can try?

    If you use the Agent then set the package protection to "Rely on server".
    Then Domain/Admin is probably not an actual proxy but the account the Agent is running under, in this or even any case follow http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/ to create the
    proper proxy for the packages.
    Arthur My Blog

Maybe you are looking for