Could you guys look and see if what I am seeing is right? They offer Global Crossing and Cogent officially. So if I use GLBX looking glass, I get this.
Trying trace from node 'Miami, FL, US' to '96.31.73.xxx'
1 64.214.16.65 (64.214.16.65) 0.761 ms 0.608 ms
2 so0-0-0-2488M.ar2.TPA1.gblx.net (67.17.66.165) 5.690 ms 5.695 ms
3 WBS-CONNECT-LLC.ae0.409.ar2.TPA1.gblx.net (64.214.147.222) 5.731 ms 5.880 ms
4 69.46.31.106 (69.46.31.106) 7.442 ms 6.667 ms
5 node1.sarorahosting.com (96.31.73.2) 15.734 ms 15.993 ms
6 96.31.73.xxx (96.31.73.xxx) 15.861 ms 15.795 ms
Now if I tracert from the VPS to the GLBX router, I get this.
traceroute to 64.214.16.65 (64.214.16.65), 30 hops max, 40 byte packets
1 node1.sarorahosting.com (96.31.73.2) 0.072 ms 0.035 ms 0.008 ms
2 69.46.31.105 (69.46.31.105) 0.731 ms 0.863 ms 1.003 ms
3 gi0-6.na21.b001841-0.tpa01.atlas.cogentco.com (38.99.204.33) 1.147 ms 1.142 ms 1.428 ms
4 gi4-1.core01.tpa01.atlas.cogentco.com (38.20.33.89) 0.818 ms 0.814 ms 0.807 ms
5 po2-0.core01.mco01.atlas.cogentco.com (154.54.27.90) 148.004 ms * *
6 po5-0.core01.jax01.atlas.cogentco.com (66.28.4.146) 5.847 ms 5.839 ms 5.872 ms
7 po5-0.core01.atl01.atlas.cogentco.com (154.54.3.197) 11.953 ms 23.819 ms 23.870 ms
8 te3-3.ccr01.atl01.atlas.cogentco.com (154.54.5.38) 11.721 ms 11.752 ms 11.787 ms
9 te8-2.mpd01.atl04.atlas.cogentco.com (154.54.3.174) 11.962 ms 11.921 ms 11.987 ms
10 ge4-1-0-390-1000M.ar4.ATL1.gblx.net (64.208.110.97) 12.252 ms 12.359 ms 12.444 ms
11 64.214.16.65 (64.214.16.65) 16.026 ms 16.061 ms 16.594 ms
I am having a strange DNS issue on a Cogent circuit using Cogent DNS servers at 66.28.0.45 and 66.28.0.61. What is happening is that some domain requests will timeout the first try. Then subsequent tries will be quick with no timeouts.
I am having a very hard time getting through to Cogent that there might be an issue somewhere and I was wondering if anyone on a Cogent line using the same Cogent DNS servers could also do a test for me to and see if you can reproduce any timeouts.
How I am testing: - Open nslookup (in linux use: nslookup -timeout=2, windows defaults to 2 seconds) - Picking a random domain name (favorite cereal.com, movie title.com, brand name.com, random word.com) - Repeating test for same domain if timeout occurs to see the next query resolve instantly
Here is an example of what Is happening for me: Code: [eger@womp ~]# nslookup -timeout=2 > superman.com ;; connection timed out; no servers could be reached > superman.com Server: 66.28.0.45 Address: 66.28.0.45#53
Non-authoritative answer: Name: superman.com Address: 64.12.47.7 > napaautoparts.com ;; connection timed out; no servers could be reached > napaautoparts.com Server: 66.28.0.45 Address: 66.28.0.45#53
I've come across an issue where our users are not logging out of their terminal services session properly. Whether via TSWeb or MSTSC (remote desktop), if they close the browser or RDP window using the x it keeps the session alive for upto 1 minute.
The problem with this is that we use terminal services to host an application for users who can't install it, so other users that login (using a generic username and password) are adopting/hijacking the original session and seeing someone elses data.
Does anyone know of a way to force a new session each time a user connects to RDP? Whether via TSWeb or MSTSC (remote desktop)?
how customers feel about being forced to use secure protocols?
For example on a cPanel server this would mean:
FTP: requires authentication over TLS SMTP: relay requires SMTP authentication over TLS. POP3: requires SSL IMAP: requires SSL cPanel: only https port enabled. WHM: only https port enabled. Webmail: only https port enabled.
Honestly, I don't think most customers would notice the difference so long as they were initially configured using secure protocols.
Combined with forcing reasonably strong passwords this should prevent a lot of iframe injection issues and SPAM related issues.
one.com (aka the worst webhost ever) are holding my domain to ransom they refuse to unlock it. Is there anyway i can go over their heads and get control of it? the address is mine, so is the phone number and email. The admin contacts are not.
Jaguarpc lock up all the VPS forcing us to upgrade. could anyone please report to Police or other authority in concern, It 's hijacking and blackmailing.
using somewhat clever techniques, I've managed to put together a script that will check various rbls, honeypots, and the like, ie: to keep the bad guys out, and the good guys in.
I've managed to put this into play on a per site basis, using simple
so that I don't have to change 500 scripts every time I want to modify it, I just change it once per server. Pretty simple there.
The problem is that I'd like to use this on a more global basis, as in putting it in apache configurations, so I don't have to load it on a per-site basis, and can catch more of what needs to be caught.
I've been a layeredtech customer since early 2005, and until this last insane price-hike fiasco, I've never had a major complaint. But now it keeps getting worse.
I wound up keeping this particular server around after the price hike (for several reasons, one of which was misinformation from a LT sales person regarding the prepay option) and several days ago received an email stating that my server would have to be moved, and that due to the chassis type of my old server, they could not move my server, I would need to migrate to a new server.
The email was less than forthcoming with details, so I tried to phone the person who sent me the email. The call went straight to his voicemail, where I left a couple messages asking him to return my calls, which he never did.
Finally I called their Sales department to figure out what was going on, and finally spoke with a nice & friendly guy (in a different department), who he stated that he felt like he was in the middle, and he just wanted to help us (the affected customers) out. Okay, I figure I can handle moving all my custom software to a new server figuring that they would find some comparable piece of hardware to move me to at the same cost.
No.
I was told I would have to pay around 10% more per month for a server with only a slightly faster CPU, only 1GB of ram and only 1 hard-drive (current server has 1.5GB of ram & 2 hard-drives mirrored)
Oh, and I have to have everything moved by the 18th of October. And I'll have to pay for 2 servers while I move. Or, I might be able to have the server moved to a different space at Savvis, but that would likely only be a short-term solution, and this situation would come up again.
I find this really appalling--they really must hate their customers who helped them through the early years!
I've been fiddling with Plesk to get HTTPS to work for [URL] .... Unfortunately I haven't had any successes at forcing HTTPS, all result in a 'to many redirects' message.
The certificate is already activated and can be verified trough; [URL] ....
I was looking at my qmail queue using qmHandle and noticed that one of the emails sitting in the queue was simply there because of a blatant typo in the email address.
Therefore, I went to the appropriate file in
/var/qmail/queue/mess/*/*
and edited the file to reflect the new email address.
Does this work at all, or should the user resend the email? I naturally don't want to look at email that isn't intended for me (which is why qmHandle is a useful tool -- because only headers are available) nor do I want someone to know that I know their email is sitting in the queue (because they might assume that I *am* reading their email even though I'm not!)
I tried qmHandle -a to no avail; the email address has been edited as per my changes, but the email is still just sitting there.
We are nearing the end of our contract with cogent and are deciding whether to continue with them. Bandcon has recently (within a last year or so) established its presence in NYC metro area.
Who would you choose among the two? Please give your input and evaluation of the two networks.
So apparently my sales rep is telling me cogent will not give me a second circuit for a redundent line so in other words, no vrrp or hsrp nothing Unless! i purchase another 200mb contract with them.
Anyone else ever have this problem?
not even are they willing to do a port fee for the second gbic i'd take up.
I have been using Cogent for many years and have always been pretty pleased with the service and bandwidth (I know many consider bottom rate/budget bandwidth). I would usually be able to call in and speak with someone who could check routing, login to switches to verify port settings, and make reverse DNS changes right then and there.
Within the last 6 months though I have been getting pretty poor support from them. Seems they are hiring more and more people just to be able to answer phones. The techs seem to have a hard time comprehending even simple reverse DNS requests and always ask me to hold for extended periods of time.
Today I called in and was even asked to hold right as they picked up the phone!! I mean, if your just going to pick up to ask me to hold, why pick up in the first place until you are ready?
I am considering getting a server from take2hosting.com. Their offer is great and sales has been very helpful and fast. Left definitely a good impression.
The downside is that they are on Cogent-only bandwidth. In the past I have really gotten something against Cogent, mainly due to one of my FDC servers being routed over Cogent and only pulling 10K/sec to Europe.
How is the Cogent network nowadays? Has it improved since a year ago? Worth considering?
From my tests the speeds are actually really great. They are located in San Jose, and I am testing speeds to Europe. For example to Surfnet Amsterdam (Cogent hands off the traffic to Surfnet in Amsterdam, so its on the Cogent network all the way) I am able to pull 2.53MB/sec. This is an incredible speed for a Westcoast<->Europe transfer. It almost makes me believe Cogent has started getting its act together.
For people who would like to test speeds, please use this test file. Especially European tests would be interesting, and it would be great if you could post where cogent hands off traffic from LosAngeles to either your network or a transit network. (In the US or Europe)
Right now I am hosting on a Level3/GlobalCrossing network @ the eastcoast. This works really well but it shows in the price. If I could combine a couple of budget boxes into one of those Quadcores it would save quite a lot. Question is: Is Cogent trustworty nowadays?
Thanks for your input
Ps. I know that hosting on a single-homed network is not the smartest thing to do. However they will add more carriers soon so this will not really be an issue. I'm expecting them to not drop Cogent tho, so my question remains
Anyone using a Cogent colocation at Marina Del Rey, CA that would care to share their experience (good or bad).
Any gotchas that we should consider ?
Considering getting a single cabinet at that location and am interested in quality and reliability of network and facilities. We rarely use remote hands so that is not much of an issue.
We use Cogent at our colo, and since this Monday (8/13/07) we've been gettin dozens of complaints from AOL users stating that connections to our sites are very, very slow and often time out.
We tested from an AOL session and were able to confirm this. We found this odd, because it came out of the blue and nothing had changed on our end. We also get excellent all-around performance from other (non AOL) connections, be it dialup or broadband.
We went ahead and did a bunch of traceroutes on the AOL session. We found things get bogged down as soon as it hits Cogent's routers in DC (timeouts / no response). These AOL sessions have no problems whatsoever with other sites and other (non cogent hosted sites) loaded fast and without issue. We then tested loading Cogent's own web site from the AOL session and saw the same sluggishness as well. The same happened when we tested a couple other Cogent client sites from AOL. They all pulled very slow (10 to 35+ secs per page) on an AOL/DSL session. This did not happen on the same broadband connection w/out AOL running on top of it. The same pages loaded very fast.
Just wondering if other Cogent clients are experiencing this? :? We have not heard from them about this, but wanted to know if this is something isolated or not.
there is anyone out there who has their infrastructure colocated in cogent owned datacenter. And how stable and secure is it. The only reason i m interested in Cogent owned colo is that they provide solid SLA.
if you can share a 100MB download link that I can use to test cogent's speed to my network. Hopefully plugged into a 100MBPS port at the switch to see if it will max out or not.
I have been searching for a solution to a problem that shouldn't exist but it does.
Background:
I have a customer on a UK server who sends emails to 500+ recipients on a monthly basis, and all but 3 emails are delivered....
The 3 that don't go, bounce after 3 days (as per the exim setup)
The 3 recipient domain's that reject don't seem to accept email from UK/European ip's and I have tried to send them emails from 4 different networks and still they bounce.
I have even tried to contact them via gmail, and still not heard back.
Proposed solution:
I want to be able to send email for that 1 domain to a Postfix Relay I have in the US.
Question:
How do I achieve this within Exim (a Cpanel Server).
I have found that so far its to do with the Router Configuration section within the Cpanel Exim setup, but I cannot seem to find an example of what and where i need to change the config...
I have an interesting situation on my CentOS 4 server. I have a number of virtual adapters (e.g. eth0:1, eth0:2 etc), and for some reason all outbound traffic is going through one of these, not eth0. If I go to ipchicken.com, it shows the ipaddress of a virtual adapter, not the normal eth0 adapter.
I have been looking around for information on how to set the default adapter to eth0, but I can't seem to find anything. I can't reboot yet, as it's a production server, so I have to wait for 'scheduled maintenance'. If that's the solution, I can try it, but I am sure there is another underlying issue/routine here.
Is there a way, while live, to set the outbound adapter back to eth0?
Please note, that I have only just realized this has happened. In fact, it has been this way since November. I can tell because server name stamps on Email messages sent from this server indicate a virtual domain at that IP address. I recall I had done some work around that time, which had involved me ifup'ing and ifdown'ing some of these adapters (but not eth0, or the eth0:100 adapter (if I recall correctly) that is now the default).
Also note that I have groups of eth0 adapters, such like: eth0:1 eth0:2 eth0:3 eth0:100 eth0:101 eth0:102
It's the eth0:100 adapter that is now the default.
We have an AWS plesk instance with around 400 domains on. All domains DNS are pointing mail to a different server and almost all domains have a contact form on their website.
the problem is, the contact forms won't work as mail is on a different server. I'm assuming that the local server thinks mail is on the server and thinks it has already been received?
is this because we need to disable incoming mail for all of these domains? if so how would we go about doing this? I tried stopping all courier-imap services but this didn't seem to work.