• (cs) in reply to R.Flowers
    R.Flowers:
    I wonder what lucky company landed Ishmael?

    Pequod.com? Now there's a company with a future...
  • Remco Gerlich (unregistered)
    Anonymous:
    The REAL wtf is that this guy uses <font> tags...

    Did you just call Google "this guy"?
  • Poor sod (unregistered) in reply to biziclop

    Actually, they fired me on his advice, because of my "questionable judgement".  God help 'em.

    Keep in mind that the anonymization of this story complicated it somewhat... the actual fix was much simpler than moving a hard drive. The boot floppy is a lovely artistic touch very much in keeping with the spirit of this infrastructiure, but it didn't really happen that way. :-)

  • (cs) in reply to Poor sod
    Anonymous:
    This is the submitter. It actually was an IP-based network.

    Could you explain what the problem was? was it firewalled, or misrouted?

  • (cs) in reply to ammoQ
    ammoQ:
    I can't decide what is worse: The production file server that boots from a floppy disk or the communication over the internet. The later is more dangerous, but the former seems more stupid.


    Booting from removable media isn't stupid. As long as it's write protected, you've set youself in a decent position with regards to intruders, because they won't be able to compromise key services and instruction sets. I use removable media all the time, though I don't use floppies (yuck). Hell, some of my production servers run completely off the CD drive, with the hard drive only there for logging and virtual memory. It's the ideal of commodity hardware...Run a bootable cd that grabs the application that is supposed to run off an app server, and runs it until the machine goes poof, and then you jack a copy of the cd into a different machine, reboot, and let it do it's thing. Downtime is practically nil.

    Mind you, I agree about the networking. TCP/IP is pretty damn simple. If you don't understand that your LAN is the exact same thing as the internet, just on a much smaller scale, you've got no business setting up a network.
  • (cs) in reply to notromda
    notromda:
    Anonymous:
    This is the submitter. It actually was an IP-based network.

    Could you explain what the problem was? was it firewalled, or misrouted?



    It's more likely that without the big chunk of configuration on the floppy, the machine no longer had any kind of networking set up. Or it had some host-y files or something, or the gateway was set there or any one of a number of problems...Though high-end routers can be configured to strip ping out of traffic.

    Odd that the machine could be pinged from the internet. Sounds like a lot of static IPs.

  • (cs) in reply to richleick

    richleick:
    Wow... they've got the Internet on computers now?

    The Internet? Is That Thing Still Around?

    From the Simpsons:

    Moe: Okay, that night we camped out under the stars.
    [dissolve to the past.  They boys are sitting around a
    campfire]
    Ah, look at all them stars.  Bunch of lazy lights -- don't
    do nothing for nobody.
    Carl: Hey, you know what I'm looking forward to?  The future. 
    Have you heard about this internet thing?
    Lenny: Internet?
    Carl: Yeah, it's the internetting they invented to line swim
    trunks.  [holds up a pair of trunks caresses his face
    lining] It provides a comforting snugness.

  • (cs) in reply to hyfe

    Anonymous:
    pjabbott:
    Anonymous:
    The LAN probably wasn't TCP/IP based; Running off on DOS it may have been IPX, NetBUEI, or Appletalk (ok, probably not Appletalk)


    That's the part I don't get...it's very likely that at least one of these was used since it was DOS-based, but  none of those (IIRC) are routable so they would not work over the internet.
    The introduction does mention having several NIC's in each computer. That mess may be insanity, but each single step leading there might have been reasonably sane.. and as long as stuff was working, why change? Too many of the posters here are probably too young to remember ipx and the ilk anyways :(

    I'm glad I'm too young to know how to load things into 'Upper memory'

    My first OS was Windows 98 with 'Plug and Pray'.

    My guess is that the network was made out of spare parts from the guy's University job .. his Rube Goldberg attempt at abstract network topology art.  If you connect the circles between the iner-connected NIC cards it spells out a secret message about satin.

  • (cs) in reply to snoofle
    snoofle:

    Just wondering... given today's equipment, if you had a 'scanner' with a sufficiently sensitive ammeter, and you ran a phone line carrying a 28.8K connection through the middle, could it 'see' the electromagnetic impulses, errr, bits, as they passed by?

    That's basically how an inductive phone tap works.

  • A. Nony Mous (unregistered) in reply to l1fel1ne
    Anonymous:

    Reminds me of the sysadmin at a previous job. He got the hot idea of crimping RJ45 jacks onto cat 3 cable (yes, regular untwisted phone cable) when doing the office wiring....



    I actually did that in an old office network, it worked well at 10mb... It wasn't my choice, but it was what was there, and what was in the budget...

    When we moved into a new office I took the time to wire it properly.

    Man i'm glad I don't do that anymore!
  • Poor sod (unregistered) in reply to notromda

    notromda:

    "Could you explain what the problem was? was it firewalled, or misrouted?"

    The server was actually a Win2k3 Small Business Server machine running a business-critical dos-based shared app. The fellow had set up "routing and remote access" to filter local network access to the machine, so that only authenticated machines' or users' packets would pass in. (Not an entirely un-clever thing to do, but it would have been nice of him to mention it when I asked him under what circumstances the server might be unreachable!)

    This server also did domain control, but did not do DHCP, which was running off a soho-grade firewall appliance. About a week before I got my call, he replaced the old server with this new one, re-creating instead of migrating the active directory domain. Then he deleted the previous domain from the old server and turned it off.  (Because of this I thought it was a domain SID problem for a while, but that turned out to be a red herring.)

    But he failed to change the IP addresses of the new server to match the old server's, or to change the DHCP server options to tell the desktops where to find the new local nameserver and domain controller.  So after the reboot-rodeo he put them through, everything could see the soho-router and internet DNS, but nothing could find the domain controller or local DNS.  Since they couldn't find the domain controller, they couldn't authenticate to it. Since they couldn't authenticate to the domain, the firewall on the domain controller dropped their packets, including my diagnostic pings. Nifty!

    (As if all that wasn't amusing enough, the range of 64 DHCP addresses available for lease included both the old and new server IP addresses. Fortuately there were never more than 45 IP devices attached at a time...)

    I fixed it by taking down his R&RA filter and manually authenticating to the server from each desktop, just as an emergency stopgap. They needed a real fix before he came back, though, so I then looked into it more and at this point figured out how hosed their local DHCP was. So I set about configuring DHCP in a more rational way... at which point he got me taken off the contract. :-)

  • (cs) in reply to Bus Raker
    Bus Raker:
    My guess is that the network was made out of spare parts from the guy's University job .. his Rube Goldberg attempt at abstract network topology art.  If you connect the circles between the iner-connected NIC cards it spells out a secret message about satin.

    Uhh ... Secret messages about a soft, shiny fabric?  Cool!  :D
  • StupidPeopleTrick (unregistered)

    Ahhhhh, the best (job) security is antiquity.

     

    - - SPT

  • (cs) in reply to snoofle
    snoofle:
    Just wondering... given today's equipment, if you had a 'scanner' with a sufficiently sensitive ammeter, and you ran a phone line carrying a 28.8K connection through the middle, could it 'see' the electromagnetic impulses, errr, bits, as they passed by?


    Well, the immediate problem is that a "28.8k" connection is an analog connection, and not a digital one. That means that you have a MOdulator taking bits (well, bytes rather) and encoding a carrier signal based on the bit stream, for processing by a DEModulator at the other end.

    See: http://en.wikipedia.org/wiki/Modulation
    and http://rnvs.informatik.tu-chemnitz.de/vorlesungen/rn_lwb/Modems/Modems.html

    So you need not so much a scanner/ammeter, as it's not a on-off type circuit, but rather something that works in the human audio spectrum that's trasmitted over phone lines. The you can analyze the phase changes in the carrier, and recover the bit stream. This is usually done in something like, say, a modem ;-)




  • (cs) in reply to Poor sod
    Anonymous:
    notromda: authenticate to the domain, the firewall on the domain controller dropped their packets, including my diagnostic pings. Nifty!

    That makes more sense. Less of a WTF, and yet oh so much more. Oh well, I fire any clients that end up being that stupid. Yes, you read that right. As a consultant, I can can fire the client. Sometimes they aren't worth the money.

  • (cs) in reply to IQpierce
    IQpierce:

    The solution is obvious. Take a scan of the hard copy of the autoexec.bat file, and use a text-recognition program to convert that scan to text. Then just paste it into the autoexec.bat file, put it on a new floppy, and everything will go perfectly smoothly.



    Nice job, but you'll be docked a half-day's pay for not involving a wooden table.

  • Hanneth (unregistered)

    I fear you!

  • verisimilidude (unregistered)

    The insurance company would only give the guy 10 hours a month and would refuse to allow anything that might take down the network.  New machines had to be added and backups done regularly.  Ishmael had no time to upgrade the network, install software, or anything else.  It worked and that was all the client wanted and would pay for.  DOS based network drivers didn't implement ping.  Until Windows 3.1 (Windows for Workgroups) TCP support was rare.  The main point I would ding Ismael on was not having the boot floppies backed up.  That he wasn't a salesman who could convince the client that their working system needed upgrading - not his job.

  • (cs) in reply to Bus Raker
    Bus Raker:

    Anonymous:
    pjabbott:
    Anonymous:
    The LAN probably wasn't TCP/IP based; Running off on DOS it may have been IPX, NetBUEI, or Appletalk (ok, probably not Appletalk)


    That's the part I don't get...it's very likely that at least one of these was used since it was DOS-based, but  none of those (IIRC) are routable so they would not work over the internet.
    The introduction does mention having several NIC's in each computer. That mess may be insanity, but each single step leading there might have been reasonably sane.. and as long as stuff was working, why change? Too many of the posters here are probably too young to remember ipx and the ilk anyways :(

    I'm glad I'm too young to know how to load things into 'Upper memory'

    My first OS was Windows 98 with 'Plug and Pray'.

    My guess is that the network was made out of spare parts from the guy's University job .. his Rube Goldberg attempt at abstract network topology art.  If you connect the circles between the iner-connected NIC cards it spells out a secret message about satin.


    Naw, he strikes me as more of a Rayon, guy.
  • (cs) in reply to marvin_rabbit
    marvin_rabbit:
    Bus Raker:

    Anonymous:
    Too many of the posters here are probably too young to remember ipx and the ilk anyways :(

    I'm glad I'm too young to know how to load things into 'Upper memory'

    My first OS was Windows 98 with 'Plug and Pray'.

    My guess is that the network was made out of spare parts from the guy's University job .. his Rube Goldberg attempt at abstract network topology art.  If you connect the circles between the iner-connected NIC cards it spells out a secret message about satin.


    Naw, he strikes me as more of a Rayon, guy.

    Oops .. meant 'satan'.  Looking at it though .. I kind of like satin better anyway.

  • (cs) in reply to marvin_rabbit
    marvin_rabbit:
    Bus Raker:

    Anonymous:
    Too many of the posters here are probably too young to remember ipx and the ilk anyways :(

    I'm glad I'm too young to know how to load things into 'Upper memory'

    My first OS was Windows 98 with 'Plug and Pray'.

    My guess is that the network was made out of spare parts from the guy's University job .. his Rube Goldberg attempt at abstract network topology art.  If you connect the circles between the iner-connected NIC cards it spells out a secret message about satin.


    Naw, he strikes me as more of a Rayon, guy.

    Damned duplication!  I swear I only clicked 'Submit' once. 

  • (cs) in reply to snoofle
    snoofle:

    Grrrr - stuck at home with 3 sick kids for a week - if I hear one more kid *snoof*, I'm, going to run amuck $*#&%@ !!!

    Peltor makes great hearing protection.  I have the Optime 105 model headset, and it even drowns out the C&W from the office next door (which is at least 105 decibels . . . on my side of the wall!).

  • konrad (unregistered) in reply to John
    Anonymous:
    The LAN probably wasn't TCP/IP based; Running off on DOS it may have been IPX, NetBUEI, or Appletalk (ok, probably not Appletalk)


    Being there, fixed that.

    When I arrived at my last job the shared network drive was on some-ones desktop. When I actually investigated the terminals I found that win 95 machines (this was current at the time) where each running between 1 and 3 different network protocols and that there was no common denominator, so a lot of the machines could not talk to the file share directly but had to find another machine to relay the information.

    Somehow this worked (granted it crashed 2 - 3 times per day)
    needless to say getting things down to just one common protocal improved network performance.
  • (cs) in reply to Colin
    Colin:
    This post makes me want to write a calculator that wraps google's search.


    Better yet you could write it in JavaScript using AJAX to get that Web 2.0 touch!
  • Poor sod (unregistered) in reply to notromda

    Notromda: The clients were not stupid, just ignorant and misled. They have chosen to remain so.

    (Which is a darn shame, since several friends of mine are clients of theirs. My friends kept asking me "So when are you going to fix their horrible billing system?" as soon as I told them I was going to consult for the company.  Now I have to tell them "I'm not"... and (rather gratifyingly) they all seem to be hastily scrambling to find other providers.)

    Once straightened out it would have been good and easy money. C'est la vie.

  • Anonymous (unregistered) in reply to Poor sod

    This topic should be called "ping-pong". In Spain (Europe, for those yankees who don't know that), we say "pong" like you say "smack down". I say this because Ishmael smacked down him by saying that.

  • foxyshadis (unregistered) in reply to A. Nony Mous
    Anonymous:
    Anonymous:

    Reminds me of the sysadmin at a previous job. He got the hot idea of crimping RJ45 jacks onto cat 3 cable (yes, regular untwisted phone cable) when doing the office wiring....



    I actually did that in an old office network, it worked well at 10mb... It wasn't my choice, but it was what was there, and what was in the budget...

    When we moved into a new office I took the time to wire it properly.

    Man i'm glad I don't do that anymore!

    Untwisted cat3 is actually rated at 1-10mb (witness dsl) as long as the lines are short and in reasonably good condition, so it's not that bad an idea as long as you don't try pumping 100 (or god forbid, gbE) over it.
  • (cs) in reply to Larry Rubinow
    Anonymous:
    I'm going to guess that, in this day and age, he didn't have a spare floppy drive lying around; it was probably easier to move the hard drive than steal a floppy drive from a machine that might require it.

    ...or perhaps it was the DISK that was corrupt, and not the floppy drive itself? Reread the article plz.
  • (cs) in reply to l1fel1ne
    Anonymous:

    Reminds me of the sysadmin at a previous job. He got the hot idea of crimping RJ45 jacks onto cat 3 cable (yes, regular untwisted phone cable) when doing the office wiring....



    There is also nothing wrong with that either.  Cat 3 was the standard for Ethernet for many years and was rated for 10Mbps, and often got close to 100Mbps when using two pair.  If you have many long runs and don't need the speed, why pay four times the cost?  If your entire office is running thin clients/dumb terminals, how much traffic is sent over the network?

    Cat 3 lost favor to Cat 5/5e during the client/server boom because of the increase in network traffic.  Since there was no widespread adoption of new telephony tech, it was still used as analog/digital phone cabling.  Today, most run Cat 5/5e/6 for both voice and data since it is easier to run at the same time and prepares for VOIP implementation.
  • (cs) in reply to pjabbott

    pjabbott:
    Anonymous:
    The LAN probably wasn't TCP/IP based; Running off on DOS it may have been IPX, NetBUEI, or Appletalk (ok, probably not Appletalk)


    That's the part I don't get...it's very likely that at least one of these was used since it was DOS-based, but  none of those (IIRC) are routable so they would not work over the internet.

    As mentioned earlier, IPX is routable.  But also....  TCP/IP is extremely easy to set up with the "Microsoft Network Client for MSDOS".  It was available around 1990 and is still in use today in a lot of corporate environments to get a basic network client booted from a floppy, usually as a first step in installing a real operating system.  So the suggestion that they weren't using TCP/IP because they were using DOS is rediculous.  If they weren't using TCP/IP, it was because the admin was an idiot or they were in a Novell environment for a long time.  In fairness to Novell, Novell NetWare has supported TCP/IP since the 80s and has been based primarily on TCP/IP since the mid 1990s, but most people used IPX on NetWare networks until the late 1990s because it was easier.

    Most importantly, since the post says that there actually was a PING utility on the workstations, they must have had TCP/IP installed.  The PING utility is installed along with the TCP/IP protocol and won't function unless TCP/IP is installed and configured.  The odds that this idiot administrator figured out how to tunnel TCP/IP over IPX without actually running TCP/IP on the network are about a billion to one.  There are products like NetWare IP that would have allowed a ping to be sent over an IPX network, but NetWare IP requires a NetWare server to do the de-encapsulation.

  • (cs) in reply to l1fel1ne
    Anonymous:

    Reminds me of the sysadmin at a previous job. He got the hot idea of crimping RJ45 jacks onto cat 3 cable (yes, regular untwisted phone cable) when doing the office wiring....


    Regular untwisted phone cable is Cat 1.  Cat 3 is twisted pair cable.  The rating on the categories are meaningless.  Cat 3 is rated for 10Mb/s, but 99% of 100Mb/s network cards will run over Cat 3 wiring and even say so in the instructions.  Cat 5 is rated for 100Mb/s, but right now, I'm writing this post on a gigabit network using Cat 5 cable.  Thank goodness it works, because Cat 5e is rated for 500Mb/s and Cat 6 is rated for 850Mb/s.  I'm unaware of a copper cabling standard that claims to be capable of 1000Mb/s.  That doesn't seem to prevent the manufacture and sale of millions of gigabit network cards.

    I have actually run 2.5Mb/s ArcNet over coat hangers and salt water.  The water wasn't rated for 2.5Mb/s.

    Before 1995, the economically prudent thing to do was to wire the building with Cat 5 cable and put Cat 3 ends on them.  It would be easy to swap out the end in the future, but difficult to replace the wire in the walls.  It worked out well, most people who did that haven't spent another dime on the wiring and are running 1000Mb/s today over it.

  • yv (unregistered) in reply to l33t
    Anonymous:
    Gore put the G in G-mail



    Please tell me that he didn't put the G in my gf's G-spot though...
  • The 2-Belo (unregistered)
    Alex Papadimoulis:

    He confirmed that the servers and workstation did, in fact, communicate with each other over the Internet.

    I was just sitting here wondering how many of these servers there were, and how much this outfit was paying to keep them all in global IP addresses in this day and age. Then I started to think about the WORKSTATION having a global IP so it could talk to its own servers via the internet even though it was just a few feet away, and if not how it was being mapped through multiple daisy-chained routers, and oh dear I think I have to go lay down for a while.

    CAPTCHA Test: foxtrot. Now all I need is a whiskey and a tango.

    - 2

     

  • Tom (unregistered) in reply to Colin
    Anonymous:
    This post makes me want to write a calculator that wraps google's search.

    Believe it or not, my friend wrote a Dashboard widget to do exactly this.

  • (cs) in reply to rswafford

    <FONT face=Arial>guy with the "free ipod" thing in your sig: </FONT>

    <FONT face=Arial>Your signature makes me embarrassed for you.  :(</FONT>

    <FONT face=Arial>(and you're a few years late -- maybe try selling Amway too?)</FONT>

     

  • M (unregistered) in reply to yv

    I see that you mentioned having a girlfriend on the Internet. Please, go on. What's she like?

  • Some Idiot (unregistered) in reply to Jersey
    Anonymous:
    Anonymous:
    Anonymous:

    He accomplished this in ten year's for a small insurance agency.

    One probably cannot begin to imagine what the local university network is like after ten years with this kind of administration!!!!

     

    capthca: pacman ( Hated that annoying woka-woka noise!)

    As a University Student, I can't say I would be truly shocked by him working there

     

    <FONT face=Arial>Exactly my thought. Some of the professors are too old-school and don't really realize that teaching students ONLY what THEY know and not allowing them to explore and use new things will make things like this happen. But then again... Maybe he did it on purpose to screw the company over for all those years of being underpaid and underappreciated and whose skills were abused. High-school kids with a lot more experience than the average and not a lot of prospects to land a technical job... Well, it's possible.</FONT>

     

    I couldn't agree more. That woka-woka noise was like having a steering wheel down your pants.

    It really drove me nuts.

  • Cyclomedia (unregistered) in reply to xrT
    <font face="Tahoma">
    "You can't ping on a local network," Ishmael quipped, clearly annoyed, "didn't you know that?"
    </font>


    "The trouble with the world is that the stupid are cocksure and the intelligent are full of doubt."

  • (cs) in reply to Cyclomedia

    Anonymous:
    <FONT face=Tahoma>
    "You can't ping on a local network," Ishmael quipped, clearly annoyed, "didn't you know that?"
    </FONT>


    "The trouble with the world is that the stupid are cocksure and the intelligent are full of doubt."

    And just how sure are you on that?!?

  • (cs)

    Apart from the potential security (and obvious stability) problems with the set up, it is very possible that the DOS machines were not connected locally using TCP/IP.  No TCP/IP means no Ping.  I know it is strange to think so, but there was a time, (and actually not so long ago) where computers used many other communication protocols to connect to each other.  And even still, when the Internet came along and became popular, still used their own propietary or otherwise network protocols to communicate with each other, and only used TCP/IP to communicate with the Internet.

        dZ.

  • (cs) in reply to xrT
    xrT:
    ammoQ:
    I can't decide what is worse: The production file server that boots from a floppy disk or the communication over the internet. The later is more dangerous, but the former seems more stupid.

    <font style="font-size: 24px;" face="Tahoma">This one is much worse... Guys like these are the reason why the things you mentioned exists...

    "You can't ping on a local network," Ishmael quipped, clearly annoyed, "didn't you know that?"



    </font>


    Not if the local network is using, say, IPX/SPX, or maybe Netware, or NetBUI -- some very popular network protocols during the heyday of DOS and Windows 3.11
  • TheDoom (unregistered) in reply to DZ-Jay

    Yanks eh? I thought they invented the electro-grid?

  • dept non style dep (unregistered) in reply to DZ-Jay

    I know a location where "windows network connection" is banned so printers cant be shared.

    The standar way to get something printed is:

    1. Use the "print as pdf" option
    2. Upload the file to a public website incomming folder
          (trough FTP or a upload.asp file )
    3. walk to the computer with printer
    4. Open a web browser
    5. Open the incomming folder, and open your document pdf file
    6. Print

    Often users make mistakes, so this cycle is repeated 3 o 4

    This is not as good has teh Linux Torbalds method to backup his kernel source :(  (let others mirror it).

    --Tei



  • (cs) in reply to dept non style dep

    Anonymous:
    I know a location where "windows network connection" is banned so printers cant be shared.

    The standar way to get something printed is:

    1) Use the "print as pdf" option
    2) Upload the file to a public website incomming folder
        (trough FTP or a upload.asp file )
    3) walk to the computer with printer
    4) Open a web browser
    5) Open the incomming folder, and open your document pdf file
    6) Print

    Often users make mistakes, so this cycle is repeated 3 o 4

    This is not as good has teh Linux Torbalds method to backup his kernel source :(  (let others mirror it).

    --Tei



    At least the printer is standing on a wooden table, right?

  • Dazed (unregistered) in reply to dept non style dep

    Anonymous:
    I know a location where "windows network connection" is banned so printers cant be shared.

    The standar way to get something printed is:

    1) Use the "print as pdf" option
    2) Upload the file to a public website incomming folder
        (trough FTP or a upload.asp file )
    3) walk to the computer with printer
    4) Open a web browser
    5) Open the incomming folder, and open your document pdf file
    6) Print

    Often users make mistakes, so this cycle is repeated 3 o 4

    This is a bigger WTF than the original post! Not only does the internal traffic go via the Internet, but everyone knows it does - but does nothing about it - and it's a real pain for all the users as well. Let me guess - either the download is not password-protected at all, or it has a password like "print"?

    Go on - give us a URL ...

  • DerelictMan (unregistered) in reply to impslayer
    impslayer:

    Anonymous:
    <font face="Tahoma">
    "You can't ping on a local network," Ishmael quipped, clearly annoyed, "didn't you know that?"
    </font>


    "The trouble with the world is that the stupid are cocksure and the intelligent are full of doubt."

    And just how sure are you on that?!?

    Nice. ;)
  • Foo (unregistered) in reply to areyouretarded
    Anonymous:
    I'm pretty sure *ping* is a golf club and has nothing to do with the internet or Al Gore...

    does Al Gore play golf??


    Dude, Al Gore plays golf on the internet!
  • Real WTF Detector (unregistered) in reply to Poor sod

    The real, real WTF is having to tell the stupid story twice. Once for make believe in way that has nothing to do with what actually happened, and once possibly for real...

    ... or are you going to surprise us with the real, real, real WTF in a day or two?

  • Carl Carlson (unregistered) in reply to Bus Raker
    Bus Raker:

    richleick:
    Wow... they've got the Internet on computers now?

    The Internet? Is That Thing Still Around?

    From the Simpsons:

    Moe: Okay, that night we camped out under the stars.
    [dissolve to the past.  They boys are sitting around a
    campfire]
    Ah, look at all them stars.  Bunch of lazy lights -- don't
    do nothing for nobody.
    Carl: Hey, you know what I'm looking forward to?  The future. 
    Have you heard about this internet thing?
    Lenny: Internet?
    Carl: Yeah, it's the internetting they invented to line swim
    trunks.  [holds up a pair of trunks caresses his face
    lining] It provides a comforting snugness.

    I think I just logged on to my internet.

  • Jon W (unregistered) in reply to WHO WANTS TO KNOW?
    Jon W:

    Besides, the WAN is simply a larger LAN.



    Biggest. Chuckle. Yet.

    Call me back when Linksys makes BGP routers :-)

    Captcha = quality!

Leave a comment on “That's What the Internet Is For”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article