Got this legacy Avocent DSR2035 KVM over IP. Works! Anyone knows how I edit the TCPIP setting on this machine? I have access to the console, it works, but there is no IP settings in any of the menu!
It took some time to figure this out. I had to upgrade firmware first and that was done through the setup port in the back and using a special cable that I built. After the fw update, there were network settings in the standard interface.
Related
So, I have been building this website with HTML and I decided to host it with on Apache2. It runs on an Ubuntu and me already changed the VM assigned Ip, which is 10.2.0.15, into another one. I can access it on the Mac where the VM is, but I asked my friend if he can open it, and he said it was a 404 Server not found error.
Please help!
You probably need to enable port forwarding:
https://www.howtogeek.com/122641/how-to-forward-ports-to-a-virtual-machine-and-use-it-as-a-server/
You haven't indicated what VM software you are using, but the above is for VirtualBox. VMware is a bit different. Also make sure your router is not blocking any packets or any firewall.
Let me start by saying that I have no experience with Linux and this is my first attempt at getting into the IoT with a raspberry pi3. My question is why can I connect via ssh to my pi when I use the ip address but not the hostname?
After getting everything set up at home, I tried to remote in via PuTTY from my laptop. (The laptop is less than 6 months old and if I need to provide the specs on it, I can. It is running windows 10 if that matters). It worked when I entered the ip address of the pi, but when I tried again with the host name (which is clearly defined in the raspberry pi configuration) it said host does not exist. I used hostname.local and still failed.
Today, I brought the whole setup to work to try a few more scenarios. From my work desktop, which is running windows 7 and not wireless, I could remote in via hostname.local. I then tried again on a different laptop running windows 7 and it worked too. Next attempt was on another new (less than 3 months old) laptop running windows 10 and it failed to remote in via the hostname.
This would tell me that there is nothing wrong with my home network or the network at work, and it also makes me think that this has nothing to do with the pi, since other computers can resolve the hostname to the ip address and successfully login. What the hell am I doing wrong or missing?
I spent 2 nights googling and browsing forums trying to find an answer for this but cant, so instead of bashing this post, please poke me for more information you think might be helpful for a solution.
EDIT I gave my computer and PI to my cousin to fix. He installed Samba, though I don't know what it does differently. After doing more research, it sounds like the problem I was having was a DNS issue. I don't know how it was resolved by downloading samba on the pi, but I can now connect via the hostname.
So if I understand correctly it would appear that there is some particular settings on that laptop preventing you from using SSH if that is the only thing you are changing? I think this is likely to be something to do with the security settings on the laptop but Windows isn't my thing sorry.
I am able to hook SharePoint 2010 VHD with vmware. The central admin comes up but port 80 dont even come up. I ran into this http://blogs.msdn.com/b/steve_fox/archive/2010/06/15/rtm-demo-vm-for-sharepoint-amp-office-2010.aspx article but I dont know to perform this in VMWare Station 8. Please suggest.
Ping localhost host gives 127.0.0.1. But I get 404 both on localhost and 127.0.01
Ping to intranet.contoso.com takes a long time and i get request could not find host ....
Binding looks good too.
I am not seeing anything in IIS log . I mean nothing specific to intranet.contoso.com.
Looks like a DNS Issue to me. Try to add intranet.contoso.com to the hosts file as:
intranet.contoso.com 127.0.0.1
If this works then it is definitely a DNS issue, check if the service is running.
Also check if you actually assigned a virtual network card to the box in VMWare.
Update: To add NIC to VM Ware you edit machine settings and add hardware, add a network card as bridged. You can then manage the network card normally inside Windows.
I am using Hyper-V for the first time (running Windows 8). When I create a new virtual network switch, external, it bridges the VMs network adapter with the WiFi - and that for some reason kills the WiFi's internet connection. Why, and what could I be doing wrong?
Thanks,
A.
If you have VirtualBoxinstalled, check if any of the Hyper-V virtual adapters/bridge connection has the VirtualBox Bridged Networking Driver ticked in the connection properties. If they do, simply untick this service where it is present and this should fix it up for you. No need to uninstall VirtualBox.
I had a static ip-address in my ethernet adapter.
Removed the static entry.
Made my external virtual switch.
Had the extra vEthernet adapter, made my static entries (ip-address, dns-server) in this adapter.
Everything is working fine now.
Chris
I had the same problem, it takes a couple of seconds to setup the connection again. Check this tutorial: https://superuser.com/questions/469806/windows-8-hyper-v-how-to-give-vm-internet-access
I just ran into the same problem, losing the internet connection when creating the virtual switch. Uninstalling VirtualBox which I had installed at the same time fixed the problem for me (just disabling the VBox adapters was not enough), so they seem to be unable to happily coexist.
I ran into the same problem recently when creating an external switch in Hyper-V. Long story short, every time an external switch was created, it would bring my ethernet connection down on my host laptop. I had wifi connection option also but disabled it to just strictly troubleshoot the ethernet network adapter.
I brought down the VM, once turned off, deleted the external network adapter from hyper V virtual switch manager. On the host machine, disabled and re-enabled the network adapter from within network connections (ethernet). Once connected, I brought the VM back online FIRST, then created the external switch second which connected with no issues. Verified I was able to access outside world aka internet on both host and VM.
Maybe you unchecked by accident the Allow management OS to share this network adapter setting that is enabled by default. Disabling this setting will leave your hypervisor OS without network connectivity.
I was able to fix such an issue by disabling Internet sharing on the wireless adapter, creating an Internal virtual switch in Hyper-V first, then disabling VMWare bridge on all involved interfaces, then I made a bridge in Network sharing center by selecting my internal switch and Wi-Fi adapter and after that I was able to select external network in Virtual switch manager in Hyper-V
I ran into the same problem too. I don't know for sure, but after trying all of the solutions above and any others I could find, I renamed my virtual switch to 'realtek' (the type of network card I have installed) instead of taking the default name that I think was 'new virtual switch'. Something else I did may have solved the problem (I modified everything I could find for two days), but I think renaming it is what finally gave me internet access to the vm.
I'm currently developing a simple multiplayer game app for Android and I need to have a server to which the users connect to.I'd like to set up this server at home. I have a dynamic IP address,so someone told me I'd have to set up a local DNS server or something like that. I'm not even sure where to start with setting up a DNS server, everything I found was for windows 2003 and linux. Nothing for XP? If any one can shed some light on this matter, explain a bit how setting a DNS works or supply a link with "setting up local DNS for dummies" I'd be grateful.
Also, besides setting up a DNS so I can find the server every time, how about the communication with it? I'd like for it to be as secure as possible. Another friend told me something about communicating via SSH, which is again something I am not accustomed to.
So if someone could explain some of these concepts or offer some GOOD link for that that would be great. I'm very confused :)
Thanks
EDIT
Btw, the server is in Java and currently i'm communicating from Android emulator to the server (which is localhost) via sockets.
That's not a simple thing you're trying to achive. First you have to create your own server on your machine (maybe you're done with this step), then you have to make this server available for everyone. At this point, I suggest the DynDNS service:
http://lifehacker.com/124804/geek-to-live--how-to-assign-a-domain-name-to-your-home-web-server
A local DNS by default help you to find your own servers by name instead of IP address, but if you have a usual internet service with dynamic IP, you need an external DNS provider to route your clients to your server. (read the link above for the full explanation)
About the SSH security: Yes, you will need some security settings indeed, but that could be a very hard problem sometimes. You can set your server to work with SSL sockets, which is a part of the core J2SE release. It will work against some sort of attack, but none against others. Running your own server will raise unexpected numbers of problems, prepare for that.
As already stated in the comment to your post, something like http://www.no-ip.com or http://www.dnsdynamic.org would solve the issue with your dynamic ip - You do not need a local DNS server.
With regards to communication, i believe that SSH is linux/unix only. Since you wish to use Windows for the server, FTP or Remote Desktop would be best. Choose FTP if all you want to do is manage your files, choose remote desktop if you wish to manage your entire computer. I've had good results with the FileZilla FTP server on windows (http://filezilla-project.org/)
With that said, i think you would be better off buying a simple and cheap hosted service instead of using your own computer - you can get something that can run your java app for $5/month some places, and compared with the annoyance of having a local server running in your house, it might be worth it.