Author Topic: Portforwarding on an old Airport router  (Read 681 times)

I've never been able to port forward on my macintosh computer since when I open up Airport Utility it cannot detect the device no matter how close it is to my device. I cannot connect to it with an ethernet cable since I lost the forgeter. I need to connect wirelessly but for who the forget knows why, it doesn't work.

Can somebody please help? I've had this problem for 2 years.

I use the old Airport Base Station and I do not currently have money to buy the Airport Extreme.

I also currently have the same problem. I ordered an Ethernet Cable, but using Airport Utility to try to connect to a wireless device didn't do anything. :P I'm going to try to mess with some settings in a little bit here.

How many ports do I forward?

28000 through 28032?

Guys. I forwarded 28000 and it didn't work. I set my private IP address as 10.0.1.1 which is my IP for router and it still doesn't work. I let my firewall allow blockland and it still doesn't work.

WHAT DO I DO. Why the hell is it so difficult to host a blockland server.

Start port 28000
End Port 28030, Thats what works for me.

Whenever I try to port forward on my mac, I get this. Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request POST -linkremoved-
Reason: Error reading from remote server


For me, portforwarding works, even on a very old router. My configuration looks like like this:

Quote from: Router Portforwarding Section
BL1
  IP: 192.168.1.250
  Port: 28000 (TCP)
BL2
  IP: 192.168.1.250
  Port: 28000 (UDP)
Web
  IP: 192.168.1.2
  Port: 80 (TCP)
SSH
  IP: 192.168.1.2
  Port: 22 (TCP)
PEEK
  IP: 192.168.1.248
  Port: 28001 (TCP)
PEEK2
  IP: 192.168.1.248
  Port: 28001 (UDP)

This probably won't help you so much, but atleast this works for me.

noedit: meh. stupid reply.

triplepost: Maybe it's because you are portforwarding ONLY TCP. On some older routers, TCP+UDP works.