I accidentally told my network adapter to use a bad ip address in my Internet Protocol Version 4 (TCP/IPv4) properties. A big oops look spread across my face as I pressed the OK button and immediately got disconnected from my remote session. Naturally I can't remote back in and even azure can't reboot the vm. Is there any way I can recover from this?
So things I would do include:
1. Redeploy
2. Try to change VM ip using the portal\powershell
3. Delete the VM and deploy new one using the same os\data disks.
Related
Both devices are connected to the same WiFi network.
I have set IIS bindings to allow connections to my IP:
However, my computer's IP address is the same as my iPad's.
Is there a way to make this work?
That's not your IP. Every time you use a laptop on a Wifi network, you'll be using the public IP address of whatever network you're on.
The IP address of "your" computer doesn't belong to your computer. It belongs to the network you're connected to. Your computer is just borrowing it for a while.
Try to set a static IP address for your computer and use another machine to send ping command to it. Then use iPad to connect.
Initially when I posted this question, I was using an xfinitywifi hotspot and I assume that came with a whole host of problems. Full-disclosure, I did not figure out how to make it work in this scenario.
However when I moved to my own home wifi network, I was still having this problem.
I had to do two things, one of which, I know is not recommended, but it was really easy.
First, I had to enter my network and sharing center and set my connection as home connection instead of public which is what I previously had it at.
Second, which is not recommended, I turned off Windows firewall. I only do this when I need to access my site from another device for debugging. I turn it back on when I am done. For a more permanent setup I know it is recommended to just enable the port you need, but I could not figure this out.
I have trouble getting my VMs into the domain.
Several old machines functioned as "servers" in our environment and when I newly started working here, I wanted to change this cluster into something more appropriate. So I calculated how one big server would cost us a certain amount of money but we would save it in electricity-bills etc.
The server finally arrived (HP Proliant) and I installed a Server 2008 R2 on it (boss wont pay for something newer a.k.a. more expensive). I created .vhd files of the HDDs of the servers I want to virtualize and copied those files into the new server. I activated Hyper-V role and created a new VM and selected one of the .vhd files as the HDD for that VM and started the machine. The machine starts, all goody.
As far as I understand in Hyper-V we got 3 network-settings and for my purpose "external network" is the one to go with. Correct me if I'm wrong. The server is already in the domain. So I thought it should actually work already, but somehow I cannot connect to the domain.
The network settings on the VM is DHCP but it is not getting an IP from the DC. Do I need to spoof the old MAC-Address? Do I have to turn the physical machine that I'm virtualizing off? (I didn't do that because I wanted to check first whether I can get both running at the same time before turning it off. Also I cannot access the environment past business hours, so testing this is when nobody is around is kinda out of question)
The VM has W7 running on it, if it matters. I'm kinda lost what to do as I only find how to join a VM into a virtual network when I try to google for solutions.
DC (physical, x.x.x.1 IP), The new server (physical, x.x.x.82 IP), The VM (virtual, DHCP, current address of its physical copy x.x.x.123 though DHCP is set on it, 123 is just the IP it got).
Regards
Edit: Found the solution. The server has 2 NICs. "Connection" and "Connection 2" or whatever it is called by standard in English. The virtual adapter (3rd NIC so to say) has "Connection 2" in its description too. I got confused and addressed the wrong NIC in the Hyper-V options. I am editing this from the VM that finally has connection to the domain.
Has been resolved. Answer is in the edit of original post.
I accidently broke my centos VM in azure by twiddling firewall rules within it. After a reboot, the normal ssh access is not working anymore. Is there any chance to get into that VM, any console login directly to the machine somehow?
After reading the current state (April 2016) at microsoft about this, I've decided to dump the virtual machine and set it up again:
This one-directional access is just a start. Console screenshots and serial output can help identify a problem, but they are not the solution for resolving the problems. We are working on enhancements that will enable secure bi-directional access to the console of the virtual machine. This will enable additionally debugging capabilities, and, more importantly, the ability to resolve a set of common problems through the bi-directional access. Right now, I don’t have a timeline but we know this is critical.
(article)
I connected two laptops using a cross-over cable. My IP Address is 192.168.1.1 and the other IP Address is 192.168.1.16. We both are able to ping each other and the reply is perfect. There is no loss of packets.
The problem is I shared a file and the other system is not able to open my IP Address using the run command. Even I am not able to open my Shared folder by giving in the run (\\192.168.1.1). A dialogue box with the message \\192.168.1.1, The Network Path was not found opens each time we try this.
But I am able to open his shared folder by giving in run command (\\192.168.1.16). I closed all the firewall services in my system. But still my system is not able to respond. Also we are not able to use remote desktop connection.
Can anyone please help me in solving this?
Additional Details: I use Windows XP and the other machine uses Windows 7. We both are in the same work group.
Here are some steps to solve your problem:
Did you set the static IP by yourself or that come automatically?
If yes then please go and set the IP manually
Then share the file and put the permission of that file to Maximum (If you believe your partner)
Then power down the firewall or antivirus for some moments (say 10 minutes)
Now try to connect using the \192.xxx.xxx.xxx method using the Run window
If the 5th step is not working, then try disabling and reenabling the LAN card, then try the 5th step again.
Hope that solved your problem.
Remote Desktop needs to be explicitly enabled. Right click on "My computer", go to properties and look at the remote settings tab.
I advice you to use Radio Access Point to connect both windows 7 and windowsXP. I think this is best choice of troubleshoting jaringan. why?
Because I already do anything to connect both Operating System but can't solve that problem.
I'm setting up a linux server in a VM for my development.
Previously I've had PHP, MySQL etc etc all installed locally on my Mac. Apart from being a security risk, it's a drag to maintain and keep up to date, and there's a risk that an OS upgrade will wipe part of your setup out as the changes you make are fairly non-standard.
Having the entire server contained within a VM makes it easily upgradable and portable between machines. It means I can have the same configuration as the destination server and with shared folders even if the VM gets corrupted my work is safe on the host machine.
Previously with the local installation I was able to develop on convenient URLs like http://site.dev. I'd quite like to carry this over to the VM way of development but I'm struggling to figure out how, if it's possible at all.
Here's the problem:
In Bridged mode, the VM is part of the same network as the host. This is great but I can't choose a fixed IP address as I may be joining other networks and that address may be taken already. I'd like a consistent way of addressing my VM.
In NAT mode I can't directly address the VM without using port forwarding. I can use http://site.dev if I use the hosts file to forward that to localhost and then localhost:8080 forwards to the vm:80. The trouble is I have to access http://site.dev:8080 which is inconvenient for URL construction.
Does anyone know a way around this? I'm using ubuntu server and virtualbox.
Thanks!
The answer is to define a separate host-only network adapter and use that for host->guest communication.
You can do this by powering down the guest and adding the adapter in the VM settings. Once that's done you can boot the guest again and configure the new network interface however suits you best. I chose a fixed IP address in an unused range.