Hi, On Tuesday 05 June 2001 20:29, you wrote:
Hi Mike, thanks for the reply. I have also tried to config it with yast an the same thing happens. but since I have sent out that 1st message I have discovered that if I telnet into the box (or ftp for that matter) from outside my lan it lets me connection then I try to connect to the box from the lan side on a windows workstation an it lets me in after connecting from outside the lan. also it seems to take a while for the connection to come up. I get this same behavior at home an just never sent out a message to the list. I have to telnet in from outside my lan at home before It will let me do so from inside the lan. Just wierd that its like this.
Now that is weird. Let me see if I understand this. If you are local, you can't telnet into the box unless you telnet in from outside first. Right? This sounds like some sort of host problem or perhaps a route problem that is resolved when an outside connection is made. But that really doesn't made sense either because that would give the connection an outside ip address. Maybe before you connect from outside, you can check to make sure that inetd is running. I just thought of something else to check. Cables and network cards. Perhaps one isn't working quite right. Although how you would check something like this is way out of my league. Mike -- Powered by SuSE 7.1, Kernel 2.4.4 KDE2.1.1 For a great linux portal try http://www.freezer-burn.org Jack Malone jack@malone.tyler.com http://www.ballistic.com/~jemalone Luke 4:18-19 "The Spirit of the Lord is on me, because he has anointed me to preach good news to the poor. He has sent me to proclaim freedom for the prisoners and recovery of sight for the blind, to release the oppressed, to proclaim the year of the Lord's favor." (NIV)