Page 1 of 1

Someone please try this link , let me know if it works

PostPosted: Wed Oct 20, 2010 3:17 am
by robert.h.weinstein

PostPosted: Wed Oct 20, 2010 3:23 am
by alphawave7
yep! 8)

PostPosted: Wed Oct 20, 2010 5:37 am
by bradrossmac
Works for me too

PostPosted: Wed Oct 20, 2010 8:39 am
by utopian
yep getting to a login :)

Thank you for the unit test :-)

PostPosted: Wed Oct 20, 2010 12:56 pm
by robert.h.weinstein
I kept getting a redirect to an internal IP

I entered the aforementioned DNS and got the following rendered in my browser

http://introductiontoobjectivism.subsonic.org then

get the following in my address bar http://192.168.1.64/login.view?

It is an internal ip rather than the external DNS?

I still get the the login screen though.

How strange is that?

Re: Thank you for the unit test :-)

PostPosted: Wed Oct 20, 2010 1:30 pm
by stennie
robert.h.weinstein wrote:I kept getting a redirect to an internal IP

I entered the aforementioned DNS and got the following rendered in my browser

http://introductiontoobjectivism.subsonic.org then

get the following in my address bar http://192.168.1.64/login.view?

It is an internal ip rather than the external DNS?

I still get the the login screen though.

How strange is that?


Not strange at all. If you're accessing it locally, the translation will be made. I am not a networking expert, but I believe your router is most likely translating the address via NAT so as to direct the traffic locally without the bother of having every packet go out to the WAN side and slow everything down.

If anyone wants to jump in and tell me how I probably butchered the explanation, feel free. But the basic jist is -- yeah, it's normal and a good thing.

PostPosted: Wed Oct 20, 2010 6:17 pm
by rwt2777
Yep, I just started my CCNA (Certified Cisco Network Associate) class a couple months back and learned about this.

What happens is the transport layer of TCP/IP recognizes the destination address of what your computer is requesting is local and it routes it directly to the internal IP of the MAC address that matches on your local LAN. The packets never even get packaged for internet travel and go directly to your local subsonic machine/server.

Hope that clarifies things!

PostPosted: Thu Oct 21, 2010 3:23 am
by alphawave7
rwt2777 wrote:Yep, I just started my CCNA (Certified Cisco Network Associate) class a couple months back and learned about this.

What happens is the transport layer of TCP/IP recognizes the destination address of what your computer is requesting is local and it routes it directly to the internal IP of the MAC address that matches on your local LAN. The packets never even get packaged for internet travel and go directly to your local subsonic machine/server.

Hope that clarifies things!


..which would mean TCP only..no IP. ;)

PostPosted: Tue Jan 18, 2011 4:44 pm
by kpaul
alphawave7 wrote:
rwt2777 wrote:Yep, I just started my CCNA (Certified Cisco Network Associate) class a couple months back and learned about this.

What happens is the transport layer of TCP/IP recognizes the destination address of what your computer is requesting is local and it routes it directly to the internal IP of the MAC address that matches on your local LAN. The packets never even get packaged for internet travel and go directly to your local subsonic machine/server.

Hope that clarifies things!


..which would mean TCP only..no IP. ;)
,

That's some real end-to-end stuff. I took Firebrand Training's CCNAcourse. took me 5 days, and I tell you, the section on TCP/IP got me by the neck. Thanks for the comment, it's a good reminder. That's a first hand explanation on the fundamentals of how computers communicate with each other in a network. Nice one!