I know the cox network engineers for Baton Rouge and they said they would never block 22 (all bets are off on other ports). Currently they are not blocking any ports in New Orleans and I suspect it is the same in Baton Rouge.
Did you move your ftp and ssh to ports above 1024? If so, I suspect you have a problem with your firewall (I'm assuming you're doing some firewalling). Your cabling won't have anything to do with getting to a particular port. It's also possible that SLU is blocking you for some reason outbound. See if you can get a buddy to test a connection to you from somewhere other than SLU On Wed, Aug 21, 2002 at 09:53:28AM -0500, Brad Bendily wrote: > > 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 -- Scott Harney<[EMAIL PROTECTED]>
