I have been a loyal customer of yours since the dial-up days of Worldnet. I write this letter to congratulate your company for being so successful that you no longer need me as a customer nor need my money which you have dutifully taken without fanfare from for the past 17 years.
If you are still reading this, I'm amazed because that's not the attitude the majority of your Customer Support conveys. My recent issues started when we decided to go with a 3rd party VoIP solution and port our existing number to that company. My wife called your Customer Support at least 2 weeks prior to ask if it was possible to port the number and keep our existing DSL connection. She was told there would be no issues. Well, obviously, there is or I wouldn't be writing this letter.
Our number was ported and my DSL was disconnected leaving me without service. When I called to check on this issue the next day I was told there was no more DSL capacity and my service could not be reinstated. At this point, I was left with no options from AT&T- no DSL and no Uverse in my area.
My case was escalated and I was told very coldly, "there is nothing we can do for you!" Obviously, this was very frustrating to me since I did not ask for my DSL connection to be terminated and was advised there would be no issues.
1. To ask me why I am not satisfied with the current service and how AT&T could keep me as a dial tone customer.
2. To protect me as your customer and ensure I authorized the porting of my number and was not being taken advantage of by another carrier to steal your business.
3. To warn me that if I go through with the porting that I would not only have an interruption in Internet service but it would be terminated with NO option for reconnection from AT&T.
In retrospect, I wonder if your "at capacity" status is reason for some of the service issues I've had over the past years?
In closing, I guess this incident is a blessing. You will not be burden with needing to add my meager monthly payment to your profits. There is probably nothing you could do to bring me back as a customer (and you probably feel you don't need me) but I hope in some way this incident will flag someone in your large organization who will be able to help the next customer with similar issues.
Thank you for your time. Please excuse me while I research cell carriers to switch my family's 4 cell phones to.
This same scenario worked on XenServer 6.0.2. After check the usual stuff (i.e. interface configs, default routes, VM settings, etc), I found the issue to be with the Promiscuous Mode setting of the VMWare vSwitch. The default setting is 'Reject'. Setting to 'Accept' as shown below allows traffic to flow.
A reboot of the VMware host or the VM guests were not necessary when making the setting change above.
With WatchGuard dropping the support on the WatchGuard x500 Firebox product in September 2009 you may find yourself configuring a new WatchGuard. We recently purchased a WatchGuard Firebox Core x550e. There is good news and bad new.
1.On the x500 Policy Manager, click File | Backup and save the backup to an XML file.
2. On the x550e Policy Manager, click File | Restore and load the XML from step 1.
3. On the x550e Policy Manager, click Network | Configuration and click Yes to the message concerning whether you want to change from a 6 interface Firebox to a 4 interface Firebox. If you don't do this, you will receive a DATA_ERROR concerning the interfaces when attempting to save the the firebox in the next step.
4. On the x550e Policy Manager, click File | Save > To Firebox.
5. You should know have the policies from the x500 on the new x550e Firebox.
I recently found myself with the need to set a WatchGuard Firebox x550e to the factory default. If you've ever had to do this for any WatchGuard Firebox product you know there are different procedures depending upon which Firebox you have. This WatchGuard support article details how to do a factory default of a Firebox X Core or Peak e-Series and non e-Series.
At some point you might need to setup a VM using an ISO file. This post shows how to setup a file share for use by XenServer.
1. Within XenServer, click Storage | New Storage Repository.
2. Click the Windows File Sharing (CIFS) radio button and click next.
3. Enter the desired name and share name. Click Finish.
4. The new repository (CIFS ISO library) is displayed in the left-hand pane of XenCenter with details on the right-hand-side.
5. Now you can use the ISOs on this Windows Share to setup your VM by changing the DVD drive setting to the desired ISO.