Timeline for Connect to remote computer behind firewall by using middle man computer
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 8, 2014 at 22:33 | answer | added | Ron Trunk | timeline score: 2 | |
| Jan 8, 2014 at 20:08 | comment | added | Scott |
@techie007 when I say see I mean cannot connect to it. This is because of the firewall not allowing inbound traffic to computer A or C
|
|
| Jan 8, 2014 at 20:07 | comment | added | Scott | @Ron I have access to all computers providing Im on their private networks. I do not have access to Computer C over the public internet. | |
| Jan 8, 2014 at 18:50 | comment | added | Ƭᴇcʜιᴇ007 | What do you mean by "cannot see"? If Computer B cannot communicate with Computer C then Computer C cannot communicate with Computer B. At least not with TCP/IP. | |
| Jan 8, 2014 at 18:34 | history | migrated | from networkengineering.stackexchange.com (revisions) | ||
| Jan 8, 2014 at 18:29 | answer | added | aseaudi | timeline score: 0 | |
| Jan 8, 2014 at 18:20 | comment | added | Ron Trunk | Do you have access to computer C? That is the real "middle man." | |
| Jan 8, 2014 at 17:52 | history | asked | Scott | CC BY-SA 3.0 |