Comcast + Irc

Discussion in 'GR Classic Archive' started by Bona Fide, Sep 1, 2005.

  1. Bona Fide

    Bona Fide Well-Known Member

    Age:
    37
    Posts:
    4,067
    Likes Received:
    0
    Joined:
    Dec 31, 2004
    Location:
    New York, USA
    I've enabled the Identd server just like they said to, but I still get that problem.

    Any help?
     
  2. KrazyNick

    KrazyNick Well-Known Member

    Posts:
    3,248
    Likes Received:
    0
    Joined:
    Apr 8, 2005
    yeah eddieD has comcast and irc dosent work for him either :(
     
  3. Gurly

    Gurly Well-Known Member

    Age:
    47
    Posts:
    8,027
    Likes Received:
    0
    Joined:
    Mar 11, 2005
    Location:
    The Nut House
    ive heard this b4 also im not sure what it is
    but someone said b4 it maybe something to do with a router or maybe even firewalls im not sure though :/
     
  4. Bona Fide

    Bona Fide Well-Known Member

    Age:
    37
    Posts:
    4,067
    Likes Received:
    0
    Joined:
    Dec 31, 2004
    Location:
    New York, USA
    Well here's what I have done, maybe it'll help clear some issues up.

    - Disabled firewall
    - Forwarded port 113 from router
    - Enabled identd server

    Anything I missed?
     
  5. Gurly

    Gurly Well-Known Member

    Age:
    47
    Posts:
    8,027
    Likes Received:
    0
    Joined:
    Mar 11, 2005
    Location:
    The Nut House
    not that i can see :/ and you get this also on just trying to enter the chat room or just on irc ?
     
  6. Llamaman

    Llamaman Senior Member

    Posts:
    2,059
    Likes Received:
    0
    Joined:
    Apr 24, 2004
    Location:
    UK
    What is the error message you are getting when you connect?
     
  7. KingCrazy

    KingCrazy Well-Known Member

    Posts:
    488
    Likes Received:
    0
    Joined:
    Jan 8, 2005
    i have comcast and get the sme problem :(
     
  8. EddieD

    EddieD Well-Known Member

    Age:
    36
    Posts:
    3,653
    Likes Received:
    0
    Joined:
    Nov 27, 2004
    Location:
    Boston, MA
    It told me to unblock port 113. I unblocked it and it still didn't work.
     
  9. Obscurax

    Obscurax Well-Known Member

    Age:
    39
    Posts:
    269
    Likes Received:
    0
    Joined:
    Jun 1, 2005
    Location:
    carpe noctem
    Use a proxy server, i never go on irc without one...
     
  10. .ckn

    .ckn Well-Known Member

    Age:
    36
    Posts:
    398
    Likes Received:
    0
    Joined:
    Aug 10, 2005
    Location:
    California
    this happened to me too but i am a cox user (cox is an cable/telephone/internet provider in san diego and other places)
     
  11. LXSCOPE

    LXSCOPE Senior Member

    Age:
    35
    Posts:
    1,665
    Likes Received:
    0
    Joined:
    Jun 25, 2005
    Location:
    Chicago
    same problem here... <_< if someone could figure this out it would be SWEET man i wish i could get on this... the only thing i could think of was a different chat room server... :P

    hope you try to help this ^_^

    thanks
     
  12. Bona Fide

    Bona Fide Well-Known Member

    Age:
    37
    Posts:
    4,067
    Likes Received:
    0
    Joined:
    Dec 31, 2004
    Location:
    New York, USA
    Okay here we go.

    Girly - This happens when I try to connect to Quakenet. It happens with all IRC clients, so its not a mIRC issue.

    Llama - I posted it in my first post. :)

    EddieD - Ditto that.

    Obscurax - Good idea, I'll try later tonight.
     
  13. KiwiFlavor

    KiwiFlavor Well-Known Member

    Age:
    38
    Posts:
    1,573
    Likes Received:
    0
    Joined:
    Jun 8, 2005
    Location:
    Dover, NH
    heh i have comcast but i didnt have a problem tho :huh:


    oo btw u like my pick up lines :lol:
     
  14. Kjah

    Kjah Well-Known Member

    Posts:
    78
    Likes Received:
    0
    Joined:
    Aug 1, 2005
    Use a proxy server
     
  15. Logicaly

    Logicaly Senior Member

    Age:
    44
    Posts:
    4,253
    Likes Received:
    0
    Joined:
    May 17, 2005
    Location:
    Bay Area, California
    Opening up port 113 on my router fixed this problem.
     

Share This Page