Cobb site specific internet problem

[rfinkle2]

Does anyone else have a problem getting onto Cobb's site in particular? There are some days when my laptop simply will not connect to the site.

Could it be internet connection speed related? i.e. I can access the site through my faster work connection, but not through my hot spot?

Any help with connection settings / timing out on that particular site would be appreciated.

I'm sweatin' @ the moment I'm so frustrated. LOL

So far :

- tried to DNS flush using msf config
- tried pinging the server and all 4 packets failed

@robry, @daustin.. could use a hang when you are free.

[trf5000]

I just logged onto it without an issue. Im at work currently.

[doubleflusher]

I don't have these issues, but I do lol @ msf config

Did you type ipconfig /flushdns then ipconfig /registerdns?

the site is up, but ping must be disabled, as I cannot ping cobbtuning.com

[trf5000]

I cannot ping either.

[rfinkle2]

Originally Posted by doubleflusher I don't have these issues, but I do lol @ msf config Did you type ipconfig /flushdns then ipconfig /registerdns? the site is up, but ping must be disabled, as I cannot ping cobbtuning.com

I did not try the second of the 2 options, but will now and report back. Thanks 2xflusher.

@doubleflusher.. sorry for my noobness. I mustn't be running my computer as administrator as it says elevation is needed. Could use a hand there as well.

[doubleflusher]

Right click on "Command Prompt' in Start Menu\All Programs\Accessories\ and choose "Run as Administrator".

This will give you elevated privileges, so you can run the above commands.

[rfinkle2]

OK. I used the second prompt and it states that registration of the dns has been initiated. I should know what to do @ this point, but could use some guidance.

[TiGraySpeed6]

I suspect your hotspot is having DNS issues
If you ping cobbtuning dot com, you should get an IP address returned even if cobb doesn't reply to pings. Do you get an IP address?



Are you on Win7, or XP? Other?

[rfinkle2]

Originally Posted by TiGraySpeed6 I suspect your hotspot is having DNS issues If you ping cobbtuning dot com, you should get an IP address returned even if cobb doesn't reply to pings. Do you get an IP address? Are you on Win7, or XP? Other?

Windows XP professional and I did get an IP address.

I tried manually entering the IP address into the address bar with no luck as well.

The more I read, the more it looks as if my network is blocking the address for some reason.

Thanks for the reply Tigray.

[Haltech]

Seems like an issue with their datacenter:

C:\Users\Haltech>tracert cobbtuning.com
Tracing route to cobbtuning.com [70.37.232.60]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     7 ms     7 ms     7 ms  10.147.0.1
  3     8 ms     8 ms     9 ms  ip68-6-12-166.sd.sd.cox.net [68.6.12.166]
  4    10 ms    10 ms     9 ms  visthbrc01-get0702.sd.sd.cox.net [68.6.8.119]
  5    11 ms    11 ms     9 ms  fed1sysc01-gex0901.sd.sd.cox.net [68.6.8.100]
  6    50 ms    34 ms    34 ms  paltbprj02-ae0.0.rd.pt.cox.net [68.1.0.235]
  7   145 ms   205 ms   205 ms  te3-8.ccr02.sjc04.atlas.cogentco.com [154.54.10.
125]
  8    35 ms    34 ms    35 ms  te0-0-0-6.ccr22.sfo01.atlas.cogentco.com [154.54
.0.177]
  9    36 ms    38 ms    38 ms  te0-3-0-3.ccr22.lax01.atlas.cogentco.com [154.54
.45.97]
 10    43 ms    44 ms    37 ms  te8-8.ccr02.lax04.atlas.cogentco.com [154.54.84.
122]
 11    40 ms    38 ms    39 ms  38.102.244.170
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *

[rfinkle2]

I e-mailed David @ Cobb and he mentioned, as have many guys that everyone but me seems to be able to get on their site. LOL.

I'm at home (using a different connection) now and can access the site without an issue.

I still need to figure out why my hotspot is having issues, but will DL what I need from home today.

[Haltech]

Well, i had no problems logging onto their site. Generally, if sites begin to get DDOS'd, the server will begin to ignore ping requests. Also, if the server is hardened, pinging them makes it difficult.

Test finished: Potential problems were found (warnings).
Basic View
Advanced View
cobbtuning.com
2012-07-26 00:35:45
Permalink:
Begin testing zone cobbtuning.com with version 1.0.1.
Delegation
Begin testing delegation for cobbtuning.com.
Name servers listed at parent: ns3.volusion.com,ns4.volusion.com
Name servers listed at child: ns3.volusion.com,ns4.volusion.com
No IPv6 name servers found.
Nameserver
Done testing delegation for cobbtuning.com.
Begin testing name server ns3.volusion.com.
Begin testing host ns3.volusion.com.
Begin testing address 209.99.51.21.
Done testing address 209.99.51.21.
Done testing host ns3.volusion.com.
Name server ns3.volusion.com (209.99.51.21) is recursive.
Name server ns3.volusion.com (209.99.51.21) authoritative for cobbtuning.com.
Name server ns3.volusion.com (209.99.51.21) answers queries over UDP.
Name server ns3.volusion.com (209.99.51.21) answers queries over TCP.
Name server ns3.volusion.com (209.99.51.21) closed for zone transfer of cobbtuning.com.
No answer received from 209.99.51.21 when querying for hostname.bind/CH/TXT.
No answer received from 209.99.51.21 when querying for version.bind/CH/TXT.
No answer received from 209.99.51.21 when querying for id.server/CH/TXT.
No answer received from 209.99.51.21 when querying for version.server/CH/TXT.
Done testing name server ns3.volusion.com.
Begin testing name server ns4.volusion.com.
Begin testing host ns4.volusion.com.
Begin testing address 69.36.95.4.
Done testing address 69.36.95.4.
Done testing host ns4.volusion.com.
Name server ns4.volusion.com (69.36.95.4) is not recursive.
Name server ns4.volusion.com (69.36.95.4) authoritative for cobbtuning.com.
Name server ns4.volusion.com (69.36.95.4) answers queries over UDP.
Name server ns4.volusion.com (69.36.95.4) answers queries over TCP.
Name server ns4.volusion.com (69.36.95.4) closed for zone transfer of cobbtuning.com.
No answer received from 69.36.95.4 when querying for hostname.bind/CH/TXT.
No answer received from 69.36.95.4 when querying for id.server/CH/TXT.
No answer received from 69.36.95.4 when querying for version.server/CH/TXT.
Done testing name server ns4.volusion.com.
Consistency
Begin testing zone consistency for cobbtuning.com.
SOA at address 69.36.95.4 has serial 56.
SOA at address 209.99.51.21 has serial 56.
All SOA records have consistent serial numbers.
All SOA records are consistent among all name servers.
Done testing zone consistency for cobbtuning.com.
SOA
Begin testing SOA parameters for cobbtuning.com.
Found SOA record for cobbtuning.com.
Begin testing host ns3.volusion.com.
Begin testing address 209.99.51.21.
Done testing address 209.99.51.21.
Done testing host ns3.volusion.com.
SOA MNAME for cobbtuning.com valid (ns3.volusion.com).
SOA MNAME for cobbtuning.com (ns3.volusion.com) listed as NS.
SOA MNAME for cobbtuning.com (ns3.volusion.com) is authoritative.
Begin testing email address admin@volusion.com.
Mail exchangers for admin@volusion.com found mx1.emailsrvr.com,mx2.emailsrvr.com.
Begin testing host mx1.emailsrvr.com.
Begin testing address 98.129.184.3.
Done testing address 98.129.184.3.
Done testing host mx1.emailsrvr.com.
Begin testing mail server mx1.emailsrvr.com (98.129.184.3) with admin@volusion.com.
SMTP banner: mx1.emailsrvr.com ESMTP - VA Code Section 18.2-152.3:1 forbids sending spam through this system
SMTP testing of mx1.emailsrvr.com (98.129.184.3) with admin@volusion.com succeeded without errors.
Done testing mail server mx1.emailsrvr.com (98.129.184.3) with admin@volusion.com.
Begin testing host mx2.emailsrvr.com.
Begin testing address 173.203.2.32.
Done testing address 173.203.2.32.
Done testing host mx2.emailsrvr.com.
Delivery over IPv4 to admin@volusion.com ok.
Delivery over IPv6 to admin@volusion.com could not be done.
Done testing email address admin@volusion.com.
Successful attempt to deliver email for SOA RNAME of cobbtuning.com (admin.volusion.com) using admin@volusion.com.
SOA TTL for cobbtuning.com too small (900) - recommended >= 3600.
SOA refresh for cobbtuning.com too small (900) - recommended >= 14400.
SOA retry for cobbtuning.com too small (600) - recommended >= 3600.
SOA expire for cobbtuning.com too small (86400) - recommended >= 604800.
SOA minimum for cobbtuning.com OK (3600) - recommended between 300 and 86400.
Done testing SOA parameters for cobbtuning.com.
Connectivity
Begin testing connectivity for cobbtuning.com.
Name server 209.99.51.21 announced by: 40670,3900
Name server 209.99.51.21 announced by multiple AS.
Name server 69.36.95.4 announced by: 27597
Zone announced by ASN: 27597,40670,3900
Zone announced by more than one ASN (3).
Zone announced by IPv6 ASN:
Zone announced by only one IPv6 ASN (0).
Done testing connectivity for cobbtuning.com.
DNSSEC
Begin testing DNSSEC for cobbtuning.com.
Did not find DS record for cobbtuning.com at parent.
Servers for cobbtuning.com have consistent extra processing status.
Did not find DNSKEY record for cobbtuning.com at child.
No DNSKEY(s) found at child, other tests skipped.
Done testing DNSSEC for cobbtuning.com.
Test completed for zone cobbtuning.com.

[rfinkle2]

It must be specific to my Verizon Wireless Hotspot. I have an e-mail into them (Verizon Wireless) and hope that it is a simple resolution.

Is that the best way to go about it guys?

[Haltech]

What happens when you bypass verizons dns and use googles? 8.8.8.8?

[rfinkle2]

I would be willing to give everything a try. Haltech, I'm such a noob but take direction well.

How do I use google's dns and bypass the Verizon's?

[Haltech]

Finkle.. the first thing i need you to do, is get on your knees...

How do you have you NIC card setup on your laptop? You need to change the DNS entries for your mobile hot spot to your NIC.

Does your hotspot run verizon software to connect?

[smoogs12]

Originally Posted by rfinkle2 I would be willing to give everything a try. Haltech, I'm such a noob but take direction well. How do I use google's dns and bypass the Verizon's?

Just gonna link you to this fink. Way easier than typing it out.

https://developers.google.com/speed/...dns/docs/using

[TiGraySpeed6]

Try this- we're gonna change your DNS servers to OpenDNS, which is a stunningly good free DNS service that I highly recommend

Control Panel>Network Connections>Double click on the hot spot connection to get the properties window>Click the Properties button>

When the connection properties window opens, scroll the middle part to Internet Protocol TCP/IP & double click on that line


When that properties window opens, in the lower part of the window choose the radio button to Use the following DNS server addresses & set them with the values shown in this screenshot-


Next, open a cmd prompt, type ipconfig /flushdns

Then try to access COBB Tuning - Engineered Performance.
Report back

lol, if you want help from multiple folks giving essentially the same advice.....

[rfinkle2]

I have an internet protocol version 4 and an internet protocol version 6.

@smoogs12, I would try that but would need to print it out and go carefully, as it is a little over my head @ current. LOL

[Haltech]

All of us do finkle.. dont bother with 6, make the modification to 4

[TiGraySpeed6]

do v4

The only reason my screenshot doesn't show v4 & v6 is that it's my ancient old virtual machine image. It only exists for my Dashhawk software


and tech support screenshots.....

[rfinkle2]

I tried the method as tigray posted, but still get the same message. I suck. LOL

[Haltech]

Maybe this is an omen... you don't need to be on Cobb sites.

[rfinkle2]

Originally Posted by Haltech Maybe this is an omen... you don't need to be on Cobb sites.

Geez Haltech, Thanks for the vote of confidence.

[rfinkle2]

I'm calling it a night on this issue tonight guys. Thanks for all of the help @smoogs12 and @TiGraySpeed6 and as always Haltech, for your support *ahem.

[TiGraySpeed6]

I suspect your IP s being filtered for reasons not of your doing/within your control.
-> You can ping & get an ip address, but just like everybody else, no returns
-> changing DNS & flushing to force recreating route made no changes
-> everybody else can reach without difficulty
-> you can reach from your office without difficulty

Unless you can get your hotspot to provide a new IP, it's a verizon issue. You can test by using a proxy based browser like TOR, which I bet will connect just fine.

[smoogs12]

Try a different browser?

[rfinkle2]

Originally Posted by smoogs12 Try a different browser?

So far, I've tried Firefox and Chrome with the same result. I'm a little frustrated, and hope to get it sorted tomorrow.

The more I read what you guys post and some of the Comcast support given to different issues, it seems as if Verizon is blocking the site / causing the issue for some reason.

Thanks guys for all of the help.

I have a working comcast connection and will download what I need tonight. No sweat.

[TiGraySpeed6]

FF & Chrome wil use the same routing methods. To change things up you need to appear to be in a different place- proxy based routing. TOR is easiest & most popular way to appear to be someplace else.


Not that I'd ever need to do that.....

[rfinkle2]

Originally Posted by TiGraySpeed6 FF & Chrome wil use the same routing methods. To change things up you need to appear to be in a different place- proxy based routing. TOR is easiest & most popular way to appear to be someplace else. Not that I'd ever need to do that.....

Now you have my ear (sounds like spy shit) lol, but am sick of seeing that error message for today.

If Verizon gets back to me, I'll let you guys know how that goes. LOL

[robry]

just saw this now Rob, everyone has given you sound advice and gone through the troubleshooting I would as well with you.

TOR is an option for you I suppose.

[daustin]

Sorry for checking in late here, Rob. It sounds like a block from either Cobb's webservers or Verizon's end. I'm actually more inclined to think it would be Verizon, but I've seen IP filtering on webhosts get the best of you from time to time.

I'm having no issues here at home on Comcast/Chrome, but that doesn't really tell us much other than Cobb isn't down.

Another question for you here that I don't think has been touched on is are you using the same computer for both connections? AKA home/hotspot? I just wonder if it isn't a browser cache issue.

[TiGraySpeed6]

seemed appropriate......

[Haltech]

dial #611 and go right to tech support. They should have it fixed within the hour at verizom.

[TiGraySpeed6]

don't be bringing simple, good ideas to actually resolve the issue in here...
You'll set a bad example for the other children!

[rfinkle2]

Originally Posted by daustin Sorry for checking in late here, Rob. It sounds like a block from either Cobb's webservers or Verizon's end. I'm actually more inclined to think it would be Verizon, but I've seen IP filtering on webhosts get the best of you from time to time. I'm having no issues here at home on Comcast/Chrome, but that doesn't really tell us much other than Cobb isn't down. Another question for you here that I don't think has been touched on is are you using the same computer for both connections? AKA home/hotspot? I just wonder if it isn't a browser cache issue.

It is the same machine, yes. I've tried clearing all of the temp files, cache etc... and done what the other guys in the thread have suggested.

Thanks for the suggestions and like you, think Verizon is the problem...SOB's. LOL.

I'm hoping that they will find that they have the site blocked for some reason. I've read that comcast customers have reported site specific issues and have had it resolved through their back office allowing sites to be accessed and hope that is the issue I'm having, but with Verizon.

[daustin]

It could be a problem with Verizon's DNS servers, but your previous test should have worked around that. I actually jumped on a client computer here real quick on Verizon business class service to see if the same site had any problems, but it worked just fine. I know that isn't the mobile broadband service, but I would assume that similar or the same DNS servers would be used.

It's pretty hard for me to say here, but it doesn't sound like a problem with your computer or on Cobb's end... so yea I think you are tracking down the right location with contacting Verizon about the problem.