• Recently Written

  • Deleting a local user profile on Terminal Server 2008 – Very tricky and a bit complicated than deleting it from Server 2003
  • “Because of an error in data encryption, this session will end” – error on Windows Server 2008
  • Norton Symantec Ghost Console is not displaying computers after installing remote client
  • Norton Symantec Ghost is not displaying all my machines on the console
  • Microsoft Office Outlook 2003 is not showing embedded graphics
  • bobzop.com (now colzop.com) – a possible MSN virus or spy ware
  • My Laptop Touch Pad is not working on DELL and Acer Laptop
  • Windows Vista and XP password recovery using Ophcrack

• Categories

  • Email
  • Hardware
  • password recovery
  • Security
  • Software
  • Windows Server 2008

• Archives

  • July 2010
  • May 2009
  • February 2009
  • December 2008
  • November 2008
  • September 2008
  • August 2008

• Blogroll

  • Express Your Opinion - Express yourself about anything and everything on the planet

I am using Dell PowerEdge 2950 with NetXtreme II NIC with Windows Server 2008 (not R2). It was working perfectly. I enabled RemoetApp, created RDP, also enabled Remote Desktop to allow our users to connect from anywhere. Good thing is it is still in testing environment. I didn’t have any security software installed on it so I proceeded to install whatever I had available to me which was Symantec EndPoint 64 bit edition for Windows Server 2008.
Sure enough like any other installation, the installation process went well. I ran live update with no hitch. Then it asked me to reboot. After that, I started to get the following error:
“Because of an error in data encryption, this session will end. Please try connecting to the remote computer again.” – Just like the screen shot below.

As soon as you press ok, it just closes the program. I tried it with RemoteApps, Remote Desktops and also using the RDP clients I created for each program. Trying to locate information, I came across many useful hints but mostly about Windows Server 2003.
I tried to change registry keys but none of them worked for me. If you want to try those solutions go ahead but please know that it may inadvertently cause some other issues. Then I found another solution that I wanted to try which basically talks about “Large Send Offload on IPv4.” This was a unique solution because I thought it was brilliant. So I followed the following steps:
1. Went to the server room (because I can’t connect remotely even as administrator)
2. Logged onto the Server.
3. Then find your active “Local Area Connection Status” window.
4. Click on Properties
5. Click on Advanced tab and you will see something like the screen shot below:

6.   Select Large Send Offload v2 (IPv4) and on the Value field select disable just like the screen shot below:

Press ok and you should be back in business.

Hope this helps.

An interesting Symantec Ghost Corporate Edition problem I encounter last week.

There is an older server and a newer server for Symantec Ghost for the same edition which is Version 8.0. License was migrated to the newer server on an earlier date. However the older server was still operational. When I went to uninstall remote clients from Symantec Ghost Console it uninstalled properly, but it was still visible on the console of the old server. I then proceeded to manually delete it and made sure license count was decreasing.

After that I went on to the new server’s Symantec Ghost Console and installed the remote client. It showed that it installed properly but it was not showing up on the computer list where it should. I tried to reinstall the client from the old server and it installed properly again and the machine appeared magically on the older server again. Thinking it may be just a glitch, I went on to uninstall the client from the older server and then reinstalled the newer client but still it didn’t show up.

At this point I went on the internet to see if there are any solutions. Sure enough there was NONE. Everyone is talking about different problems but not as unique as this where after installing remote client from a new Symantec Ghost Server, the remote machine does not appear on the console. After a lot of process of elimination, I thought of trying out the following steps:

1. Install remote client from the old Symantec Ghost Server Console.
2. Apply the proper DOS Template.
3. Uninstall the Client from that machine using the old Ghost Server Console.
4. Delete the machine from the old server console.
5. Log out from the Old server.
6. Disconnect the network cable for that server.
7. Log on to the new Server Console for Symantec Ghost.
8. Install the remote client on the same machine.

At this point to my surprise, the machine appeared on the new console. Who would have thought of it?

I am just sharing this just incase someone else is having the same troubles.

It was not an easy task for me to setup the Norton Symantec Ghost Server in a production environment. It is a brand new server, brand new installation, brand new Symantec Ghost but yet I was unable to see any of my machines on the domain. After fiddling around for a while found out that the subnet was not configured to handle this. Basically my server was on one subnet and all my machines were on commodity subnet. As soon as I plugged in the server onto commodity network, it started working and I was able to view all my computers.

It was not as simple as this to figure this out, but if you run into the same problem, try it out it may help you.

Here is another new issue I came across. After working on the new Symantec Ghost server for couple of weeks, we had to do some Windows Operating System updates including the server environment. Everything went smoothly as far as I was concerned. In the morning I came in and fired up the console for Symantec Ghost, and to my disbelief I saw that all my machine names are displaying something I have never seen before. All my machines turned into, “Not Known” status. Here is the screen shot.

Anyways time to scratch my head off. I tried to find some information that will help me from Symantec forum, but my problem seemed to be very unique and found no help anywhere. As a good System Admin, by the process of elimination I have implemented the following steps:

1. 1. Undo the changes done by the update.
2. Uninstall and then reinstall Symantec Ghost Console
3. Removed all the computers from the Server and then tried to re-add them.

But every time I would remove one machine it would automatically come back as, “Not Known.” I had total of 120 licenses. After a while it crossed 150 entries on my console and all are displaying, “Not Known.” Then I thought to myself, lets see what happens if I turn off all my 120 machines. Sure enough as soon as I did that it stopped generating the error.

So the only thing that came to my mind that it might be a BAD Network Card. Of course it was. One by one I started to turn them back on, and the 39th machine was the culprit. I ordered a NIC and its been working like a charm ever since.

Now I am not entirely sure if anyone will have this problem or not but just something to look for if you suddenly see all your Symantec Ghost machines are taken over by “Not Known” zombie.

Cheers.