Computer help needed!

[Legacy777]

yup....there's either a router issue, or they have you setup behind some sort of firewall.

The external IP showing up on the board is
129.71.34.17

If this issue just happened, they either just implemented a firewall, or their router pooped out.

If you just talked to the helpdesk dude, you might want to have him check with the higher ups, or talk to one of the network/higher up people directly.

[georryan]

That's an internal address. The public can't see that. Hmm, that might be why ftp isn't working for you, either. Did your school make some changes recently? Did they say?

But you should still be able to trace to a site, unless they are blocking the pings, which some administrators do. Your still getting onto the internet right???

[BAC5.2]

Yep, I'm in my dorm room right now. The FTP works now (it was a setting issue, I was in Passive mode, and I needed to not be. Now I'm getting just about 1MBPS upload speeds).

IM service has been out since thursday.

It's kind of frustrating, not being able to get on IM.

[vrg3]

That's weird... normally behind your type of firewall you're supposed to use passive mode FTP. I guess they have some kind of intelligence built in specifically for FTP, and also limit downstream bandwidth on locally-initiated TCP connections?

Can you get on IM with Quick Buddy? I forget what port it uses by default, but it might be different from the port normally used by native IM clients (the protocol is different). http://toc.oscar.aol.com/tic.html

[BAC5.2]

Yea, I can use AIM-Express just fine, if that's what you mean.

I don't know what the deal is with the FTP. Passive mode was giving me 4kbps and decline from there to nothing. Every upload would time-out. No Passive mode, and I get almost 1MBPS.

At home, on our cable line, I think I was using Passive mode (it's default with SmartFTP, the FTP I use) and was getting close to the same speeds.

Wild, huh?

[vrg3]

Wild indeed. It's clear something's monkeying with your packets; you have a private IP address, the middleman is fixing FTP stuff, apparently throttling certain types of connections, and not even trying to deal with the ICMP packets that traceroute uses.

Try changing the port that AIM uses. I think it's somewhere in the settings, in the same place where you specify information about proxy servers. The default is 5190, but other ports will work. Try 80, maybe.

[BAC5.2]

WOAH! Port 80 works

SWEET!

That's friggin weird! It worked BEFORE, but it stopped. AWESOME!

Vikash, once again, your a God.

[vrg3]

Cool.

I think someone consciously made a decision to cut your campus off from AIM.

If you play with the port settings in your peer-to-peer software you might be able to get them to work.

[BAC5.2]

What ports should I try? 80 again?

[georryan]

isn't port 80 the same port that web browsers use???

You may want to change it to some other port number.

[vrg3]

Phil - Sure, you can try 80... or maybe others. I dunno. Try 81, 8000, and 21 maybe. Remember to turn on the setting saying you're firewalled and can't accept incoming connections, too. I'm just making general suggestions; it's possible that they don't make any sense when applied to whatever particular P2P applications you're using.

Actually, now that I think about it, Limewire uses Gnutella as its underlying transport, doesn't it? So you can't set the server-side port. And since you can't accept connections either, you really can't make any useful tweaks to Limewire at all.

I don't know anything about Shareaza though.

Ryan - Yes, port 80 is the port used for HTTP. That's why I suggested it -- it was likely that the packet mangler wasn't going to mess too much with it.

Remember, we're talking about the port on the server, not the client, so there's no worry about conflicts with web browsers or anything. Locally, his computer's picking whatever random port it wants. Then the NAT system is reassigning it anyway.

[BAC5.2]

The FTP uses port 21, btw.

[georryan]

Ryan - Yes, port 80 is the port used for HTTP. That's why I suggested it -- it was likely that the packet mangler wasn't going to mess too much with it.

Remember, we're talking about the port on the server, not the client, so there's no worry about conflicts with web browsers or anything. Locally, his computer's picking whatever random port it wants. Then the NAT system is reassigning it anyway.

Oh, right.

I was on a different page for a sec.

[vrg3]

Phil - Yeah, that's why I thought you might try it. It might cause problems, though, since your FTP packets are being modified.

[Tleg93]

I just noticed this post. While I was working at Kellogg's my proxy address and port assign was changed by a virus or something. Initially, I asked the techs there what was up and they had no clue. I went in and changed the proxy to the correct name and reassigned the port to port 80 and voila, it fixed it. I don't know if you access the internet through a proxy server but if you do then maybe you should check out your internet settings under tools - connections and verify that it's the same as the proxy your school has assigned. A lot of times this seems to be the trouble with proxys so give it a try.

[JasonGrahn]

format c:\

[vrg3]

You mean mke2fs /dev/hda1 ?

[BAC5.2]

Vikash - Check g-mail.

[Legacy777]

fdisk that biatch

[totech]

Hmm.... Packeteer? Sounds about right