i have tsung setup in my remote linux server.(54.54.90.90) no browser here.
i have my windows machine (122.122.130.130) where i browse my web app through firefox. i have changed firefox settings to use SOCKS proxy on port 8090 (http://blog.ashurex.com/2012/03/15/creating-ssh-proxy-tunnel-putty/) to route all traffic from my windows laptop to linux box to the internet rather than from windows laptop to internet.
now i started tsung-recorder which runs by default in 8090, hoping whatever requests i make in my windows laptop will be recorded here. but no session is recorded.
I want to record a tsung-recorder session in my linux machine as i browse in my windows laptop. please help.
Just configure an HTTP proxy on Firefox and point it to the remote server where your tsung-recorder ran using port 8090.
Related
in the last days chrome and edge stopped working to access localhost domains o my windows machine. Firefox is still able to, so I guess it has something to do the browser engine.
My setup: I have a vm started with vagrant on hyper-v. Inside the vm is my apache webserver.
On my windows 11 operating system the hosts file points my local development websites to the ip of the vm. This was working for the last years without any problem.
DNS over https is not enable in Edge or Chrome.
I already have tried using different local domains like localhost or .local. without success
I have tried ipconfig /flushdns without success
I reinstalled Chrome without success
My host file is
172.28.148.95 workspace.localhost.de
127.0.0.1 workspace.localhost.de
What can I do, that Edge and Chrome can access local domains?
I am trying to test offline feature of my HTML5 / Java application. I can imagine 2 ways to simulate that locally.
I turn of the wi-fi / internet of my laptop. But localhost 0 127.0.0.1 doesn't have anything to do with internet and it still keeps serving my request.
I stop the tomcat. In this case I get the standard browser error page (Unable to connect error message).
How could I test this on my local tomcat?
You could try disabling your network adapter. That would probably do it.
Instructions for Windows
Instructions for Linux
I have a Windows 2012R2 instance running at GCE and successfully can log in via "Chrome RDP", a Chrome RDP client that is launched by the Developer Console if you click on RDP. I also used the "Chrome RDP" Chrome Web Store App via an ssh tunnel to a linux instance in the same project and network.
I then installed Google Chrome and set up access via "Chrome Remote Desktop", but when I access the box, the screen is just a big black square. I think this is all related to the fact that there is no "Display Adapter" section in the "Device Manager".
I'm hoping someone could tell me what the requirements are to run "Chrome Remote Desktop" on a virtual machine with no monitor installed that has no "Display Adapter" drivers.
I wasn't able to reproduce the issue as I was able to remote into my VM using the "Chrome Remote Desktop". The only thing I could think of is that you might need to update Chrome and Remote Desktop App.
Another thing to try is to create a new Windows 2012R2 instance and see if you can use the Chrome Remote Desktop to log into it before making any changes to the instance.
I am running a Windows Server VM Instace on Google Compute Services... I can access the instace via the "Windows Remote Desktop" no problem... I could install Team Viewer on the instance...
Because of Firewall issues I cannot run "Windows Remote Desktop" from my desktop to access that VM (google compute) Instance... Reason of why I installed Team Viewer on that VM instance...
The funny thing is that I can access that VM instance through Team Viewer Only, as long as it is connected through "Windows Remote Desktop" to a separate 3rd computer... (4G internet outside the firewall --of desktop trying to access the VM Instace through Team Viewer--).
Even if I minimize the "Windows Remote Desktop"on my laptop it will cut the connection through TeamViewer between the VM cloud instance and my Desktop computer...
Any help or ideas in there? It seems that either Team Viewer isn't able to start or somehow either the VM Windows Server screen only runs when the "Windows Remote Desktop" is running....
As I get this message:
"The screen cannot be captured at the moment. This is probably due to fast user switching or a disconnected/minimized Remote Desktop Session."
I did a complete version installation of TeamViewer as administrator, running on a Windows Server on google compute VM.
Hopefully someone out there can help me! I don't know if it may be part of the Google Compute Services Instance settings so as to limit the remote desktop only to the native "Windows Remote Desktop" program... Or perhaps a setting were since it's a VM the screen is de-activated when the "Windows Remote Desktop" program is off or minimized etc...??
My main problem is having TeamViewer work without having to initiate the native Windows RDP... In order for TeamViewer do it's job and take its place... as in the place where I am located (my desktop computer) the firewall blocks Windows RDP but does not block TeamViewer's.
I tried changing the listening port to different numbers....
According to the instructions here:
http://support.microsoft.com/kb/306759 and here:
http://support.microsoft.com/kb/304304/
Unfortunately.. when I changed it and then rebooted the Win Server 2008 VM, and checked to see if it made the change... I noticed it goes back to be on the same port again.... (of course to connect I had to do it through the original port)...
So it changes it but on rebooting it goes back to be on the same port again... I don't know if it's either because the new port was being used or there is a policy somewhere directing it always to the original port again...
I enabled those ports also to work for RDP in the Google Compute Instance interface, but still it made no difference...
It doesn't seem TeamViewer has a setting to change the port it connects with etc...
Hopefully I can find someone knowing about this issue.... The AWS instance used to work fine with LogMe In at the time.... I may end up using AWS (Amazon Web Services) again as Google Compute Srvs. won't do the job... but it's much cheaper than the AWS isntance... Thanks for helping...
In my case it happened due to slower network speed on the other side, of which I intend to take session.
I am facing an issue with windows 8 phone emulator.
Windows Phone emulator wasnt able to connect to Windows Phone
operating system. Phone didnt respond to connect request
This is the error that I get. When the emulator starts with internet but my application doesnot deploy. The ip that gets assigned is 192.168.137.1. Previously it worked fine,
but then suddenly it started giving this issue.
Below is the list of troubleshooting that I have performed:
169.254.xxx.xxx address set to internal emulator via dhcp, Application deployed successfully with NO internet connection
Have tried MAC address spoofing but nothing works when I use these settings.
Have changed External Virtual Switch in Sharing mode this starts the internet with ip 192.168.137.1 but application doesnot deploy
In debugger errors shown are:
Invalid pointer error
App deployment failed
Have tried Network bridging but still it doesnt work.
Created all settings manually including the internal switch and external swithch. But same issue faced when it gets 192.168.137.1 ip then internet works but application doesnt deploy.
And when it gets 169.254.xxx.xxx ip series application deploys but no internet connection.
No firewall are turned on or no antivirus is blocking any connections.
Wireless router used for network connectivity, still not successfully
Have also tried clean installation of everything but still no go.
Need help with this issue as I have been trying to get it resolved since a week.
This issue is not faced if installation is done on the same pc through a virtual machine.
What I did was :
Have allotted 4gb ram, 60gb hdd & 4 cores to the VM.
1)I installed a virtual machine with default settings.
2)Then I stopped your virtual machine (shut Windows 8 down, DO NOT suspend it).
3)At the VMWare Virtual Machine list, right click Windows 8 machine then click "Show in Finder".
4)Right click the file then click "Show package contents", then find and open with a text editor a file with the extension .vmx
5)Go till the end of the file and add this two lines (first check whether they were previously added):
hypervisor.cpuid.v0 = "FALSE"
vhv.enable = "TRUE"
6)At the VMWare Virtual Machine list, right click Windows 8, click "Preferences" then "Advanced". Choose "Intel VT-X with EPT" as "Preferred virtualization engine".
And then when I started the windows in the virtual machine it seems to be working fine without any additional setting change. However it is still not running on a physical machine
I recommend if someone is facing a similar issue then to use a Virtual Machine till this kind of issue is resolved.
Struggling with the same problem for 3 days I finally solved my issue by disabling windows firewall for "Guest or public network". I have yet to figure out what application/service to allow through so I can re-enable it.