local lan

johnh10000 · 05-02-2009, 06:21 AM

Hi gang

I have a very simple to box lan on a cross over cable, we are waiting for our local cable company to provide a router!

Ubuntu intripid serving and a xp pro box

--
Sor far got ping to work and ftp to work anon wise.

Got ssh and telnet to work at server end, xp end it connection refused, help, how do I let the lan connect?

Also working on server box, but apache2 wont let work on xp

any ideas

{BBI}Nexus{BBI} · 05-02-2009, 08:27 AM

Have you opened the required ports on the firewall (serverside)?

johnh10000 · 05-02-2009, 01:39 PM

Quote:

Originally Posted by {BBI}Nexus{BBI}

Have you opened the required ports on the firewall (serverside)?

not sure if I have ? How do I do that please?

baig · 05-02-2009, 01:43 PM

If you are not sure what to do with your firewall configurations.. Answer simple question and get a professional firewall configuration.

http://easyfwgen.morizot.net/gen/

cheers!!

johnh10000 · 05-02-2009, 03:19 PM

Quote:

Originally Posted by baig

If you are not sure what to do with your firewall configurations.. Answer simple question and get a professional firewall configuration.

http://easyfwgen.morizot.net/gen/

cheers!!

Cheers again

for that, just done that, will report back soon, and let ya no if it worked!

johnh10000 · 05-02-2009, 04:43 PM

Quote:

Originally Posted by baig

If you are not sure what to do with your firewall configurations.. Answer simple question and get a professional firewall configuration.

http://easyfwgen.morizot.net/gen/

cheers!!

Making progress, the web sorry intranet is visable, now but the net on the server wasn´t

think that was my fault. However the telnet says ¨could not open connection¨

any ideas?

johnh10000 · 05-05-2009, 01:27 AM

just about there now, samba,http, ftp, works just a few problems with telnet (connection refused)

found lokkit was my best choice, got from multiverse repositry, tnx for you help.

any ideas on my connection refusd?

chrism01 · 05-05-2009, 01:39 AM

Well, telnet is usually disabled by default on Linux because its a plain text (not encrypted ) protocol, so very unsafe.
Recommend you use ssh if possible, the usual solution.
If you really HAVE to use it, its usually controlled from the xinetd daemon, see /etc/xinetd.d dir.
Should have its own cfg file in there, set disable = no.