How does a hosting provider differentiate between network and server uptime.
In Serverpoint.com Policies I read that they offer 99.95% uptime guarantee
We guarantee that 99.95% of the time your web site will be accessible via IP address to the world.
Just looking for opinions on uptime guarantees. Does anyone actually look at those guarantees anymore? Or is it just assumed that every host now a days is up 99.9% of the time.
The reason I ask is that it appears that every host has one, but I haven't really ever experienced one myself.
I recently signed up for a VPS server with VolumeDrive. I am going to be launching a large website in less than a month and right now I just have a Coming Soon page and a Wordpress blog. My response time is really poor. It takes about 10 sec to pull up my blog and I have complained. They told me that they are going to move me to another server shortly.
Do hosting companies guarantee performance in a VPS environment? I know you are sharing the physical server with other VPS servers so what is to say that this new server will not have the same problem? I thought providers were able to set bandwidth/system limits on VPS servers to stop this from happening? Do you recommend that I just take the expense and go dedicated or should I look into moving to a different hosting provider?
There are many of us who choose web hosting services for their website based on a number of factors like price, web space provided, server uptime etc. Honestly any web hosting package which provides about 5 GB of web space under US $20 per month is fine to me. And of course most web hosting companies will tell you that they provide 99.9% uptime which honestly is not lived up to by 90% of the companies out there. Any technical person can tell you that there are large numbers of issues that creep up while running a web hosting service which makes it very difficult to actually provide 99% uptime.
For me, the single most important aspect of a web hosting service is its support and what kind of guarantee they give on their technical and customer support. Things can go wrong in any service, but how fast you rectify it is the most important thing. And not just that, website owners have different technical levels. Some might need help for the most basic features while some would require more complex support for the databases, scripts etc.
A good web hosting company would always provide 1 hour support guarantee to you for your queries. Even if a query is complex and the support staff needs to consult their administrators, programmers etc, it is always nice for a customer to be updated of what is going on and whether they can solve it immediately or after consultation with various people working in the web hosting company.
It can be very irritating for you if have opened a support ticket and next thing you know its been hours or even days before anyone has bothered to respond to you and all you have got is an automated response. Obviously once you open a support ticket, you do get an automated response saying your query has been received but I always look out for in how much time do I receive the second automated response telling me a member of the support staff has checked your query and replied to it. That shows the competence level of the web hosting company and how much they actually care about their customers.
In conclusion, whether you are looking for a web hosting service for your new website or are looking to transfer web hosts, make sure you check whether the service offers a 1 hour support guarantee on their website. Don't be fooled with offers of web space, email accounts or even uptime guarantees. It's the support that will make the big difference in your web hosting experience.
I signed up with La(m)nehost not a short while back, I now wanted to make use of the guarantee since i'm not happy with there service.
I issued a ticket the 27th december 2008, requesting my money back since I wasn't happy with there services and they offer a 60back not-happy-money-back guarantee.
Till this very day it seems as Lanehost is REFUSING to respond to the ticket! I asked about the issue on the chat and just got a lame answer "you should log a ticket"...
What can I do against this? I paid around 150dollar for a year (stupid enough).
I was about to start my own hosting company, and this just sets me back alot.
Before i start i would just like to mention i had this problem about 8-10 months ago but fought this would be useful to share.
I bought the hostgator swamp shared hosting package for a website me and my friend were going to make.
Long story short my friend didnt have to much time in his hands so pulled out so a was left with hosting that i didnt need, so about 30-35 days in i cancelled the account, Hostgator claim that if you cancel your account with them no more than 45 days being with them the will issue a full refund.
I waited the full 3-5 business days they say it takes to issue the refund, I never recieved that refund, i gave them another week still no sign of the money.
After numerous chats with live operaters and opening tickets, i still hadn't got anywhere, live operaters where giving me coupons to make up for the refund ( but thats still not good enough ) and the operaters answering the tickets were saying they had issued the refund.
I just decided to forget about it.
The service was good though in that period of time they, such as changed my main domain name for me for free because i was a new customer.
I'm curious to see who here runs time services for their network / their machines. Also, if you do run time services, do you use a Stratum 0 time source (GPS, WWVB, DCF77, CDMA, et al) or do you just sync with pool.ntp.org? Is your NTP server in pool.ntp.org?
What I'm really curious to find out is if anyone here provides stratum 1 time sources (a time source that is directly sync'd to an external reference clock, like a GPS).
I noticed that there are huge pings to my server from time to time, example:
------------------ 64 bytes from HOSTNAME (server-IP): icmp_seq=0 ttl=60 time=2.93 ms 64 bytes from HOSTNAME (server-IP): icmp_seq=1 ttl=60 time=2.70 ms 64 bytes from HOSTNAME (server-IP): icmp_seq=2 ttl=60 time=1901 ms 64 bytes from HOSTNAME (server-IP): icmp_seq=3 ttl=60 time=899 ms 64 bytes from HOSTNAME (server-IP): icmp_seq=5 ttl=60 time=2.69 ms 64 bytes from HOSTNAME (server-IP): icmp_seq=6 ttl=60 time=2.62 ms 64 bytes from HOSTNAME (server-IP): icmp_seq=4 ttl=60 time=2132 ms 64 bytes from HOSTNAME (server-IP): icmp_seq=8 ttl=60 time=2.57 ms 64 bytes from HOSTNAME (server-IP): icmp_seq=7 ttl=60 time=1190 ms 64 bytes from HOSTNAME (server-IP): icmp_seq=10 ttl=60 time=2.65 ms 64 bytes from HOSTNAME (server-IP): icmp_seq=9 ttl=60 time=1048 ms 64 bytes from HOSTNAME (server-IP): icmp_seq=12 ttl=60 time=2.74 ms 64 bytes from HOSTNAME (server-IP): icmp_seq=11 ttl=60 time=1205 ms ------------------
First I thought that it is network related, but most strange for me was that I did not have any packets lose.
Then I tried to ping from my server to other hosts - situation was the same - some ping were good and some were huge (700ms, 800ms, even 2000ms)
I checked: cat /proc/sys/net/ipv4/netfilter/ip_conntrack_max and it was 65536
Then I checked: cat /proc/sys/net/ipv4/netfilter/ip_conntrack_count and it was ~1600 so normal.
I did not have such dropped information on all my other servers. Dropped counter for RX was constatnly increasing.
So I decided to restart all services on the server. After restarting network and ipaliases - problem disappeared. RX dropped counter is still rising, but I do not have any slowdowns on the server and pings are normal.
My question is - does anyone could have any idea what can casue my problem and how can I prevent this in the future?
I am wondering how powerful of a computer/server I'm going to need for a project for work.
The server will only be accessible over the companies LAN, it will most probably need to be running Windows, because that's what the rest of the system runs. Even though I'd rather have it Linux. The server will be running Apache, PHP, and MySQL.
It will need be accessed by around 100-200 workstations (200 on the far out side max).
They don't need to write to the database. Just read. So possibly only 1 to 2 MySQL queries per page. PHP will be of course used to generate the pages.
So how powerful of a server that's just dedicated to this would be needed?
I realize this might not be the right forum for this, but the people here are so helpful
I have have Two Apache Webserver in One Network On one Static Ip. Both Apache Severs are installed on Ubuntu 12.04.First Webserver Setup hostname apache, domain name test.com.On this web server i Run My Website,Email, And 2 Php Webapps.last night i setup a second separate(own pc) apache Server(ubuntu 12.04) as a Cloud Server.(own cloud) hostname cloud, domain name cloud.test.com..my question is how can access both server via port 80 from the world.Right now i only can access Server 1 from the web.
I nat port 80 to both static lan adresses in the network.I use (pfsense) for the router.i try to reach my Second Server with cloud.test.com
For a server that use many virtual network interfaces (IP ranges) there is any posibility to find that 2 IP's from different IP ranges are pointing to same machine server?
I'm kind of annoyed. Not so much the server outage; I know those happen.
What is annoying me is the inability to get anyone on the phone.
I've been calling each of their 4 numbers in succession for the last 45 minutes. Finally connected with someone who has no idea what's going on, only that it is allegedly affecting their entire customer base. Man, if you're not going to answer the phone, at least put on a voice message, or maybe a banner on your Account Manager page.
their site didn't go down, just the ones they are hosting.
I'm a newbie at this so, for the vets, if you are experiencing a server outage, how long do you give your hosting company to give you an answer before getting "assertive" on the phone.
It's not a big deal to me since currently I only use my site for email. However, there must be some folks losing a bit of cash by being out of commission for an extended period of time.
I'm trying to setup a VPN server on windows 2003 standard. It suppose to work like this if configuration is correct: the server will have 20 static public IP addresses, each of my workstations will use one of the 20 IPs to connect to the server, then connect to the internet with the same IP it connects to the server. So if I do a IP lookup, each workstation will show a different public IP but the server will always assign the same IP to the same workstation.
Now all my workstations can connect to the server with any of the IPs I have, and they can surf the internet with no problems at all. However, if I do a IP lookup, every workstation shows the same pubilc IP which is totally not what I wanted. I have searched google and not much useful infor come up. Can any of the experts here help me out?
I am going to setup our new database server (call it beta) in our data center. Previously we only had one server (call it alpha) which was web, email, ftp, dns, and database. Beta is taking over alphas database duties. We have a Sonicwall router/firewall as our main connection access point.
I am trying to decicde if we should simply connect alpha and beta together locally via a gigabit crossover cable, or if I should connect beta into our sonicwall router/firewall.
Beta does not need to be outside accessible at all. So if I connect beta to the sonicwall I simply would not open any ports.
What do you guys think is best for performance and the overall right way to do it.
I current have a VPS hosted with a host who rent racks from Gyron.net at Telstra Londong Hosting Center Datacenter (Docklands) and im very satisfied with the network but im looking to change hosts, so im looking to find hosting companies that also rent racks/network from Gyron.net.
So does anyone knows hosting companies that rent space/racks/network from Gyron.net?
Any security risks with setting up server on home network? I would like to set up a computer running linux or xp as a computer on our home network. We have about 3 other computers on the same network.
My network manager says that it would be a security risk to the other computers on the network if I were to have the server running on the network. The server would be connected to a netgear wireless router and I would have ports 80 and 21 opened just for the internal ip address of the server. (for example, the server is on 192.168.0.3, and I had just the two ports open for it, while there were computers on 192.168.0.2 and 192.168.0.4).
The netgear router has a firewall built into it. Each of the other computers on the network have software firewalls. I would not have a firewall on the server, and I really don't care if someone hacks it. So, what at worst could happen? Would the other computers be at risk?
If you are a professional, I want your opinion also.
There are several methods of offering network path redundancy. The basic decision for me has come down to:
Do it at Layer 2 Do it at Layer 3
At the moment we have layer 2 redundancy to each server. 2NICs on the server up with one having the IPs for apache/mysql/etc. each nic going into a seperate switch and the switches connected together, with 2 routers running VRRP to handle the gateway. Everything is Vlaned.
So basicaly the switch redundancy is done by spanning tree and the IP redundancy is done with a process on the router/server to move the IP to the other router/server NIC if there is an issue.
I am thinking about going with 2 fully seperate networks. in differant subnets. where each router would have a gateway. the routers would talk to each other and they would speak OSPF or ISIS with the servers. This way I would move hosting onto loopback IPs on the servers and those loopback IPs would be advertised to the both routers through seperate networks. Again everything would be Vlanned.
This has the advantage of getting rid of spanning tree which has caused issues from time to time. It would keep redundancy up and we could standardize on the routing daemon ran on the servers allowing all of the various OSs we run to have the same basic config for network redundancy. Where now each OS tends to have its own solution. This would make life easier from a config and troubleshooting point of view.
We are facing this weird problem from the past few days. Whenever we reboot the Windows 2003 Service, the server becomes inaccessible from the network or the internet after reboot. It is only after we run the sharedaccess.reg file available from http://windowsxp.mvps.org/reg/sharedaccess.reg and reboot the server, we can access the server remotely. But the same thing happens after rebooting the server again. We are also not able to start the Windows Firewall service. We get an error while trying to start the Windows Firewall Service. The screenshot of the error message is attached with this post.
Is there a good dedicated server company that has fast guaranteed turn ups, allows colocation, a private network, and is outside the midwest?
I want to colo my database server(s), firewalls, and switches but then use dedicated servers as web servers. Hopefully allowing me to add web servers very quickly as needed (someone getting /.'d). I would want the webservers on a private network only.