Most often carried over CAT5 cables with RJ-45 connectors via Ethernet signals. Other options, such as Pigeons, are available.
View TCP/IP settings and current IP address in
Troubleshooting, Methods@, Applications@ Ideas@ Servers@ Services@ ISPs@ embedded@ spam@
WinSock HTTP@ FTP@ DNS@ SMPT/POP3@ LPR@ Traceroute
Also:
See also:
If you are using A) MS Windows and B) a small local network and if you C) share resources (which is a common situation) then when you D) connect to the internet, these resources are made available to the internet BY DEFAULT! Since many people (most people) don't know this, it is a common opening for hackers.Windows 95 and 98 automatically bind the local network device sharing services to the internet connection. It is then possible to send a request for a list of available (shared) devices from anywhere on the internet and your machine will respond with all the devices you share on your local network (hard drive, printers, etc...) and with your user name and local network name! Now the hacker only needs to guess the password (and many people just leave the password blank) to have access to whatever you have shared and maybe to the rest of the network.
This has nothing to do with Java or JavaScript or any program being loaded onto your system without your permission. The program is ALREADY ON your system if you are using Windows and it feels that you have given it permission to share this information if you have not removed the check marks next to "Client for Microsoft Networks" and "File and Printer sharing for Microsoft Networks" under Start: Settings: Control Panel: Network: TCP/IP: Properties: Bindings. Which I very much recommend that you do.
See:
"In the beginning ARPA created the ARPANET.
And the ARPANET was without form and void.
And darkness was upon the deep.
And the spirit of ARPA moved upon the face of the network and ARPA said,
"Let there be a protocol," and thre was a protocol.
And ARPA saw that it was good. And ARPA said, "Let there be more
protocols," and it was so. And ARPA saw that is was good.
And ARPA said, "Let there be more networks," and it was so."
-- steward@deltanet.com, in misc.education
See:
George Patterson Says:
Another very good resource for understanding TCP/IP at the byte level is to read some of the Linux network drivers and other source. A large amount of the code is commented and easy to understand even if you are not a seasoned programmer.+
file: /Techref/tcpip.htm, 12KB, , updated: 2020/4/23 17:03, local time: 2024/11/5 02:48,
18.221.18.145:LOG IN ©2024 PLEASE DON'T RIP! THIS SITE CLOSES OCT 28, 2024 SO LONG AND THANKS FOR ALL THE FISH!
|
©2024 These pages are served without commercial sponsorship. (No popup ads, etc...).Bandwidth abuse increases hosting cost forcing sponsorship or shutdown. This server aggressively defends against automated copying for any reason including offline viewing, duplication, etc... Please respect this requirement and DO NOT RIP THIS SITE. Questions? <A HREF="http://linistepper.com/Techref/tcpip.htm"> TCP/IP</A> |
Did you find what you needed? |