« Previous Next »

Thread: Can't see my own websites on my networked PCs/MACs since getting AT&T U-verse

Last post 02-23-2009 7:21 AM by tomkmvp. 2 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (3 items)

Sort Posts:

  • 02-20-2009, 10:26 PM

    Can't see my own websites on my networked PCs/MACs since getting AT&T U-verse

    Recently went thru 6-week ordeal without Internet (incl email), but ended up with nice hi-speed service (+TV +phone) except for 2 problems of which this is one:

    The dozen or so websites are visible to computers other than those within my own home network.  They are hosted on a PC using IIS on my home network.  They have been up and running for years.  Nothing changed except the switch from AT&T (formerly PacBell) DSL to AT&T U-verse that has some majorly different intricacies (e.g. those that screw up my email which is also hosted on a PC in my network).  (Lost my static IP and am temporarily relying on the current IP staying static for a while, and pointed the DNS server to the new IP.)

     I've spent hours looking for solutions within IIS documentation and on the Internet.  Would greatly appreciate a fix or a pointer to one. 

     Thanks - Geoffrey!

  • 02-21-2009, 11:45 AM In reply to

    Re: Can't see my own websites on my networked PCs/MACs since getting AT&T U-verse

    Welcome to the land of 'consumer' high speed without a static ip address.  If I understand your question, the websites hosted on your pc aren't available.   You would need to ensure the DNS on the external DNS provider has the latest ip address.   Since you have a dynamic ip, a lot of services block port 80, 25.  This isn't an IIS problem per se as much as a connectivity.  I would do this.

    1) ensure you can telnet yourIP 80 from external to your network

    2) ping from an external source and see if they are up and running.

    I'm not sure if 1, 2 are working externally so that is why I mentioned.   For your internal machines to hit the same website.  I'd check your dns settings on your machines to ensure they can resolve the same addresses.  I run a Domain Controller at my house for years where the domain name was aspdot.net (which is also an external domain I own).  I had to 'add' ip addresses on the DC so internal boxes knew how to resolve the 'www' domain.   Hope that helps provide some direction.

    Steve Schofield
    Windows Server MVP - IIS
    http://weblogs.asp.net/steveschofield


    http://www.IISLogs.com
    Log archival solution
    Install, Configure, Forget
  • 02-23-2009, 7:21 AM In reply to

    • tomkmvp
    • Top 10 Contributor
    • Joined on 03-20-2003, 10:27 AM
    • Central NJ
    • Posts 6,163
    • IIS MVPs

    Re: Can't see my own websites on my networked PCs/MACs since getting AT&T U-verse

    As Steve indicated, it's likely that your ISP is blocking the ports necessary for running servers at home as this usually violates the terms of service of a consumer grade internet access account.

Page 1 of 1 (3 items)
Microsoft Communities