On (22/07/04 07:11), Stephen R Marenka wrote: > On Thu, Jul 22, 2004 at 01:31:13AM +0100, Clive Menzies wrote: > > On (20/07/04 10:31), Stephen R Marenka wrote: > > > > nc -l -p 2080 -e /bin/sh > > > on tty2 or whatever suits. > > Thanks Stephen > > > > I used the above on tty2, which from the man page I understand means > > that this machine will listen for shell commands on port 2080. However, > > when try to contact this host from my workstation using: > > > > [EMAIL PROTECTED]:~$ nc -t Homer 2080 > > Homer.PRIORYROAD [192.168.1.21] 2080 (?) : No route to host > > Either the machine isn't really on the network or you have a routing > problem. I think you're right 'cos I can't ping 192.168.1.21 (100% packet loss)
I guess the network doesn't get configured 'til reboot - which it won't and that's why I need to get to the log output from another machine ;( I think I'll try to repeat the install and leave it to DHCP rather than configuring the network manually and see if that gives me a useable network connection before reboot. Many thanks for the help Regards Clive > > Does ifconfig show you have a configured network on Homer? > > What about route -n? It's good to see a default gateway. > > -t isn't necessary, I'm not sure what effect it would have. > > Can you ping 192.168.1.21? Can Homer wget some random web page? -- http://www.clivemenzies.co.uk strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
