I was wondering how some people is able to hide their IP when they connect remotely to a server for example. I'm connecting frequently to a linux server and I can see that when using the $who command, it shows from where is everyone connecting to the server, but sometimes it doesn't tell the IP nor the domain or anything, and somebody told me that is because he is hiding his ip using Tor or something similar. My question is: how can I hide my IP when I use a terminal emulator such as PuTTY so that the server doesn't knows my IP?
Connecting through Tor or some other mechanism to hide your true IP has nothing to do with why the who command doesn't show the IP or hostname. Even if connected to an SSH server over Tor, it would show the Tor exit IP rather than nothing.
It may be like Pekka, said, they are connected locally, or another possibility is that their connection timed out and who still shows the login but they aren't actually connected.
If you want to run Putty over Tor to "hide" your IP from the server, just run Tor locally and configure Putty to use Tor as a SOCKS proxy.
You could also run ProxyChains to use Tor or other SOCKS proxies and then run either proxychains putty or proxychains ssh user#host.org to connect through the proxy which will prevent the server from seeing your actual IP.
Configure PuTTY to use Tor
Related
I have a bit of a bizarre problem. I have a Hyper-V VM and I cannot connect to it via IP address on the host computer.
I intend to use it as an SQL server to host a database for a website while I test it, and the first step I can see in this endeavour is to make sure the IP addresses work externally.
Other PCs on the LAN appear to be able to connect just fine via the IP address on Remote Desktop. I cannot do so. I also cannot connect through SQL Management Studio (named pipes or TCP/IP). Although named pipes gives an error relating to being denied access as opposed to IPs which are just not found.
I have tried pinging both ways:
VM => Host : Always gives a "Destination Host Unreachable" error
Host => VM: Always gives a "Request Timed Out" error
As for netstat -a -n, I can see that the VM is listening to 3389 (default Hyper V port, which makes sense).
Regarding Firewalls, all have been turned off on all machines. I can tell that the firewall is not the issue.
If you need any more information to help me to diagnose and treat the problem, please ask me as I would like to get this sorted as quickly as possible.
Thanks a lot in advance.
Which windows server version do you use?
Windows Server 2016 blocks insecure RDP connections (https://support.microsoft.com/en-us/help/4295591/credssp-encryption-oracle-remediation-error-when-to-rdp-to-azure-vm).
Since RDP uses CredSSP you have to install the current Windows Patches.
Do you can ping the DNS server by IP address from your VM?
Is ICMP (ICMP = the thing you need for ping) on your host enabled?
Here is a Checklist for ICMP:
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc749323(v=ws.10)
Solved,
Just switched to another physical computer and it was fine.
I have a computer connected to my workplace AD domain where through this connection it has access to the internet and also can connect to a server located on that domain e.g 150.130.xxx.xxx. I wonder how I can keep the connection to the server whilst disabling internet connection so that this computer can connect to the server but not the internet. Any advice?
I found a way by changing the IP settings from "obtain an IP address automatically" to "use the following IP address" and giving it the actual IP address of my machine, then leaving the default gateway and preferred DNS server empty.
Another solution is to simply do route -f in cmd after you've connected to the network. This will prevent internet traffic from being sent to your router. This might be a little simpler than what youre doing - it essentially does the same thing, but all in one convienent little command.
My web server is running on localhost (127.0.0.1:8800) and I would like to send HTTP posts from another machine to that server.
Does anyone know how I will be able to access the server from the outside? (I did a SSL port forwarding from the external address to localhost, but it is a kind of hack and some aspects do not working properly, e.g. web socket does not detect traffic that's been forwarded)
127.0.0.1 is the loopback address of your network card. Only your computer can access that. 127.0.0.1 on any other computer will be that other computer.
You will have to run your server on your internal ip-address (if you're doing this in an internal network). It will probably look something like 192.168.0.x. If you're instead connecting to the computer using the internet you will of course have to bind the server to the external ip-address.
You can find your internal ip-address on Windows by opening cmd.exe and typing ipconfig. On OSX or Linux/BSD you run ifconfig in a terminal.
i am on a Windows machine and need to connect to an application on a Unix box under a certain port.
i've been told it's open but i'm still having difficulties getting in, is there anything in can do on my end to debug this? how can i check if the port of the Unix server is really open from my IP address?
You can use Telnet.
E.g. telnet example.com 80 to check if the server at example.com accepts connections on port 80.
I got access via SSH (root access) to a Machine that's inside a network at my client's office.
I'm programming in my computer a PHP application that needs to integrate to LDAP. The LDAP server is in another server at my client's network and not accesible from outside, however I can perfectly access it via the server I can connect to via SSH.
My question is: IS there anyway I can make a tunnel and setup a port in my computer to get the traffic forwarded to the LDAP server using my SSH connection to one of the computers on the network?
Thanks!!!!
Yes, ssh has a "-L" option to create a tunnel. That option takes 3 parameters, separated by colons (:). Local listen port, remote host, remote port.
ssh -L 9999:ldapserver:389 user#otherhost
Where 9999 is the local port that the tunnel will be created on. The ldapserver:389 bit tells it where to connect to on the other side.
Then, tell your application to connect to localhost:9999 (or whatever port you choose) and it will be tunneled across.