We have been using a program called knock.exe successfully under Windows XP to knock on some set of ports which will then allow a connection to be established via ssh on another port to a remote machine. This program worked fine under Windows XP, but under Windows 7 it takes a lot longer to run (gives no error messages) and I am unable to connect to the remote machine.
If i run knock.exe inside a VM not running Windows 7 then connect using SSH from the Windows 7 machine, then it works.
Note that when running the port knocking application from Windows 7, the events get through to the remote machine because there is logging with the ip address of the local machine on the remote machine running knockd (linux).
I have also tried using knock7 from sourceforge with no success.
I have tried many other variations such as setting compatibility mode, and other port knocking applications with no success.
It seems like this is a change in the Windows 7 behaviour (possibly introduced in Vista) from the Windows XP behaviour.
It would be better to not have to run a VM just to do port knocking.
Any suggestions would be much appreciated.
Thanks!
use cygwin version of knock.exe
Related
I am trying to run commands on the cmd prompt of my windows xp mode virtual machine from my main computer which is in windows 7. I've tried to look at the name of the windows xp mode computer which is virtualXP-63912, so i tried : "psexec \\virtualXP-63912 cmd" but it doesn't work. Any ideas of how I can get this to work?
As seen here, you need to change your VM from 'NAT' mode, which allows for web access but no local network connectivity (which is what you need to be able to psexec or run remote powershell commands on your XP mode VM, and also to be able to access the \computername\admin$ share, which is what PSExec uses for remoting) to NIC mode, which will bridge your VM to the network, and give it a local routable IP address.
In short, open the Windows XP Mode console, select your XP Mode Vm and go to settings, then change the network setting to bridged, as discussed in this post from Microsoft on the issue.
Finally, if I may suggest it, move off of XP Mode. It's not supported well these days and the new replacement, Hyper-V for Windows 8.0 and above is built-in to the desktop OS and is much, much more feature filled. You can copy and paste from your desktop into a VM, and run machines with Linux, even OSX on your Windows machine.
As I know, I can connect to remote Windows server through SSH from Linux and use Powershell. But how I can connect without ssh from linux? Maybe exists native tools?
If you wanted a remote desktop session, you could use the rdesktop package:
Description: RDP client for Windows NT/2000 Terminal Server
rdesktop is an open source client for Windows NT/2000 Terminal Server, capable
of natively speaking its Remote Desktop Protocol (RDP) in order to present
the user's NT/2000 desktop. Unlike Citrix ICA, no server extensions are
required.
I'm unaware of any other native Windows protocols similar in spirit to ssh.
I guess you could install a VNC daemon on your Windows system so you could use VNC clients on your Linux boxes. Or you could install (well, no, please don't) a Windows telnet daemon, and use telnet to connect. Or you could install Citrix on your Windows server and use the Linux Citrix client. (Not a solution I enjoyed using in the past. I'd recommend sticking with ssh or VNC instead.)
If you want to get a shell you can try winexe
it works quite well on fedora
I have written a C application to run on a small wireless network (linksys router). The application uses named pipes. When the server is a Win 7 machine and the client is a XP (Pro, SP3) machine the named pipes connection works fine and the app runs perfectly. However, when I swap roles and make the server the XP machine and the client the Win 7 machine, the pipe fails.
I have tried turning off the firewall on the XP machine and that doesn't solve the problem.
File and print sharing between the two machines works fine.
Any suggestions would be most gratefully accepted.
I am running Ubuntu 10.10 and also Windows 7 under vmWare Workstation within Ubuntu.
My internet connection in vmWare is shared from the host as 'NAT'
I am using XAMPP on Ubuntu for developing sites. I use http://localhost/mysite to open the site under development in Ubuntu.
I wanted to use a similar command to open these sites in the Windows 7 installation under vmWare.
While browsing some of the topics I came to know that it is possible by using some IP of 'NAT'.
I am totally new to Linux and vmWare both. Just migrated to Linux from Windows and need help understanding it in detail.
Kindly help me with the process of How to access these sites in vmWare.
Please help.
VMWare's installer should set up a new network interface on your Ubuntu system, check ifconfig -a to find its IP address.
Make sure your webserver is listening on either 0.0.0.0 OR (127.0.0.1 AND the vmware-interface IP address).
From the Windows system, try typing in http://<vmware-interface-ip>/mysite. Hopefully it'll go. You can check the windows networking control panels to see what the gateway address is, it'll probably match.
I hope this gets it going for you.
I need a virtual server for web development, it'll host Apache+Postgres+Ruby+something else.
What's the most effective software to run such a server? (ie with least virtualization overhead)
Is there a way to run Linux as as service?
I use VirtualBox at the moment, but it's inconvenient in some ways, such as it needs an emulator window open which also captures keyboard input when alttabbed into.
(Also, coLinux hangs at boot on my machine, so it's probably not an option)
Check out the features of VMWare Server. It's free, you just have to register.
I've never found VMware to be much of a performance hog unless running 3+ virtual machines.
The latest free server version (VMware Server 2) runs as a service IIRC, so you can set up your dev server to start up and shut down when your PC does, and you can either log on to the VM's console through the web interface, or create a shortcut on your desktop so it's fairly non-obtrusive.
There is a very convenient utility that hides VirtualBox from the foreground completely: vboxctrl. With vboxctrl you can run a Linux server on your Windows machine, make it automatically go to sleep when Windows shuts down or hibernates; then use any SSH client to log in to the server. Or you can use Xming to open graphical windows from the Linux server; I've worked quite a lot of time in GVim open through Xming.
If anyone needs more details, leave a comment, I may write an article about this.