For x, y, and z reasons, I have a desktop PC without a monitor. The desktop PC was set up as a server on my home network with a static ip address of 10.1.10.5 set in windows server 2012 r2, and I could remote access it via any of my PC's. I am basically trying to set this up again on a different network, but without actually accessing the computer itself with it's own monitor ect.
I was hoping it would be as simple as pluging it in, the router/modem combo would pick up the server and it's ip address of 10.1.10.5, and I could connect via remote desktop connection from a pc on the same network.
I can see the device has connected to the router with the IP address of 10.1.10.5, but I have not been able connect to it via remote desktop connection. It is also not displaying the computers proper name, it just says "STATIC IP ADDRESS" beside the IP and mac address in the router.
I have a feeling that there is something blocking me on the windows side. On the network it was connected to before, it had all firewall permissions and network discovery turned on. I assumed it would just apply to the new network.
The router/modem combo is a: Cisco DPC3825, basically the ones that Shaw give you in Canada.
Any thoughts, is this even possible?
I'm going to guess that because the desktop hasn't been logged into on the new network, it's not going to configure it as a private network, meaning the firewall and network discovery rules won't be enabled, meaning remote desktop connect won't be allowed from other devices.
!
It's more likely the new network is using a different subnet, so network access isn't possible. Verify the subnet used by the new network and assign a static IP from that range instead.
Use teamviewer. Its so eazy that a monkey can do it and you don't need to worry about port forwarding and opening up ports. It also has access outside of your network if you can remember the ID, file transfer with hidden file attributes, and VPN.
I'm not very network savvy, but when I was a university student I had to work on a computer remotely. It had proprietary software on it and it was on a network that was only in one building on campus, and I also had issues with remote desktop connection if I wasn't on that network. I was however able to ssh through a vpn into it and run my codes from home. If I needed to transfer files I would just use sftp. I'm sorry if my jargon is off, I never bothered to learn much about networks and it's been a while since I've done this. If you can do whatever you need to do through the terminal/command line and file transfers this may be just as good as a remote desktop connection. If you need to do anything graphical this method won't work.