Return-Path: Received: from ehdarby.com ([67.33.59.6] verified) by realpeople.com (CommuniGate Pro SMTP 5.1.16) with ESMTP id 1550807 for Helix-L@realpeople.com; Sun, 22 Aug 2010 13:58:58 -0500 Received-SPF: none receiver=realpeople.com; client-ip=67.33.59.6; envelope-from=elton@ehdarby.com Received: from [192.168.0.3] ([74.230.12.211]) by ehdarby.com (Post.Office MTA v3.8.4 release 116 ID# 1001-64977U100L10S0V38) with ESMTP id com for ; Sun, 22 Aug 2010 13:58:54 -0500 Message-Id: <2692FA2A-555F-4469-A6BA-9E8D11E8181E@ehdarby.com> From: Elton To: "Helix Discussion List" In-Reply-To: Content-Type: multipart/alternative; boundary=Apple-Mail-1--746351708 Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: [Hx] Comcast Business Class Hell - OFF Date: Sun, 22 Aug 2010 13:58:46 -0500 References: X-Mailer: Apple Mail (2.936) --Apple-Mail-1--746351708 Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable > Putting the static IP on the WAN port makes perfect sense given what =20= > you describe I guess it does, as my Netopia's WAN setup defines the login and PAP/=20 CHAP to Bellsouth, as well as the NAT, Compression Method, Firewall, =20 etc., etc. -- it just does not work with this Comcast (2) IP/=20 passthrough static setup on their SMC that will not allow true bridge-=20= mode. If you are talking about a more less complicated Netgear or Linksys =20 router interface, it does look simple to do, but "not so much" with =20 our (old school) Netopia R910 -- maybe I'll just get another router =20 (just got burned the last time I did this). If I google topics related to this Comcast SMC Gateway, problems seem =20= rampant in server environments and there are a myriad of suggestions =20 with no clear solution -- so, it not just me ;) > I expected some comment on your DNS settings. The absence of such a =20= > 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 =20 Netopia will not work at all; no point in discussing DNS if you have =20 no internet at all. The DNS worked fine with the Comcast SMC acting a the primary router; =20= 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 =20 has worked perfectly. I moved my registrar's (Network Solutions) =20 pointers to the Comcast static IP -- all port-forwarding to my servers =20= worked if you are not inside the SMC's LAN with the servers. I recall =20= this problem in another office that used the Comcast SMC when testing =20= Windows 2003 server remote desktop, you could not test from inside the =20= office LAN and learned that the Comcast SMC will not properly handle =20 port forwarding when the calls originate from the SMC's LAN. Also =20 port 8080 is hardcoded as the SMC's remote admin port, which is =20 Tomcat's default port, etc. -- this maybe another reason why Comcast =20 does not recommend using the SMC Gateway as a primary router -- they =20 encourage you to use it as a bridge-mode TA, in front of a "real =20 router". It would be much easier to do this if they provided such a =20 device (as they used to do on noe-business accounts) vs. this =20 problematic router without true bridge-mode capabilities. Elton --------------------------- 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 =20= > you describe, but I expected some comment on your DNS settings. The =20= > absence of such a comment makes mean think that is the source of =20 > your issues. Just a wild guess on my part, but it is often a good =20 > place to start. > > Greg Myers > Chapel Hill, NC > > Sent from my iPad > > On Aug 22, 2010, at 11:21 AM, Gib Henry wrote: > >> I've heard horror tales about Comcast broadband=97but then again, I =20= >> can tell you first-hand horror stories about Bellsouth DSL. Have =20 >> you looked at hiwaay.net? My experience with their predecessors =20 >> and with them was nothing but positive; it's just that they =20 >> couldn't match cable speeds (if/when Bright House/Road Runner is =20 >> working). At least they make a reliable backup for cable broadband. >> >> And what about the power-grid networks we were hearing about some =20 >> years ago? The power companies were going to offer phone and =20 >> internet across their powerlines, but that hasn't materialized as =20 >> far as I know. >> >> For some reason, American DSL seems to be limited to about 1.5Mbps =20= >> down (and whatever they throttle you to for upload), which =20 >> mystifies me, because in Europe, DSL speeds can exceed 20Mbps. =20 >> I've heard that our infrastructure (phone lines) just won't do any =20= >> better, but my office is directly across the street from the telco =20= >> central office...? The fiber-optic folks were interested in =20 >> stringing a line across the street, but not enough users in the =20 >> building were willing to sign up (sigh). Cheers, >> --=20 >> >> Gib >> >> On 8/21/10 6:00 PM, Elton wrote: >>> >>> I'm moving from Bellsouth DSL to Comcast Business Class. Either =20 >>> I'm not getting something, or the Comcast tech support that I =20 >>> spoke to told me wrong, but I cannot get the Comcast SMC Gateway =20 >>> to work with our R910 Netopia router (also learned that I cannot =20 >>> use the Comcast SMC as a primary router; will not route properly =20 >>> inside the LAN to the WAN back to our servers; assume this is why =20= >>> few use it as a primary router in a server environment, from what =20= >>> Comcast tells me). Comcast issued me (2) IP#"; the Gateway's IP =20 >>> #XX.XX.XX.106 and my static IP #XX.XX.XX.105. They told me how to =20= >>> set the Comcast SMC Gateway to "semi-bridge mode" (basically: turn =20= >>> of everything, check the first 2 of 3 features to all "True Static =20= >>> IP Passthrough", uncheck "provide DHCP", etc., then told me to =20 >>> connect out router to the SMC Gateway, and go into our router's =20 >>> WAN setup and "assign it to the #105 static IP# they =20 >>> issued" (which makes no sense, IMO) -- I tried this 20-times, to =20 >>> no avail. Maybe its me or maybe its our Netopia R910 (old school) =20= >>> router (which is not so simple to do this with it's: address =20 >>> translations, compression, PAP/CHAP, firewall, options, etc., etc. =20= >>> settings in the WAN setup) -- but I could not get it to work after =20= >>> spending all night trying. Reverted all back to the Bellsouth/=20 >>> 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-=20 >>> =3D-=3D- >>> You received this message because you are subscribed to the =20 >>> mailing list . To unsubscribe, e-mail = >> >; to switch to DIGEST mode, e-mail >> digest@realpeople.com>; contact a human being at = >> >. Google archive since 20 August 2006: = http://groups.google.com/group/helix-l=20 >>> . Basic archive since 1 Jan 2006: = http://mail.realpeople.com:8100/Lists/Helix-L/List.html >>> --Apple-Mail-1--746351708 Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable
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=97but 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>.&nbs= p; To unsubscribe, e-mail <Helix-L-off@realpeople.com&= gt;; 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-1--746351708--