• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

HTTP IP Syntax

EmosOohay

Member
How is the IP address of a computer attached to a gateway specified.

For example if the gateway is 150.98.30.170 and the attached computer, named Felix, is 192.168.0.9 how is the IP address of Felix specified?

I've tried http://150.98.30.170/Felix/, http://150.98.30.170:Felix/ and others. All my guesses were incorrect.

I'd like to be able to address Felix over the internet from work.

Thanks for the help!
 
Thanks for the links, I'm studying some of the articles linked from the IPMonster page now.

Unfortunately the two pages don't answer my question, unless there is no answer because the IP syntax does not address this issue.
 
Can't be done. The 192.168.x.x address range is used because it's defined as a local and unroutable address so it's invalid on the internet. The way your Nat works is by tracking outgoing requests from your computer and using them to map the replies back to the right computer. If you want to be able to hit the computer from the outside you'll need to setup port maping which is really just a stactic association that anything coming in on that port goes to that computer.
 
Your example confuses me because of the tongue stuff. Could you retype it without the comedy?

I'll study up on port forwarding and maping though!


Thanks!
 
Originally posted by: EmosOohay
Your example confuses me because of the tongue stuff. Could you retype it without the comedy?

I'll study up on port forwarding and maping though!


Thanks!

I didn't mean for it to be in there. It was a parsing issue. It should look fine now. 🙂
 
Originally posted by: EmosOohay
FYI: Here's what I was looking for: Remote Desktop ROCKS! located at http://blogs.msdn.com/trishm/archive/2003/10/28/57566.aspx 😀
If you look at the Note 2 at page I direct you to, it suggested the exact same solution.

Whether you would like to use Windows Remoter Desktop or VNC it up to you. There is con and pros to either. VNC has smaller foot print, takes fewer resources, and is less intrusive to system then Remote Desktop. Remote Desktop is better in case of longer period more complex interaction.

The solution however is the same. I.e. installing it on each LAN?s Computer and assigning different ports. The ports are then use as the ID for each computer (Not http syntax).

:sun:
 
Back
Top