IE lan settings revert back when rpt open it during recording http proxy - ibm-rational

I am beginning to use Rational Performance Tester to do some load/performance testing and I stuck at the first step - recording a script. I am using IE 11 and I am disabling internet by going to Internet Options>Content>Lan Settings. Then I try to open some website and it won't open - which is good (expected behaviour). Then I run my RPT to do the recording and the Internet options revert back and 'Automatic Configuration' check box get checked (unwanted behaviour). The HTTP proxy recorder say that it is accepting connection at (some number) port but open connections stay 0. The bytes in the recording window do not move with any click, thus nothing being recorded. Thanks in advance!
I have only tried it in IE 11. Don't have access to any other browser (company policy)
There is no coding required.
I expect open connections to move above 0

This issue was solved when I had admin rights to the machine and application - run IBM RPT as administrator. Thus I was able to record the http traffic and successfully play it back using the load agents.

Related

TestCafe Sudio setting different timeout, when recording

The problem is specific to the recording. I found timeouts settings in the browser properties of the TestCafe Studio and they work when I press "Run Test" button. However, whenever I press "Record test" the editor seems to ignore my settings and I get the request timeout error:
Failed to complete a request to 'address.com' within the timeout period. The problem may be related to local machine's network or firewall settings, server outage, or network problems that make the server inaccessible.
I tried changing the recording settings, but they don't seem to work either.
The site is up and working, just takes a while to load.
Indeed, TestCafe Studio does not support the same settings in recording mode as in run mode.
As a workaround, temporarily place the await t.wait(timeout) function at the beginning of the test.

The console has been disconnected. Close this window and re-launch the console to reconnect

I am having an issue when trying to open to any VMs using "Launch Web Console" option via the vcsa 6.7 . I was wondering if someone could please point me in the right direction?
My environment currently looks like this:
1) vcsa 6.7
2) Three Esxi (6.7) Hosts & multiple vms are running (including windows & Linux)
Whenever I try to connect to the console, I get the following error:
The console has been disconnected. Close this window and re-launch the console to reconnect.
Console access is given through a connection to the ESXi host.
Often times I receive this message when connected to the console of a VM which has vMotioned to another host. However, I can close and re-open the console just fine.
You may also want to verify that you can access port 902 (TCP & UDP) for each of your three hosts. Example of this requirement: https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.install.doc/GUID-5071C86E-FF1E-4E54-A424-A20917401160.html
I had the same exact problem and unfortunately, the solutions I found on the internet did not solve my problem. I had to re-check my settings and found out that the problem was the proxy setting was ticked on. which it won't allow you to connect to any others services as well if you are out of range of that proxy. The Solutions "FOR MAC USERS" as follows:
1-Go to your network settings.
2-From the menu down to the right-click more options. in my picture say (Weitere Optionen) "German".
3-From the menu on the left side make sure that the proxy option is 'unticked' (not chosen).
Then click on to confirm and enjoy using your VM service. Hope this would solve your problem as well as it did to mine.
See pictures!
https://i.stack.imgur.com/1PjjP.jpg
https://i.stack.imgur.com/1jnJf.jpg
https://i.stack.imgur.com/8XiAY.jpg

LoadRunner VuGen Script Replay Failing for Citrix Module Login

I am using LoadRunner VuGen to record a test I would like to execute using a Citrix module. I am able to successfully record the actions but when I play the actions back, it stops at the following line of code:
ctrx_wait_for_event("LOGON", CTRX_LAST);
The Citrix ICA Client screen is displayed and it is waiting for the Username, Password, and Domain to be entered by I am unable to manually enter the information in and after a couple a seconds it fails. When I initially record my actions, I am logging into Citrix via a web URL. But when I play back the actions it goes directly to the Citrix ICA Client screen without ever opening the URL.
This is Citrix application where Logging into the Citrix Desktop is taking too much time than the parameterized hence throwing the TimeOut Error.
In the error if the IP address is also mentioned, then it is usually is a citrix connectivity/network connectivity issue.
We had a similar error without any IP address, we did the following which resolved the issue:
Check if there are any active citrix sessions, if yes clear/terminate all the sessions. Then run the VuGen script from VuGen and dont try manually
Upgrade the ICA client if it is older than 13, we are using 14.x version

IE 10 not using AppCache after browser closed

I wrote an application using the HTML5 Cache Manifest and I'm having a problem using it in IE 10.
I used Fiddler to witness the manifest file being downloaded and all resources fetched on the initial load of the application. If I disable my network adapter to force the machine offline, the application continues to work as expected as long as I don't close the browser window.
However, when I close the browser window, then attempt to re-open the page from a favorite, IE 10 tells me "You're not connected to a network". Obviously I know that, I'm trying to use the app offline. These exact steps work in Chrome.
Is this behavior by design? Is there a workaround? I can't test with IE 11 right now...is this different in IE 11?
Hearing of some issues of the appcache clearing if your company utilizes gpo settings and has "empty temporary internet files folder when browser is closed" enabled.
Did you find the answer to this? I have the same problem. I did get a bit further though. I found that if you go to the IE10 File menu option and tick Work Offline then try and access your cached app it loads the page but I still have an issue as it does not appear to be using the javascript file that should also be cached. All works ok on Google Chrome but our clients are restricted to IE so Chrome is not an option.

IE10 in Win RT can not connect server on local network

When I browse the web with IE10 in win8's Metro part there is no problem but when I try to view page that is located on server in my local network(the same subnet) it displays this message:
This page can't be displayed
•Make sure the web address http://192.168.1.100 is correct.
•Look for the page with your search engine.
•Refresh the page in a few minutes.
If following these suggestions didn't work, resetting your connection might help.
Reset connection [<-a button here]
Get more help with connection problems
Now the funny part is that there is an option in metro version of ie10 to open page on desktop (in regular IE10) and than it works with no problem.
I can't find or think of any security setting that would restrict browsing websites inside your own local network.
(this is Windows 8 32Bit Release Preview build 8400)
Any ideas?
This is related to EPM (Enhanced Protected Mode) in IE10. It's hard to summarize in an answer here, but Eric Lawrence (a PM on the IE team) has an excellent post detailing everything about EPM:
http://blogs.msdn.com/b/ieinternals/archive/2012/03/23/understanding-ie10-enhanced-protected-mode-network-security-addons-cookies-metro-desktop.aspx
In particular, read the "Loopback-blocked" and "Private Network resources" sections.
In your case, you might try one of these approaches:
Try aliasing the dotted hostname (http://192.168.1.100) via a custom DNS entry (e.g. http://myservice)
Change the Trusted Zones settings
See if your network connection was established as sharing or non-sharing, which would trigger private vs. public mode.
Again, see Eric's post for the details of each of these.