Return-Path: Received: from na3sys009aog106.obsmtp.com ([74.125.149.77] verified) by realpeople.com (CommuniGate Pro SMTP 5.1.16) with SMTP id 1550810 for Helix-L@realpeople.com; Sun, 22 Aug 2010 14:59:14 -0500 Received-SPF: none receiver=realpeople.com; client-ip=74.125.149.77; envelope-from=greg@glmyers.com Received: from source ([209.85.213.179]) by na3sys009aob106.postini.com ([74.125.148.12]) with SMTP ID DSNKTHGBiCHHIBNYoVEgtqCmMlvgzncijqZ7@postini.com; Sun, 22 Aug 2010 12:59:13 PDT Received: by yxp4 with SMTP id 4so2022164yxp.38 for ; Sun, 22 Aug 2010 12:59:04 -0700 (PDT) Received: by 10.100.57.1 with SMTP id f1mr4289501ana.205.1282507136522; Sun, 22 Aug 2010 12:58:56 -0700 (PDT) Return-Path: Received: from [192.168.15.9] (cpe-066-057-047-187.nc.res.rr.com [66.57.47.187]) by mx.google.com with ESMTPS id 14sm9285192ant.1.2010.08.22.12.58.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 22 Aug 2010 12:58:55 -0700 (PDT) Message-Id: From: Greg Myers To: Helix Discussion List In-Reply-To: Content-Type: multipart/alternative; boundary=Apple-Mail-2--742761271 Content-Transfer-Encoding: 7bit X-Mailer: iPad Mail (7B500) Mime-Version: 1.0 (iPad Mail 7B500) Subject: Re: [Hx] Comcast Business Class Hell - OFF Date: Sun, 22 Aug 2010 15:58:36 -0400 References: --Apple-Mail-2--742761271 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Did you wait the needed two days after changing the DNS entry to test = it? Like I said, I am totally guessing for possibilities, but impatience = with DNS changes is typically the problem that bites me when I do = similar changes.=20 Greg Myers Chapel Hill, NC Sent from my iPad On Aug 22, 2010, at 2:58 PM, Elton wrote: >> Putting the static IP on the WAN port makes perfect sense given what = you describe >=20 > I guess it does, as my Netopia's WAN setup defines the login and = PAP/CHAP to Bellsouth, as well as the NAT, Compression Method, Firewall, = etc., etc. -- it just does not work with this Comcast (2) IP/passthrough = static setup on their SMC that will not allow true bridge-mode.=20 >=20 > If you are talking about a more less complicated Netgear or Linksys = router interface, it does look simple to do, but "not so much" with our = (old school) Netopia R910 -- maybe I'll just get another router (just = got burned the last time I did this). >=20 > If I google topics related to this Comcast SMC Gateway, problems seem = rampant in server environments and there are a myriad of suggestions = with no clear solution -- so, it not just me ;) >=20 >=20 >> I expected some comment on your DNS settings. The absence of such a = comment makes mean think that is the source of your issues. >=20 > I didn't comment on DNS my because the Comcast SMC in front of the = Netopia will not work at all; no point in discussing DNS if you have no = internet at all. >=20 > The DNS worked fine with the Comcast SMC acting a the primary router; = but I can use the SMC as my primary router for the reasons outlined. >=20 > My DNS has pointed to my Bellsouth DSL static IP, since 1996 -- all = has worked perfectly. I moved my registrar's (Network Solutions) = pointers to the Comcast static IP -- all port-forwarding to my servers = worked if you are not inside the SMC's LAN with the servers. I recall = this problem in another office that used the Comcast SMC when testing = Windows 2003 server remote desktop, you could not test from inside the = office LAN and learned that the Comcast SMC will not properly handle = port forwarding when the calls originate from the SMC's LAN. Also port = 8080 is hardcoded as the SMC's remote admin port, which is Tomcat's = default port, etc. -- this maybe another reason why Comcast does not = recommend using the SMC Gateway as a primary router -- they encourage = you to use it as a bridge-mode TA, in front of a "real router". It = would be much easier to do this if they provided such a device (as they = used to do on noe-business accounts) vs. this problematic router without = true bridge-mode capabilities. >=20 >=20 > Elton >=20 > --------------------------- > Sent from my BlackBerry Wireless Handheld >=20 > On Aug 22, 2010, at 1:05 PM, Greg Myers wrote: >=20 >> Putting the static IP on the WAN port makes perfect sense given what = you describe, but I expected some comment on your DNS settings. The = absence of such a comment makes mean think that is the source of your = issues. Just a wild guess on my part, but it is often a good place to = start. >>=20 >> Greg Myers >> Chapel Hill, NC >>=20 >> Sent from my iPad >>=20 >> On Aug 22, 2010, at 11:21 AM, Gib Henry wrote: >>=20 >>> I've heard horror tales about Comcast broadband=E2=80=94but then = again, I can tell you first-hand horror stories about Bellsouth DSL. = Have you looked at hiwaay.net? My experience with their predecessors = and with them was nothing but positive; it's just that they couldn't = match cable speeds (if/when Bright House/Road Runner is working). At = least they make a reliable backup for cable broadband. >>>=20 >>> And what about the power-grid networks we were hearing about some = years ago? The power companies were going to offer phone and internet = across their powerlines, but that hasn't materialized as far as I know. >>>=20 >>> For some reason, American DSL seems to be limited to about 1.5Mbps = down (and whatever they throttle you to for upload), which mystifies me, = because in Europe, DSL speeds can exceed 20Mbps. I've heard that our = infrastructure (phone lines) just won't do any better, but my office is = directly across the street from the telco central office...? The = fiber-optic folks were interested in stringing a line across the street, = but not enough users in the building were willing to sign up (sigh). = Cheers, >>> --=20 >>> =20 >>> Gib >>>=20 >>> On 8/21/10 6:00 PM, Elton wrote: >>>>=20 >>>> I'm moving from Bellsouth DSL to Comcast Business Class. Either = I'm not getting something, or the Comcast tech support that I spoke to = told me wrong, but I cannot get the Comcast SMC Gateway to work with our = R910 Netopia router (also learned that I cannot use the Comcast SMC as a = primary router; will not route properly inside the LAN to the WAN back = to our servers; assume this is why few use it as a primary router in a = server environment, from what Comcast tells me). Comcast issued me (2) = IP#"; the Gateway's IP #XX.XX.XX.106 and my static IP #XX.XX.XX.105. = They told me how to set the Comcast SMC Gateway to "semi-bridge mode" = (basically: turn of everything, check the first 2 of 3 features to all = "True Static IP Passthrough", uncheck "provide DHCP", etc., then told me = to connect out router to the SMC Gateway, and go into our router's WAN = setup and "assign it to the #105 static IP# they issued" (which makes no = sense, IMO) -- I tried this 20-times, to no avail. Maybe its me or = maybe its our Netopia R910 (old school) router (which is not so simple = to do this with it's: address translations, compression, PAP/CHAP, = firewall, options, etc., etc. settings in the WAN setup) -- but I could = not get it to work after spending all night trying. Reverted all back = to the Bellsouth/Netopia setup.=20 >>>>=20 >>>> Anyone have any experience with this?=20 >>>>=20 >>>> Thank!;=20 >>>>=20 >>>> Elton=20 >>>>=20 >>>> ---------------------------=20 >>>> Sent from my BlackBerry Wireless Handheld=20 >>>>=20 >>>>=20 >>>> = =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=20 >>>> You received this message because you are subscribed to the mailing = list . To unsubscribe, e-mail = ; to switch to DIGEST mode, e-mail = ; contact a human being at = . Google archive since 20 August 2006: = http://groups.google.com/group/helix-l. Basic archive since 1 Jan 2006: = http://mail.realpeople.com:8100/Lists/Helix-L/List.html=20 >>>>=20 >>>=20 >=20 --Apple-Mail-2--742761271 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Did you wait the needed two days = after changing the DNS entry to test it? Like I said, I am totally = guessing for possibilities, but impatience with DNS changes is typically = the problem that bites me when I do similar = changes. 

Greg Myers
Chapel = Hill, NC

Sent from my iPad

On Aug 22, 2010, at 2:58 = PM, Elton <elton@ehdarby.com> = wrote:

Putting the static IP on the WAN port makes = perfect sense given what you describe

If you are talking about a more less = complicated Netgear or Linksys router interface, it does look simple to = do, but "not so much" with our (old school) Netopia R910 -- maybe I'll = just get another router (just got burned the last time I did = this).

If I google topics related to this = Comcast SMC Gateway, problems seem rampant in server environments and = there are a myriad of suggestions with no clear solution -- so, it not = just me ;)


I expected = some comment on your DNS settings. The absence of such a comment makes = mean think that is the source of your = issues.

I didn't comment on DNS my = because the Comcast SMC in front of the Netopia will not work at all; no = point in discussing DNS if you have no internet at all.
The DNS worked fine with the Comcast SMC acting a = the primary router; but I can use the SMC as my primary router for the = reasons outlined.

My DNS has pointed to my Bellsouth = DSL static IP, since 1996 -- all has worked perfectly.  I moved my = registrar's (Network Solutions) pointers to the Comcast static IP -- all = port-forwarding to my servers worked if you are not inside the SMC's LAN = with the servers.  I recall this problem in another office that = used the Comcast SMC when testing Windows 2003 server remote desktop, = you could not test from inside the office LAN and learned that the = Comcast SMC will not properly handle port forwarding when the calls = originate from the SMC's LAN.  Also port 8080 is hardcoded as the = SMC's remote admin port, which is Tomcat's default port, etc. -- this = maybe another reason why Comcast does not recommend using the SMC = Gateway as a primary router -- they encourage you to use it as a = bridge-mode TA, in front of a "real router".  It would be much = easier to do this if they provided such a device (as they used to do on = noe-business accounts) vs. this problematic router without true = bridge-mode capabilities.



---------------------------
Sent = from my BlackBerry Wireless Handheld
=
On Aug 22, 2010, at 1:05 PM, Greg Myers = wrote:

Putting the static IP on the = WAN port makes perfect sense given what you describe, but I expected = some comment on your DNS settings. The absence of such a comment makes = mean think that is the source of your issues. Just a wild guess on my = part, but it is often a good place to = start.

Greg Myers
Chapel Hill, = NC

Sent from my iPad

On Aug 22, 2010, at 11:21 AM, = Gib Henry <gib@realpeople.com> = wrote:

I've heard horror tales about Comcast = broadband=E2=80=94but then again, I can tell you first-hand horror = stories about Bellsouth DSL.  Have you looked at hiwaay.net?  My experience with = their predecessors and with them was nothing but positive; it's just = that they couldn't match cable speeds (if/when Bright House/Road Runner = is working).  At least they make a reliable backup for cable = broadband.

And what about the power-grid networks we were = hearing about some years ago?  The power companies were going to = offer phone and internet across their powerlines, but that hasn't = materialized as far as I know.

For some reason, American DSL = seems to be limited to about 1.5Mbps down (and whatever they throttle = you to for upload), which mystifies me, because in Europe, DSL speeds = can exceed 20Mbps.  I've heard that our infrastructure (phone = lines) just won't do any better, but my office is directly across the = street from the telco central office...?  The fiber-optic folks = were interested in stringing a line across the street, but not enough = users in the building were willing to sign up (sigh).  = Cheers,
--
<gib.png>
  Gib
=
On 8/21/10 6:00 PM, = Elton wrote:
I'm moving from Bellsouth DSL to Comcast Business = Class.  Either I'm not getting something, or the Comcast tech = support that I spoke to told me wrong, but I cannot get the Comcast SMC = Gateway to work with our R910 Netopia router (also learned that I cannot = use the Comcast SMC as a primary router; will not route properly inside = the LAN to the WAN back to our servers; assume this is why few use it as = a primary router in a server environment, from what Comcast tells = me).  Comcast issued me (2) IP#"; the Gateway's IP #XX.XX.XX.106 = and my static IP #XX.XX.XX.105.  They told me how to set the = Comcast SMC Gateway to "semi-bridge mode" (basically: turn of = everything, check the first 2 of 3 features to all "True Static IP = Passthrough", uncheck "provide DHCP", etc., then told me to connect out = router to the SMC Gateway, and go into our router's WAN setup and = "assign it to the #105 static IP# they issued" (which makes no sense, = IMO) -- I tried this 20-times, to no avail.  Maybe its me or maybe = its our Netopia R910 (old school) router (which is not so simple to do = this with it's: address translations, compression, PAP/CHAP, firewall, = options, etc., etc. settings in the WAN setup) -- but I could not get it = to work after spending all night trying.  Reverted all back to the = Bellsouth/Netopia setup.

Anyone have any experience with = this?

Thank!;

Elton

= ---------------------------
Sent from my BlackBerry Wireless = Handheld


= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
= You received this message because you are subscribed to the mailing list = <Helix-L@realpeople.com>.=   To unsubscribe, e-mail <Helix-L-off@realpeople.com<= /a>>; to switch to DIGEST mode, e-mail <Helix-L-digest@realpeople.co= m>; contact a human being at <Helix-L-request@realpeople.= com>.  Google archive since 20 August 2006:  http://groups.google.com/g= roup/helix-l.  Basic archive since 1 Jan 2006:  http://ma= il.realpeople.com:8100/Lists/Helix-L/List.html

=
=

= = --Apple-Mail-2--742761271--