OK...so I have the No-IP DUC running on my server...and I go to my No-IP....and it goes to my router setup. I definitely have the ports forwarded right ("Virtual servers" sending ports 80 and 21 to 192.168.2.53). It could just be my router freaking out when it sees me doing an outbound connection back to itself and assuming i want to configure it.
Did you try a different port besides 80? You're ISP might be blocking it.
Topher has the same ISP, I think he's running on port 80. But if they were blocking it nobody would be able to get in. And does everybody else get my router setup?
EDIT:
80
HTTP
Stealth There is NO EVIDENCE WHATSOEVER that a port (or even any computer) exists at this IP address!
Nightie, in the no-ip duc program. make sure your host has the check mark, may sound stupid but that is what was giving me problems, I didnt know the smily face need a check mark
UPDATE: ftp is wierd. last night, i was able to locally ftp. before, it said "connection closed by remote host" and now (after reboot) it connects and says that.
Comments
-Q
Always knew my router was a piece of crap that can't handle a server.
Topher has the same ISP, I think he's running on port 80. But if they were blocking it nobody would be able to get in. And does everybody else get my router setup?
EDIT:
80
HTTP
Stealth There is NO EVIDENCE WHATSOEVER that a port (or even any computer) exists at this IP address!
Nightie, in the no-ip duc program. make sure your host has the check mark, may sound stupid but that is what was giving me problems, I didnt know the smily face need a check mark
EDIT 2: nvm about ssh, now only ftp is the problem.
also, someone try doing an anonymous FTP.
-Q