-
Content Count
14,251 -
Joined
-
Last visited
-
Days Won
56
Content Type
Profiles
Forums
Gallery
Everything posted by ssh
-
I wear them out for more than school. I like having the toes protected anywhere witha shit load of people, drunks, kids, or where I may find a desire to use my feet for more than walking. Honestly my top three pieces of footwear are flipflops, my combat boots, and steel toed boots. I refuse Timberlands after having three pairs losing stitches in under 6 months. J And here I am essentially walking around in socks: Most comfortable "shoes" I've ever worn.
-
Why would you need a modem for this Enable remote access....and pm me your ip..... How would you connect from outside the local network? Unless the router is setup for port forwarding or using a reverse connection. UDP.. ...requires no handshakes.. excluding port 0 That doesn't make any sense to me. The Remote Desktop Protocol: UDP Transport Extension Protocol has two distinct phases of operation. The initial phase, UDP Connection Initialization (section 1.3.2.1), occurs when a UDP connection is initialized between the terminal client and the terminal server. Data pertaining to the connection is exchanged and the UDP connection is set up. Once this phase is completed successfully, the protocol enters the UDP Data Transfer (section 1.3.2.2) phase, where Coded Packets are exchanged. The protocol can operate in one of two modes. The operational mode is determined during the UDP Connection Initialization phase. These modes are as follows: RDP-UDP-R or "Reliable" Mode: In this mode, the endpoint retransmits datagrams that have been lost by the underlying network fabric. RDP-UDP-L or "Best-Efforts" Mode: In this mode, the reliable delivery of datagrams is not guaranteed, and the endpoint does not retransmit datagrams. The connection between the endpoints is terminated when either the terminal client or terminal server terminates the connection. No protocol-specific messages are exchanged to communicate that the endpoint is no longer present. Umm, this is RS-232 not something over ethernet. Protocol is UBER simple. Send command shit happens. Command might be "request for state" both literally and figuratively. The remote desktop talk was off topic. How is that It was completely unrelated to helping Ryan.
-
Why would you need a modem for this Enable remote access....and pm me your ip..... How would you connect from outside the local network? Unless the router is setup for port forwarding or using a reverse connection. UDP.. ...requires no handshakes.. excluding port 0 That doesn't make any sense to me. The Remote Desktop Protocol: UDP Transport Extension Protocol has two distinct phases of operation. The initial phase, UDP Connection Initialization (section 1.3.2.1), occurs when a UDP connection is initialized between the terminal client and the terminal server. Data pertaining to the connection is exchanged and the UDP connection is set up. Once this phase is completed successfully, the protocol enters the UDP Data Transfer (section 1.3.2.2) phase, where Coded Packets are exchanged. The protocol can operate in one of two modes. The operational mode is determined during the UDP Connection Initialization phase. These modes are as follows: RDP-UDP-R or "Reliable" Mode: In this mode, the endpoint retransmits datagrams that have been lost by the underlying network fabric. RDP-UDP-L or "Best-Efforts" Mode: In this mode, the reliable delivery of datagrams is not guaranteed, and the endpoint does not retransmit datagrams. The connection between the endpoints is terminated when either the terminal client or terminal server terminates the connection. No protocol-specific messages are exchanged to communicate that the endpoint is no longer present. Umm, this is RS-232 not something over ethernet. Protocol is UBER simple. Send command shit happens. Command might be "request for state" both literally and figuratively. The remote desktop talk was off topic.
-
You got it.
-
UDP requires no handshakes with windows platforms excluding port 0....linux is another story or devices connected through them You have absolutely no idea what you're talking about. Just admit it already. My Windows computer is connected to my router for Internet. It has no connection to my Linux computers. I could turn them off and unplug them from the network and it would make no difference. What you're saying is equivalent to "I could break into your 1996 Dodge Stratus, but if it's parked next to a 2001 Jeep Cherokee then I can't."
-
I wasn't trying to be a dick. I just didn't believe there was any way to do it other then the ways I already described.
-
How did I cheat?
-
Bullshit...The packets sent and received does not match up with this Ip has not been used!!!! Your going through a proxy or connected this ip to a device hardy used!!! Tell me I'm retarted! You're literally making up mumbo jumbo. I have a regular windows tablet with remote desktop enabled on a regular internet connection with a regular router. The fact that the other computers are running Linux is completely irrelevant.
-
This is from my local network, connecting to the windows computer: And here's connecting to port 22 from outside the network (since port 22 is forwarded on the router), and utterly failing to connect to port 3389:
-
Now use it.
-
Yes I just gave you my IP.
-
My router IP is 70.162.77.55 The computer's internal ip is 192.168.1.11 Here's my router with no port forwarding, the remote desktop settings on the windows computer, and showing port 3389 is in fact open from another computer on the network:
-
I really have no idea what you just said. Do you want to try or not?
-
AKA changing the router settings for port forwarding. So if I give you my router's IP and tell you to connect to my windows computer, you can't, unless I setup port forwarding on my router. Lets bet than...$100.00 paypal for your ip...I'm good for it... I'm not betting anything, I barely have enough to pay rent. Let me plug in my win8 tablet and enable remote access then I'll pm you my IP--if you still want to try.
-
AKA changing the router settings for port forwarding. So if I give you my router's IP and tell you to connect to my windows computer, you can't, unless I setup port forwarding on my router.
-
TCP and UDP is filtered but that is useless with the right tools......as far as the ip the history of the packets sent and received is helpful... I'm beginning to think you're retarded, or know a lot more about networking than I and just make no sense when explaining.
-
What I'm saying is the router filters incoming connections, so unless the router is setup to port forward than the computer won't connect. Or if you use a reverse connection where the computer behind the router connects to the other computer (that is either open to the internet like a server, or itself is behind a router that has port forwarding setup). Aside from the above I don't see how you can connect to a computer from outside it's local network, regardless of whether it's TCP or UDP. Are UDP connections not filtered on routers? If so, then how would you know which internal ip to connect to?
-
Why would you need a modem for this Enable remote access....and pm me your ip..... How would you connect from outside the local network? Unless the router is setup for port forwarding or using a reverse connection. UDP.. ...requires no handshakes.. excluding port 0 That doesn't make any sense to me.
-
Is there a manual online I could read? http://www.linearcorp.com/pdf/manuals/AXNET_226505.pdfHere are the instructions for connecting: http://www.linearcorp.com/faq/pdf-638.html From reading that it sounds like you can set it up with either a serial port OR modem. If you do the serial port way then you make a pseudo modem on the computer but it's actually using the serial port. Your computer has a port like the one on the far left here: http://www.libertycable.com/RUB_IMAGES/images/hi-res/DIGI-HDE-S_RS232_side.png ? Yes. I do know what a serial port is. I am lost on the rest of the shit you guys are talking about though. I don't believe you need a modem to connect to it, the serial port alone is enough (hardware wise). Then follow the instructions in that PDF for setting up the connection.
-
Why would you need a modem for this Enable remote access....and pm me your ip..... How would you connect from outside the local network? Unless the router is setup for port forwarding or using a reverse connection.
-
Did you use excel trend line? I tried using the solver in Excel but it wasn't working out, the plot was sigmoidal and the actual equation was just y=b+log(x/(1-x)). I suck at Excel though.
-
Is there a manual online I could read? http://www.linearcorp.com/pdf/manuals/AXNET_226505.pdf Here are the instructions for connecting: http://www.linearcorp.com/faq/pdf-638.html From reading that it sounds like you can set it up with either a serial port OR modem. If you do the serial port way then you make a pseudo modem on the computer but it's actually using the serial port. Your computer has a port like the one on the far left here: http://www.libertycable.com/RUB_IMAGES/images/hi-res/DIGI-HDE-S_RS232_side.png ?
-
Try hitting the escape key before dragging and dropping? Anything happen?
-
Is there a manual online I could read?
-
I mean that shit is like Rock Auto and their listing for a flux capacitor.