I've got Parallels running on my Macbook Pro and I'm developing a small application that needs to be run exclusively on mobile devices (using sencha touch).
The problem is that my Windows 7 IP address in Parallels is 10.211.55.0/24 and our local network is 192.168.1.0/24
Accessing the IIS application via Firefox or IE is not acceptable since I need to test on the iPad and iPhone.
Does anyone know how to expose IIS applications to the network from within a Parallels VM?
Forget I ever asked such a stupid question.
I simply had to put my VM in Bridge mode rather than Shared Network
I was looking in the wrong place (Parallels config rather than VM config)
Related
I have mac-mini configured and running at my home.
And I want to pair my Visual Studio to that mac.
Is it possible to configure it as a build host in case when it's located in a different network ?
i.e. Mac is at home and my Windows/Visual Studio setup is at work.
Your OS-X machine has to reachable by a secure shell connection (SSH) over port 22.
If you can ssh from your Windows' PC to your Mac, say using Putty, then yes, you can make Visual Studio/Xamarin connections to that Mac and use it as a build host.
1) You can bridge two private networks via a VPN
2) Expose your Mac (port 22) to the public Internet (buyer beware)
The key issue, other then security on your Mac, is the speed/bandwidth of your connection between the two machines. Well the amount traffic is not really heavy if you are just using it as a build-host and not using the iOS removing simulator, network latency can be a real performance killer.
If using the (new) iOS Remote Simulator, bandwidth requirements climb and the high network latency can make it a non-solution in some situations.
(It only a Mac-Mini, almost fits in a pocket, take it to work with you ;-)
Your Mac needs to be accessible via SSH (port 22) from the PC running Visual Studio. You will need to setup a VPN or configure your home network to properly forward port 22 to the Mac.
I am developing an application windows 10 on a stationary PC. I also have a tablet windows 10 that once connected to the PC via USB not see debugging (
How to make it accessible?
Ok so I found an article that highlights how to debug a UWP application on a Surface pro using a cable:
Essentially the Visual Studio debugger wants to debug your application via a network, so you are creating a network between your desktop machine and your surface pro.
Below is the guide with the main steps highlighted
https://tomsoderling.github.io/Wired-Debugging-on-Surface/
Hardware Needed
In order to debug over a wired connection, you’ll need a few things:
2 USB to Ethernet dongles. You can find them for pretty cheap on
Amazon.
A length of cat 5 cable to connect the two dongles together.
Connect the dongles together with the ethernet cable, and plug one
dongle into your laptop and the other into the Surface.
Launch the remote debugger program on your surface and configure the following:
No Authentication
Turning this off seems to alleviate a lot of the
hassle of trying to get the debugger to connect to the remote client
app. I debug on a private or wired network and only have the remote
client running when I need to debug, so the lack of security doesn’t
concern me here.
Allow any user to debug
I use this setting because
don’t log into my Windows 10 VM via Parallels so I’ve had an issue
with that. I also use this when my coworker needs to debug on the
Surface.
And then your device should be found in the Auto discover in visual studio
A few useful pieces of information: I'm running Windows 8 Professional on a custom-built rig, and I am using a 'WiFi dongle' to connect my computer to the local router. I am using a home network, not a public/work/school network.
I installed the Windows Phone SDK. Piece of strawberry cheesecake so far. Coded my first simple browser app (as detailed on the Windows Phone Dev site) and hit the Run button, expecting my app to come to life and breathe in links and breathe out websites!
But instead, I got this:
Something happened while creating a switch:
Xde couldn't find an IPv4 address for the host machine.
In this case, the emulator wouldn't run at all. And so, I did my research and found out that the solution was this:
Remove all the switches from Hyper-V Manager's "Virtual Switch Manager", and make a new Internal one called Windows Phone Emulator Internal Switch.
I did, and the error did NOT show up again but it did screw up my WiFi and Bluetooth adapters (which I had to do a system restore to solve) and now both WiFi and Bluetooth peripherals are working again.
However, I got this error instead when running the emulator again:
The Windows Phone Emulator wasn't able to connect to the Windows
Phone operating system:
The emulator couldn't determine the host IP address, which is used to
communicate with the guest virtual machine.
Some functionality may be disabled.
In this case, the emulator did run, but I couldn't find my app anywhere. I did some research again and found that the solution to this was:
Delete the Windows Phone Emulator Internal Switch from Hyper-V Manager's Virtual Switch Manager.
Now, I created the switch to solve the problem in the first place. But I did delete it, for the heck of trying everything out. And no surprise there but, it went back to the first error.
I am now stuck in this paradox and have no idea how to escape it.
Thank you in advance!
follow the following steps to solve this problem
1.go to network and sharing center
2.go to change adapter setting
3.go to v Ethernet (internal Ethernet port windows phone emulator internal switch)
4.right click it and enable it(if already enabled then disable and enable it again).
Remove any Cisco VPN's or similar connections. I have found this VPN client works as a replacement to Cisco https://www.shrew.net/
For me shrew soft version 2.1.7 was the only version that worked.
I have parallels installed on my mac and I have installed windows 8 as a virtual machine. I am able to run an application running on the mac localhost in windows 8 but now I would like to run a .net app on the mac (i.e. localhost:50055). I have read numerous solutions but none is working for me. What am I missing?
I just bashed my head against this for a couple of hours too and I think, in the end, the piece I was missing was turning off Windows 8's firewall.
This accepted solution is what clued me into turning off my firewall, as soon as I did that it worked.
Access Parallels Windows localhost from Mac
You'll probably have to "enable" anonymous authentication in Authentication setting in IIS Manager" too according to Matt Gibson's solution.
What I ended up doing:
Found the VM's ip address by pulling up the command prompt and typing ipconfig
Updated my Mac's host file by adding the VM's ip address (in my case it was 10.211.55.3)
Checked Parallels VM Setting -> Configure -> Hardware was set to Shared Network
Windows Firewall - turned off for Private Network Settings (Control Panel\System and Security\Windows Firewall\Customize Settings)
Checked IIS Authentication -> Anonymous Authentication is Enabled
This worked for me, hopefully it'll work for you too.
I am running Ubuntu 10.10 and also Windows 7 under vmWare Workstation within Ubuntu.
My internet connection in vmWare is shared from the host as 'NAT'
I am using XAMPP on Ubuntu for developing sites. I use http://localhost/mysite to open the site under development in Ubuntu.
I wanted to use a similar command to open these sites in the Windows 7 installation under vmWare.
While browsing some of the topics I came to know that it is possible by using some IP of 'NAT'.
I am totally new to Linux and vmWare both. Just migrated to Linux from Windows and need help understanding it in detail.
Kindly help me with the process of How to access these sites in vmWare.
Please help.
VMWare's installer should set up a new network interface on your Ubuntu system, check ifconfig -a to find its IP address.
Make sure your webserver is listening on either 0.0.0.0 OR (127.0.0.1 AND the vmware-interface IP address).
From the Windows system, try typing in http://<vmware-interface-ip>/mysite. Hopefully it'll go. You can check the windows networking control panels to see what the gateway address is, it'll probably match.
I hope this gets it going for you.