toggle

AAPL Stock: 442.04 ( + 8.78 )

http://www.macnn.com/articles/02/01/07/comcast.transitions/

Comcast transitions @Home customers,

updated 06:35 am EST, Mon January 7, 2002

 
", 0, 0);


Wade Williams, noting Comcast's lack of Mac support, writes "ComCast's new Internet service, to which former ComCast @Home users will transition starting January 15th, apparently will not be offering static IP addresses as a service. As you know, that means users will not be able to set up any type of web, gaming or other server. I would suggest that all Mac users using their service use the feedback form."


by MacNN Staff

Post tools:

TAGS :

 

Related Articles

Recent Articles

toggle

Comments

  1. MacNN.com Reader

    Fresh-Faced Recruit

    Joined: Jul 2001

    0
    01/07, 07:24am | report spam | Reply |

    Gaming server?

    Honestly, I've been on the line with Comcast technical support, and a gaming server is the last thing they want on their network. It slows everyone down on the node, especially with the upload speed caps on most systems that have existed already, and the fact each node is limited to a certain speed. We should NOT be asking for gaming server support without asking them to upgrade all nodes to support a minimum of 768 kbps upload speed for all users. Otherwise other people in the neighborhood will get frustrated by slow downloads and web speeds. If you are running a gaming server on my network now, please stop until you can convince Comcast to widen the bandwidth for everyone. It is the number one reason users see slower speeds during peak usage periods. Static IP address affects both PCs and Macs set up as gaming servers. This in fact is a good thing they are stopping it where it still exists, because with dynamic IPs it is harder for hackers to reach your machine, since they won't know what your IP address you are on all the time.

  1. nerdtech

    Fresh-Faced Recruit

    Joined: Aug 2000

    0
    01/07, 07:55am | report spam | Reply |

    DYNDNS.ORG

    Static IPs don't really matter when you use services like DYNDNS.ORG - they map DNS names to dynamic IP addresses, and do it by using clients that you install on your machine,

    On startup of your machine, the client then registers your IP address with your chosen DNS name on their DYNDNS domain name servers, and you can still get to your machine at home.

    My Comcast DHCP address rarely changes, but when it does, all I do is restart, or edit the DNS name on the DYNDNS.ORG website, and all is functional in minutes again.

    DYNDNS.ORG is free, by the way.

  1. phillymjs

    Fresh-Faced Recruit

    Joined: Jun 2000

    0
    01/07, 08:33am | report spam | Reply |

    DHCP makes no difference

    At least, not on @Home's network. You can reach a DHCP-addressed computer running a webserver or whatnot on Comcast@Home by punching in the fully-qualified name. I do this all the time to Timbuktu into the machine of a client I have who's on @Home.

    The fully-qualified name consists of the Comcast@Home-assigned hostname (usually something like "CC123456-A"), plus the local node's(?) name, your state abbreviation, and "home.com". For example, "CC123456-A.wlwgrv1.pa.home.com" would access computer CC123456-A on the Willow Grove, PA node.

    You can find out the name by doing NSLOOKUP on your IP address on a Windows box. I think TraceRoute on the Mac will pull up this info as well as part of some of its operations, I'm just too lazy to pull out my iBook right now to make sure. :-)

  1. rpfotog

    Fresh-Faced Recruit

    Joined: Jan 2002

    0
    01/07, 09:25am | report spam | Reply |

    New Network Headache

    My father-in-law was advised by Comcast that he had to change his iMac's TCP/IP settings a couple of weeks ago. He can now no longer use his iDisk, which he relies on nearly every day. I can access his iDisk from my home (also on Comcast) about 15 miles away but when I take my PowerBook to his location, I get the same problems he does; the connection won't let you upload, and it times out and disconnects after about two minutes. I'm worried that I'll suffer the same fate when my portion of the network gets changed over.

    No one has an answer.

  1. MacNN.com Reader

    Fresh-Faced Recruit

    Joined: Jul 2001

    0
    01/07, 09:42am | report spam | Reply |

    Not dropping mac support

    http://www.comcastonline.com/FAQsList.asp?.=.&FAQCategoryID=6

    Shows the requirements at the bottom of the page. Macintosh systems with OS 8.5 and up are listed as supported.

    The web site linked in the post does not work on Macs, but before people go and complain to ComCast, they should know that so far, it looks like only one web page lacks support. NOT their planned service.

    Loosing the static IP's will suck, even with DynDNS.

    128 upload speed is....come on. How lame is that?!?

    ComCast isnt gonna be much better then @Home.

  1. MacNN.com Reader

    Fresh-Faced Recruit

    Joined: Jul 2001

    0
    01/07, 10:47am | report spam | Reply |

    Subscriber agreement

    I suspect if you look at Comcast's subscriber agreement that there's a clause specifically prohibiting running servers. I know AT&T's agreement has such a restriction. By asking them for server support, you're raising a red flag. All they have to do is poll your machine for server ports and, if they find one, they can legally terminate your service.

  1. MacNN.com Reader

    Fresh-Faced Recruit

    Joined: Jul 2001

    0
    01/07, 10:54am | report spam | Reply |

    i agree

    I am with Concast and the service is terrible. Unfortunatley, they are the only game in town.

  1. mdmuzzie

    Joined:

    0
    01/07, 03:00pm | report spam | Reply | delete

    Comcast nightmare

    The transition between Comcast's old (@ Home) service and their new service has been a nightmare.

    I live in North Jersey (the Union area) and the DCHP server has been going down frequently. (It was even down this morning--the morning of the #@$% MWSF keynote; luckily I was planning on driving up to Tice's Corner anyway.)

    To top that off, my customer information was not even transferred to their new system until a week later. To top THAT off, they changed all of their customer support numbers without telling many customers their new numbers.

    I have had no more than a day and a half of uptime since December 27.

    This after 2 years of near continuous uptime with Comcast@home.

  1. mculbert

    Joined:

    0
    01/07, 11:26pm | report spam | Reply | delete

    re: New Network Headache

    Not sure if Comcast is willing to do anything about it, but this might at least be an explanation:
    (from Apple KnowledgeBase article 31201)

    Firewall and Proxy Server Setup

    iDisk uses the AppleTalk Filing Protocol (AFP). If your computer is behind a network firewall or proxy server, they must be set up to allow outbound connections on TCP port 548. Additionally, ICMP echo must be enabled on the firewall or proxy server.

    iDisk does not work through an HTTP or SOCKS proxy.

Login Here

Not a member of the MacNN forums? Register now for free.

 
close
Photo
toggle

Network Headlines

toggle

Most Popular

MacNN Sponsor

Recent Reviews

MaxUpgrades MaxConnect for 2006-2008 Mac Pro

Nobody outside of Cupertino's privileged bunch knows the future of the Mac Pro line for sure. Despite Apple's reluctance to tell us wh ...

Brother HL-3170CDW LED Printer

We've mentioned before that we are far from a paperless society. For now, at least, there are tasks that require a piece of paper for ...

HTC One

It is hard to overstate just how critically important the HTC One is to the Taiwanese company’s fortunes. Despite its alarming decline ...

toggle

Most Commented

 

Popular News