Changes for 2008 your desktop should change daily
Dec 24

Craig wants to know all about configuring his network.

 
icon for podpress  Standard Podcast [124:44m]: Play Now | Play in Popup | Download (624)

24 Responses to “Trouble Shooting a Network”

  1. Tom Mahady Says:

    R.E.M. references that refer to songs made by the band that occurred after GREEN will only be worth half the point value of something that would be on document or earlier.

  2. blackdan Says:

    the entire explanation on A, B and C networks and subnets was rubbish… but at least you guys were right when you said that - for home users - this doesn’t matter.

    Happy holidays!

  3. Tom.landy Says:

    Best christmas present ever guys…So happy when I got up to both a MacBreak Tech and a VFX show…

    Also Something Something ID sounds better…happy christmas & a merry new year!

    tom.landy
    Ireland

  4. macbreaktech Says:

    No kidding the subnets discussion. This the problem with having questions sprung out of no where–no notes. I should have cut it from the discussion but decided to leave it in because in the end it doesn’t matter at all. If you really want to know all about subnets try these links:

    http://en.wikipedia.org/wiki/IP_address

  5. Shash Says:

    Awesome! I’m barely crawling along, about to run out of podcast content: and you guys give me 2 hours of it!

    Are you guys every going to do an episode on bonjour? you brought it up, but i think you could go into much more detail on it.

    Shash

  6. Jeff Says:

    Thanks, guys. I actually did listen to the whole 2 hours and learned a lot. Basic question, I guess, but in the beginning you were talking about how to get back to my mac working in the DHCP environment and mentioned connecting the dsl modem/router into the airport extreme’s LAN port instead of the WAN port. If I heard this correctly, why does this work?

    I have a similar set up and can’t figure out how to open up a port that needs to be opened…. Thanks.

    Jeff

  7. The Ash Man Says:

    That was a great episode, all review and elementary for me as an IT professional, but it is great to hear these complicated matters worked through and discussed. Feels like school. Your podcast is among the best. Length is not a problem, I would rather have the depth.

  8. saltyfrog Says:

    Where are all the shownotes that were mentioned during the talk? “I’ll put it in the show notes”… am I not seeing them?

  9. incon Says:

    sorry guys…. that was over done (poorly) and I’m glad your shows a talk already in progress because you need an episode just for errata for this baby. Not sure what else to say…. If you don’t know the acronyms look them up before the podcast not on the fly otherwise you lose a lot of geek creed. Sorry but pick up your game other I’ll be picking up my rj45’s and cat6 and crimping else where.

  10. Warren Says:

    Long time listener(from Hello World), first time poster. ;-)
    Love the show guys. I am a Windows leaning to Linux user, but love the show as so much of what you talk about crosses all platforms. Especially have enjoyed all the networking casts. Keep up the good work!

  11. lvthunder Says:

    I really wouldn’t say this would be a troubleshooting your network episode. I would say it is an Introduction to Networks episode. Not that is was bad or anything, but there wasn’t a lot of troubleshooting in it.

  12. TJ Asher Says:

    Hey, where are the slides?!?!

    You said you would post them so we could follow along.

    I also agree that in this world of acronyms, you better know them in a show where you are supposedly teaching folks. If you don’t, look it up before the show and don’t make up things. There’s enough misinformation out there as it is.

    The shows are great but you really need to appoint someone to take notes so that you can provide links to stuff. Either that or have John’s intern go through the show and find the linkable stuff and post it.

  13. Mike Loiterman Says:

    Just a quick note:

    Many modem/routers can be set to bridge mode…at least they used to. A quick google search on the model should reveal an internal IP address that, when access, should allow this type of modification.

    This would allow Craig to use his AirPort as Apple intended. It would also simplify his setup and prevent dual NAT/Firewall issues.

  14. Doug Walker Says:

    Show notes please! I would love to have the Keynote files. It would help when I have to explain this stuff to my family.

  15. piminnowcheez Says:

    Let me add my keytaps to the chorus:

    Hugely useful show, thanks!

    and

    Eagerly awaiting those slides!

  16. Scott Says:

    Just started listening to this episode, and came looking for the shownotes you mention…now I’m not sure if I want to listen to this stuff “in thin air” or whether I’ll just skip this episode…

  17. Jon Quimbaya Says:

    I 2nd what Mike said. I had DSL 2 years ago, and I turned off the router portion of the modem. It just passed the public IP address along to the the router I had. This allows the use of the router’s firewall. Eg. if I wanted to use UPNP, I couldn’t use the router in the modem because it didn’t support it. By doing what you suggested of not using the WAN port of the Airport, then UPNP would not be available.

  18. Scott S-New York Says:

    You should know that setting your DHCP server to serve out a publicly routable IP address is a BAD thing! Let’s say you set your DHCP server to serve out addresses from this space 74.125.19.0/24 Well that happens to belong to Google and when you try to browse to google the DNS server will return the address of 74.125.19.99 (the address for http://www.google.com) and then your router will think that is on the local subnet. Viola! you cannot reach google and most users will be scratching their heads for a long time. DHCP server should only serve out non routable address spaces or address spaces assigned to the user.

  19. Paul TS Lee Says:

    Next time, integrate the slides into the podcast, i.e. making an enhanced aac with linked images. Yes, it’s extra work, but that would make it a better podcast.

    Regarding the things you guys got wrong/confused: I’m ok with acronyms not always being expanded correctly, as long as their use is correct. However, for stuff like UPnP and other security related matters, you guys really should run it by Steve Gibson. I mean, you *are* in related podcast networks, and leveraging Steve is a Good Thing.

  20. Carlos Says:

    Echo the positive comments above - thanks for this show. Really helpful.

    I also echo the comments above - where are the notes / slides???

  21. Jeremiah Staes Says:

    I love how these shows tell the why - I am putting this question here because it seems like the right place, and not appropriate with the most current show.

    Along the theme of this episode, I’d like to hear a show on the “why” certain things are. For instance, why did resetting my PMU fix my twitchy DVD drive on my macbook? Or, why does flashing the PRAM help with certain issues? What does Applejack do that seems to make my machine run better when things are wonky? Why is it that some USB hubs don’t seem to want to sync with an iPhone or some iPods (I’ve been able to replicate this multiple times on different machines - I’ve bought multiple hubs to get it to work, and the only ones which seem to work are USB 1.0, which is really annoying).

    In short, more “Penn and Teller”… the mac-fu in the background.

  22. gamov Says:

    hi,
    I have almost the same setup as Craig: 1 modem router + 1 apple router. I’m a bit puzzled why you didn’t propose the following settings im using:
    1. I put the modem router (a speedtouch) in bridge mode (the ISP gave me the configuration file to upload)
    2. The apple router connecting via PPPoE to the ISP and managing my home network (with DHCP, NAT, WPA2, etc)

    It was no so clear that we can also do the opposite, setting the apple router as a wireless bridge.

    It was a nice long show to listen, kudos.

    Cheers,
    Gam

  23. Eric Naujock Says:

    Uggh. Please do your research before talking about a topic. Within every 5 minutes I found myself pounding my head into a wall to get the bad information out. If the person asking questions does not do the research at least have the expert do it. Get a copy of TCP/IP illustrated and read it before talking about this stuff. Each question had at least 1 factual error in it. Please try to do a better job in the future. This episode really hurt your street cred in my opinion. As a former CCNP , CCDP it really hurt.

  24. llf Says:

    I also would have liked to have seen the slides. I presume they’re long gone by now. The ‘cast itself was good, imo, because I’m in the middle of troubleshooting a tough complex network issue…..

    BTW, it would have been nice if you’d said *what exactly* you were looking at, i.e. network settings in Tiger or Leopard, Airport Utility, the 2Wire s/ware, etc.

    And, of course, the comment about the book author being a woman, and therefore ‘no tech in the book’ was gratuitous….. that’ll only get you in trouble.

    But I love the casts, love the depth of what you do. I suggest you mention earlier on in the ‘casts *who you are* as I have only a clue, even after listening to 6 or 7 of these.

    Thanks for what you do, in any case.

Leave a Reply