After nearly 11 years, I’ve finally decided to pull the plug on Usenet archive: Groupsrv.com.
The page you have requested no longer exists!
But don’t panic just yet!
I’ve coded this page in a way, that it’s monitoring each redirect & capturing data about the thread you’ve requested. Page you’ve requested is still available in Google’s Usenet Archive. You should be able to access it using following URL:
Note: I can’t guarantee that all Groupsrv.com pages can be found in Google Groups, but over 90% of the content should be there. If not, try the resources below!
List of TCP and UDP port numbers! – also use port numbers. They usually use port numbers that match the services of the corresponding TCP or UDP implementation, if they exist. The Internet
Network address translation! – TCP and UDP packets, and for these protocols the port numbers are changed so that the combination of IP address and port information on the returned
Internet Relay Chat! – assigned port 194/TCP by IANA. However, the de facto standard has always been to run IRC on 6667/TCP and nearby port numbers (for example TCP ports 6660–6669
Telecommunication! – presented to higher layers. With UDP, packets are not ordered or retransmitted if lost. Both TCP and UDP packets carry port numbers with them to specify
RADIUS! – ports, web servers, etc. RADIUS is a client/server protocol that runs in the application layer, using UDP as transport. The Remote Access Server, the