You'll need to contact someone who has physical access to the server and get them to fix it for you. [by TrevorH]
I maintain a server with Window 2008R2, SQL Server 2008R2, Bitwise SSH server and IIS7.
The applications that use the SQL server are either websites located on the same machine or use a SSH tunnel to connect to it.
Within the windows firewall I have the remote desktop login bound to a series of IP addresses which are allowed to get in.
I'm trying to allow access to certain ports on the server, via only one of the server IP addresses.
So for example if the server has two IP addresses:
I only want for example ports 25, 26 to be accessible via 18.104.22.168.
I'm trying to connect remotely from my Windows 8 client to manage my Hyper-V Server 2012.
A colleague of mine added several IP addresses to a server, but these IPs are not appearing in the list to use with bindings.
This goes for IIS7 web sites and IIS6 FTP sites.
We found this KB article, but I don't have the offending patch installed: http://support.microsoft.com/kb/2551090/en-us
I don't think the server was restarted after the IPs were added as it is a live production server, but
I currently don't have physical access to the router that my remote server is connected to. This router, from my server's perspective, should be accessible is 192.168.1.1.
We have ran into this error, trying to connect to WSUS server:
Can't connect to SQL server may not be running
Please verify that SQL server is running and configured correctly on
the server. Contact your network administrator if the problem
The only thing that changed was the name of the server. It is Windows 2008 R2 x64 Enterprise edition.
I am using ssh as a SOCKS server by running this command on the server:
ssh -f2qTnND *:1080 root@localhost
There is one problem: anybody can connect to the server and use it's internet connection.
To use iptables to filter access to the server, but I connect to the server from various non-statically allocated IP addresses so I would have to edit very frequently those filters which c
(Sorry if this question has been answered before, but I'm really in a hurry before our server gets null routed again and I want it to work first time.)
Our service provider has given us 4 IP addresses from 69.x.x.194 to 69.x.x.198.
How do I configure my CentOS 5.6 box to use these extra IP addresses so we can still access the server when it gets kicked down by attackers again?
We are connecting a server to our network via VPN (Client-Gateway).
Is it possible to maintain the external IP address while the VPN is connected?