feature telnet server not available in windows 10 [closed] - server

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
In the features of windows 7 we have both telnet client and telnet server. But in windows 10 telnet server is not available, Can anyone please guide on how to install it? And I am also aware that we can use ssh instead of telnet.

Microsoft deprecated Telnet Servers in Windows Server 2012 R2, and subsequently in Windows 10.
Telnet is considered completely insecure these days, because it sends everything across the wire in plain text, so they removed it.
Since you'd need to install a 3rd party Telnet server, you should (instead) consider installing a SSH server. Similar abilities and results, but SSH is generally considered secure.
Perhaps check out this Serverfault question for some suggested SSH servers:
What is a good SSH server to use on Windows?
(Answer from #Ƭᴇcʜιᴇ007 found HERE)

I know I am a tad late to this feed, but I have used the GSW Telnet Server and SSH Server and they have been great. They claim to be the most secure SSH on the market and I have never had any issues with data security at all.
They do have 24/7 support and can help with installation if there are any difficulties.
Hope this helps - Ben

Related

Open port to remote access PostgresSQL on Ubuntu [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I opened a PostgreSQL port by adding a line in /etc/postgresql/10/main/pg_hba.conf
host mydatabase myuser my_ip_adress/32 md5
and then opening the port like this:
sudo ufw allow 5432/tcp
Is this secure enough? Our should I also limit the IP adresses for port 5432 in ufw / iptables?
"Secure enough" depends a lot on your requirements.
I would say that that is good enough for normal purposes. An easy improvement would be to use scram-sha-256 instead of md5 (don't forget to change the password_encryption parameter and set a new password).
If your database contains the secret algorithm that the NSA uses to break TLS encryption, you might want to use a different authentication method like Kerberos that uses central identity management rather than database passwords.

system library:connect:No route to host [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 5 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Improve this question
I have a small sample application which send some data to the server and close the connection afterwards. I ran it on my localhost as server & client and it worked.
When I ran the same code after changing the IP to another host(running Cent OS in VM) as server and my client (Ubuntu), I get the following error from client binary.
client.c : 47 Error connection to remote machine
139915881411416:error:02002071:system library:connect:No route to host:bss_conn.c:246:host=192.168.56.101:6001
139915881411416:error:20073067:BIO routines:CONN_STATE:connect error:bss_conn.c:249:
I am able to ping the remote server from my terminal. Any suggestions or solutions are welcome :) .
Actually the problem was because of firewall running on server(Cent OS). After stopping the firewall using command,
service iptables stop
the client was able to make a connection with the server.
Better Solution (without stopping firewall):
Add your client's IP address in the iptables so that it will allow the client to connect to your server without stopping firewall.
iptables -I INPUT -s <client_ip_address> -j ACCEPT

Strange LAN issues with VPN [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
In my company's physical office, there is no domain controller setup, just a bunch of computers ranging from Windows XP to Windows 10 that are all part of the same workgroup in the same LAN. These computers can access shared folders on other computers in the network by logging with user accounts that exist on those computers. With me so far?
Problem: I've set up a VPN through the router (netgear router with openvpn client), and I can see the shared folders on "Most" computers. I'm using Windows XP Professional, and inside the VPN I can access computers that are Windows XP or newer. I'm getting a local IP address from the router's DHCP and all that seems perfect. But I'm having I'm having problems accessing Windows 2000 computers. I try to log in and receive the error "STATUS_LOGON_FAILURE". I'm typing the correct username and password, and just can't figure out why it's not working.
I'm using Wireshark to analyze the packets and can't really see anything in there that is that much different in the SMB communication between these machines, and I'm not really sure where to start. Since XP machines in the same office behind the same router can access Windows 2000 machines, but I can't through the VPN, it seems the problem might have something to do with that. Any tips on how to trouble-shoot this?
Thanks!
I found the solution. It had to do with this registry setting:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\lmcompatibilitylevel
On all machines in the office, this value was set to 0. If I set mine to 0, I can login fine. Of course, the REAL problem is that 0 seems pretty out-dated and insecure, so now I'll need to review whether all the old machines in the office can support a NTLMv2 so I can update that, but that's a different issue. So this is SOLVED.

Issue on SMTP access via Internet [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
Currently we are implementing to use POP3 / IMAP service for flexibility of mail clients.
We are also overlooking on mobiles to be able to access via internet.
We have successfully configured the POP3 / IMAP service and tested already.
Now, the main issue when connecting to the SMTP server. I am planning to
publicly publish an open STMP relay but with user authentication.
Mail Client (e.g. IMAP) --> Internet --> Firewall ---> Email Server (Relay Host to) --> Microsoft Exchange Online Protection --> External Domain
Right now I was able to test the SMTP service using telnet domain.com 25 it was successfully and having reply from ehlo / helo command.
But via on the internet the command or connection reply only with *************** or unrecognized command.
We have already disable SMPT checking or fixup on firewall equipment still no good.
I am thinking to use the Microsoft Exchange Online Protection as alternative relay agent.
But how do I configure the Microsoft EOP and mail client on this? Or can you recommend alternative solution.
Thank you.
Traveler should be included with your Lotus Domino license.

Remote desktop connection to Raspberry Pi without specifying a port [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have a Raspberry Pi running Debian 7 (Wheezy) connected on "Site A", where the network is managed by a third-party company and where all ports are closed to the Internet (for security reasons). So, there is no way for me to do any port forwarding to VNC, nor SSH or anything else. That means I just can't access it in any way other than locally, on-site.
However, I need to connect to that device on the X Desktop session (graphical interface) to do some maintenance, and I am located in let's say "Site B", which is nearly 300 miles away from site A.
I know you can do such tasks on Windows or x86 Linux computers with TeamViewer (we use it for our other hardware in the same location and it works like a charm), but since the Raspberry Pi is based on an ARM architecture, it isn't supported by TeamViewer yet.
If anyone has ever achieved this, I would be glad to hear how to do it!
Since you have no ssh access, I can safe you from going on site A once.
I would setup a reverse ssh tunnel for ssh and VNC to a computer on the raspberry:
nohup ssh -N -R 3000:localhost:22 you#site-b &
nohup ssh -N -R 3001:localhost:5900 you#site-b &
You might implement some "watchog" which reconnects the tunnels if they should get disconnected for some reason. I assume that a VNC server is already running on the raspberry.
On site B you can now use:
ssh -p 3000 localhost # ssh to raspberry.
or VNC to the raspberry using localhost:3001