I upgraded my desktop machine from windows 8 to 10 and now I'm unable to connect to any of my Vms (hosted on another server) using RDC.
I have one server(Ubuntu no GUI) that host multiple VM's(windows and Linux w and w/o GUI) using VirtualBox. From my laptop I normally connect with RDC using the host(server) ip followed by port number (192.168.0.2:3396 assigned during create VM process) works fine, at that point I adjust network setting(static ip) for the LAN and exit. etc etc..
On the windows 10 desktop I receive and error; This computer can not connect to the remote computer. I can however connect with the ip address (192.168.0.5) no port. this part is fine for existing Vms that have static ip. I need to connect and assign the ip.
Thanks for any feedback or suggestions
Related
I have a SQL Server instance in docker which maps its port 1433 to host 1433.
It's working and I connect to it.
Next, I have a Windows (actually, its old Windows 7) virtual machine in Hyper-V on same host. Virtual machine can see host (to be specific at ip 192.168.10.1).
But from virtual machine I can not connect to SQL Server on port 1433. I can't simply open a socket from virtual machine (have tried though python).
I've tried to stop docker container and start simple web server on 1433 port and I can easily connect to it from virtual machine. But once SQL Server appears there, something goes wrong.
Any ideas, what may be wrong or what to check (just got a humble idea that may be caused by MTU, but not yet checked - makes sense?)
I'm using a container to develop for an embedded system. To interact with the debugger I need openocd running on the host machine (as it needs USB access, and it's on a Windows machine therefore I can't access the USB port from the container), and connect to it with a gdb running in the container. I'd like to know if it is possible to forward/connect to a port from the host machine - from all that I've read until now this does not seem to be possible?
My current workaround is to run an SSH server in the container, forward it's port and open an SSH connection from the host to the container with reverse forwarding the openocd port. But that is quite a bit more convoluted than I'd like.
Just exposing the port to the local network and connecting via the public IP came to mind as well, but our corporate firewall blocks that.
I'm currently having a Macbook Pro M1 as my development machine, running Docker on Mac for my containerised applications and Windows 11 VM using Parallels as my development environment. In this Windows VM lies the SQL Server database that Docker needs to connect to. To those who may be unaware, no, the M1 chip doesn't support nested virtualisation.
Therein lies my question: how do I establish a connection from Docker through the MacOS host to SQL Server in Windows VM?
Points that I'm aware of:
There is no direct connection between Docker and Windows
Docker has its own subnet assigned by default e.g. 192.168.65.0/24
Parallels uses shared network by default, which places the Windows VM in an invisible subnet e.g. 10.211.55.x
Parallels support bridged network but ideally would like the corporate VPN to just be in the MacOS host
Inside Mac's host file, an entry exists to resolve the private IP of the Windows VM to a hostname e.g. 10.211.55.x windows-11.shared
Docker uses a specific hostname to establish a connection to the MacOS host i.e. host.docker.internal
SQL Server is configured to accept TCP connections through port 1433
Using the connection string Server=windows-11.shared;Database=xxx;User ID=xxx;Password=xxx throws the "Server not found" error because no direct connection
Advice greatly appreciated!
I have two laptops one running Windows 8.1 and other running Windows 7. Both are connected to the same wifi router. I want to bring them on the same network because I want the Windows 7 machine to act as a Server so that I can host my SQL Server database on it.
Which means Windows 7 machine name should appear in list of 'Server Name' combo of SQL Server connection properties dialog box.
If they are connected to same router means they already are on a same network.
Assign unique IP to your laptops from router settings (Typically hosted at http://192.168.0.1/).
Do the ping test from cmd.
Enable TCP/IP Protocol for SQL Server.
You should now be able to connect SQL from remote machine with it's IP.
I installed Oracle 11g Standard Edition on my machine ( Windows 7 X64 ) and configured a listener. While being on the network , when I tried to connect through Jdev 11g , connection was successful. But when I'm off the network , I'm not able to connect to the Database thru Jdev. EM console is not opening too.
Is there any way I can connect to Database while I'm not on the network ?
Your listener has to be configured to listen to your localhost internal interface, 127.0.0.1, for you to be able to connect when not on a network.
If it's only configured with your network adapter's IP address you will only be able to connect while on the network. When you unplug your LAN cable the interface associated with that IP is disabled and no longer reachable, even from within your PC. You will also have problems if your IP is allocated by DHCP, and would need to use a DNS name that follows reallocation; that's why servers usually have fixed IPs.
You can configure the listener to use both addresses if you need to be able to connect locally when off the network, but have other clients connect to your database when you are on the network. Having a DB that others need to access on a machine that isn't always connected would be a bit odd though.