Prev: Expansion port splitter cable?
Next: Computereyes(tm) By Digital Vision.
From: ramswell on 7 Apr 2008 02:47
On Apr 6, 11:11 pm, Richard James <rja...(a)invalid.com> wrote:
> On Sun, 06 Apr 2008 21:20:41 -0700, ramswell wrote:
> > Can anyone find the time to call in and test out my BBS?
>
> > mkbbs.dnsalias.org
>
> Hmm maybe a few suggestions.
> I just tried Nmap
> $ nmap -P0 -p23 mkbbs.dnsalias.org
>
> Starting Nmap 4.20 (http://insecure.org) at 2008-04-08 01:59 EST
> Interesting ports on adsl-75-51-91-117.dsl.lsan03.sbcglobal.net
> (75.51.91.117):
> PORT STATE SERVICE
> 23/tcp filtered telnet
>
> Nmap finished: 1 IP address (1 host up) scanned in 12.305 seconds
>
> Which means you telnet port is visible on the Internet but for some
> reason nothing can connect to it. So either your modem is not sending the
> packets to the computer running the telnet server or the telnet server
> itself is not working properly.
>
> It may be possible that you have another software firewall installed
> somewhere that is causing problems. But that firewall would need to be on
> the machine with the telnet server.
>
> can you connect from another machine in your network to that telnet
> server?
>
> Richard James
> --
> sig fail on line -1



Interesting! Haven't tried that method yet. I'll give that a try and
see what happens there.

So what your telling me is that all the ports tested out OK and that
the TELNET is visible from the internet but won't connect? Then it IS
on this side.

Thanks for the update.

Charles
From: Andreas Kohlbach on 7 Apr 2008 20:52
Richard James wrote on 07. April 2008:
>
> On Sun, 06 Apr 2008 21:20:41 -0700, ramswell wrote:
>
>> Can anyone find the time to call in and test out my BBS?
>>
>>
>> mkbbs.dnsalias.org
>
> Hmm maybe a few suggestions.
> I just tried Nmap
> $ nmap -P0 -p23 mkbbs.dnsalias.org
>
> Starting Nmap 4.20 ( http://insecure.org ) at 2008-04-08 01:59 EST
> Interesting ports on adsl-75-51-91-117.dsl.lsan03.sbcglobal.net
> (75.51.91.117):
> PORT STATE SERVICE
> 23/tcp filtered telnet
>
> Nmap finished: 1 IP address (1 host up) scanned in 12.305 seconds
>
> Which means you telnet port is visible on the Internet but for some
> reason nothing can connect to it.

Not exactly "visible". Well it is as it eats the probes.

> So either your modem is not sending the
> packets to the computer running the telnet server or the telnet server
> itself is not working properly.

If the telnet server wouldn't work you'd get a "closed" if the port
wasn't filtered.

> It may be possible that you have another software firewall installed
> somewhere that is causing problems. But that firewall would need to be on
> the machine with the telnet server.

That's possible too that (running Windows) the Windows firewall doesn't
allow the traffic. Here ramswell also had to allow port 23.

I came across a D-Link WLAN router which was also stubborn. No matter
what I told it it always blocked all incoming traffic. A firmware update
helped then.

It would also help to connect the machine in question directly to the DSL
or Cable modem and allow the Windows firewall traffic inbound to port 23.
--
Andreas
My Commodore 64 classic game music page at
http://freenet-homepage.de/ankman/sid.html
From: ramswell on 7 Apr 2008 22:34
On Apr 7, 5:52 pm, Andreas Kohlbach <a...(a)spamfence.net> wrote:
> Richard James wrote on 07. April 2008:
>
>
>
>
>
> > On Sun, 06 Apr 2008 21:20:41 -0700, ramswell wrote:
>
> >> Can anyone find the time to call in and test out my BBS?
>
> >> mkbbs.dnsalias.org
>
> > Hmm maybe a few suggestions.
> > I just tried Nmap
> > $ nmap -P0 -p23 mkbbs.dnsalias.org
>
> > Starting Nmap 4.20 (http://insecure.org) at 2008-04-08 01:59 EST
> > Interesting ports on adsl-75-51-91-117.dsl.lsan03.sbcglobal.net
> > (75.51.91.117):
> > PORT STATE SERVICE
> > 23/tcp filtered telnet
>
> > Nmap finished: 1 IP address (1 host up) scanned in 12.305 seconds
>
> > Which means you telnet port is visible on the Internet but for some
> > reason nothing can connect to it.
>
> Not exactly "visible". Well it is as it eats the probes.
>
> > So either your modem is not sending the
> > packets to the computer running the telnet server or the telnet server
> > itself is not working properly.
>
> If the telnet server wouldn't work you'd get a "closed" if the port
> wasn't filtered.
>
> > It may be possible that you have another software firewall installed
> > somewhere that is causing problems. But that firewall would need to be on
> > the machine with the telnet server.
>
> That's possible too that (running Windows) the Windows firewall doesn't
> allow the traffic. Here ramswell also had to allow port 23.
>
> I came across a D-Link WLAN router which was also stubborn. No matter
> what I told it it always blocked all incoming traffic. A firmware update
> helped then.
>
> It would also help to connect the machine in question directly to the DSL
> or Cable modem and allow the Windows firewall traffic inbound to port 23.
> --
> Andreas
> My Commodore 64 classic game music page athttp://freenet-homepage.de/ankman/sid.html



So is your suggestion to turn off th firewall COMPLETELY on my
daughters computer? that, I won't do as she goes onto a lot of
Japanese and German sites that will do a browser hijack if that
happened.

Charles
From: Klompmeester on 8 Apr 2008 05:49

"ramswell" <shifty_butch(a)hotmail.com> wrote in message
news:6fbda476-2d8a-4858-8199-709662d5b65a(a)p39g2000prm.googlegroups.com...
> On Apr 7, 5:52 pm, Andreas Kohlbach <a...(a)spamfence.net> wrote:
>> Richard James wrote on 07. April 2008:
>>
>>
>>
>>
>>
>> > On Sun, 06 Apr 2008 21:20:41 -0700, ramswell wrote:
>>
>> >> Can anyone find the time to call in and test out my BBS?
>>
>> >> mkbbs.dnsalias.org
>>
>> > Hmm maybe a few suggestions.
>> > I just tried Nmap
>> > $ nmap -P0 -p23 mkbbs.dnsalias.org
>>
>> > Starting Nmap 4.20 (http://insecure.org) at 2008-04-08 01:59 EST
>> > Interesting ports on adsl-75-51-91-117.dsl.lsan03.sbcglobal.net
>> > (75.51.91.117):
>> > PORT STATE SERVICE
>> > 23/tcp filtered telnet
>>
>> > Nmap finished: 1 IP address (1 host up) scanned in 12.305 seconds
>>
>> > Which means you telnet port is visible on the Internet but for some
>> > reason nothing can connect to it.
>>
>> Not exactly "visible". Well it is as it eats the probes.
>>
>> > So either your modem is not sending the
>> > packets to the computer running the telnet server or the telnet server
>> > itself is not working properly.
>>
>> If the telnet server wouldn't work you'd get a "closed" if the port
>> wasn't filtered.
>>
>> > It may be possible that you have another software firewall installed
>> > somewhere that is causing problems. But that firewall would need to be
>> > on
>> > the machine with the telnet server.
>>
>> That's possible too that (running Windows) the Windows firewall doesn't
>> allow the traffic. Here ramswell also had to allow port 23.
>>
>> I came across a D-Link WLAN router which was also stubborn. No matter
>> what I told it it always blocked all incoming traffic. A firmware update
>> helped then.
>>
>> It would also help to connect the machine in question directly to the DSL
>> or Cable modem and allow the Windows firewall traffic inbound to port 23.
>> --
>> Andreas
>> My Commodore 64 classic game music page
>> athttp://freenet-homepage.de/ankman/sid.html
>
>
>
> So is your suggestion to turn off th firewall COMPLETELY on my
> daughters computer? that, I won't do as she goes onto a lot of
> Japanese and German sites that will do a browser hijack if that
> happened.

What sort of Japanese and German sites is she visiting that you know will do
browser hijacks?


From: sta on 8 Apr 2008 06:38
Perhaps, your family should stop using M$IE...
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Expansion port splitter cable?
Next: Computereyes(tm) By Digital Vision.