Brad, I had the same problem last week, and I spent 3 hours with cox cycling my modem and doing all kinds of useless c**p. All COX is interested in is whether or not you can browse the internet. I talked to 3 different guys and they all said they didn't know why I couldn't telnet / ssh / ftp to my machine from a remote location. But they said COX doesn't support that so they weren't going to help me with it. I think I might move to a business account. For now though, I am running ssh on an open port so I can still get to it remotely. BUT, here is how you tell that COX is blocking your stuff. "nmap -P0 ip-address" this will show you a machine with your address but with ports open and filtered that you probably don't have open or filtered on your machine. I had a friend of mine from work nmap my computer and he said it was probably one of COX's routers filtering. By the way you have to nmap it from a computer not on the cox network or it will show you the correct info instead of what I said earlier. Whether COX is admitting it or not, they are filtering a lot of regular ports. Once you nmap you will see what I am talking about.
Hope this helps, Boyd ----- Original Message ----- From: "Brad Bendily" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, August 21, 2002 9:53 AM Subject: Re: [brlug-general] Cox.Net & SSH > > To divert the conversation back to the original subject. > I'm not able to ssh or ftp to my home, which is cox.net, from > SLU at least. Haven't tried it from any where else. But I was > able to move my ssh service to another port and I can connect with > no problems. Same goes for FTP. > > I "chatted" with a Cox tech support rep last night and he gave me a > list of ports they block and 22 and 21 were not in the list. But I > told him I couldn't access services on those ports. He was going to > let someone in the BR TOC know about it. Perhaps someone made a > configuration change that broke port 22 and 21. > > I'm also still having the intermittent connectivity problems. > So they're suppose to look into that too. In the mean time I'll > be testing my cabling to rule out that as a problem. > > -- > Brad Bendily - CNA > > > > _______________________________________________ > General mailing list > [email protected] > http://brlug.net/mailman/listinfo/general_brlug.net >
