Forum Discussion

The_Bhattman's avatar
The_Bhattman
Icon for Nimbostratus rankNimbostratus
Sep 01, 2009

invalid connection Information...

My irule editor was working last night and today suddenly I get "invalid connection Information...". Now it works if I use the proxy settings, but I was able to connect directly, w/o the proxy information entered. I also noticed in my sniffer trace that the iRule doesn't make an attempt to leaves my nic. Any ideas?

 

CB

10 Replies

  • I don't think it's taking the Proxy settings from I.E. because at the very least I shoudl have see packets leave my interface and there was zero packets leaving the interface - that is until I manually added a proxy setting.

     

     

    But hey it is a great product.

     

     

    CB
  • It returned back to normal after then 6th uninstall/re-install and reboot.

     

     

    CB
  • This is hard for me to test since I don't have a proxy to test it through. All I know is that under the seams it's using the .Net HttpWebClient classes which most likely inherit the IE settings but I can't be for sure. There is nothing that changed in the last few weeks code-wise and I've definitely not uploaded any new versions that would have automatically downloaded that would effect connectivity.

     

     

    For those that are having this issues, please reply to this forum and give me your configurations and I'll see if I can find out what's going on.

     

     

    -Joe
  • Also, it's totally bizarre that a uninstall-reinstall would fix a connectivity issue. I'm at a loss on this one.

     

     

    -Joe
  • Did you check out Hoolio's response above about Proxy and IE?

     

     

    Bhattman
  • Will_'s avatar
    Will_
    Icon for Nimbostratus rankNimbostratus
    I was also having this problem after it was working. I realized I was using an internal proxy which it must have picked up the settings from. I tried "Clearing History" on the connect dialogue box, but NG. It only works now when I have my Fiddler proxy started and proxy to 127.0.0.1:8888...

     

  • Any updates on this? I am getting the same error too. Tried with an external proxy and did not work. Also tried with fiddler but no luck either.