Server won't let traffic in

[OR83]

I called the ISP and they said they don't block any ports

[The Cog]

oscar080483.no-ip.biz resolves to 192.168.1.2 which is a reserved address, not reachable over the internet.
First, you need to change the DNS entry to give your publicly visible address, not your private internal address. You probably have to configure your router to make the dyndns entries as your server doesn't even know your public address.

Beyond that, please answer the questions we have posted.

[OR83]

hmm that's weird 192.168.1.2 is what linksys told me to use they said to use anything from .2 and below .100 my IP before .2 was .109

[OR83]

I called my ISP yesterday and they told me to call linksys and they said to use that. are you suggesting I go back to .109?

[CharlesA]

hmm that's weird 192.168.1.2 is what linksys told me to use they said to use anything from .2 and below .100 my IP before .2 was .109

They told you to use that for your DNS information?

You should have just let your router update no-ip.biz's information. It should use your external IP.

[The Cog]

I called my ISP yesterday and they told me to call linksys and they said to use that. are you suggesting I go back to .109?

I don't understand that question.

To explain, 192.168.1.* is a range of addresses for private network use. Your ISP will allocate a public address to your router when it connects, and the router performs translation between the two. Since the router translates all 192.168.1.* addresses to the single public address, incoming connections need a port-forwarding entry configured to tell the router which private address to forward the incoming call to.

Once the DNS entry is giving the public address, you will not be able to connect to your server by name from inside your private network. This is because address translation doesn't allow for both addresses being on the same side of the router. You will need to test from a different public address on the internet.

[CharlesA]

+1 to The Cog.

Once you get the DNS entry sorted out, you should be good to go if your ISP isn't blocking ports.

[OR83]

I'm going to have to reset everything then.

[lisati]

I'm going to have to reset everything then.

Before you do, you might want to check to see if your router has an option to automatically update the DNS information at no-ip. On my current router (one by Thomson provided by my ISP) the relevant option is found on the Toolbox->Dynamic DNS menu item.

[OR83]

it has it only for DynDNS and TZO not for no-ip. had my modem and router reset i got and ip of 192.168.1.100 on the server