Apexadmin
asked on
Connectivity Issues on a Win2k8 Virtual Server
I've just installed a new Windows 2008 domain. I have two HP Proliant ML350 G6s with Xeon E5520 2.26 GHz processors. Both have HP branded Window 2008 Server 64-bit installed. One server, VMHost1, has two virtual servers running, VitServ1 (Win2k8 32-bit) and Vit Serv2 (Win2k3 SP3). VMHost2 has one virtual server, VitFile (Win2k8 32-bit).
VitServ1 and VitFile are Domain Controllers.
VitFile is a file server and an AV server running Symantec Endpoint Protection Manager Version 11.0.5002.333.
There are three users in this network, all using new HP desktops running Windows XP SP3.
The users have three mapped drives, H:, P:, and U:.
The problem is that sometimes it looks like one or two mapped drives are empty. Opening the P: will seems to work, but no files will be listed. After this, if they open H:, that drive is fine but still nothing listed on P:. Rebooting seems to fix this, but it happens ramdomly to different drives, and different users/computers.
I did see a couple of errors in the event logs on the XP machines saying that the number of TCP/IP concurrent connections have been reached, but the times don't match the problem.
I also have a few of Event ID: 2012: "While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem."
I have found a similar problem related to Symanect Endpoint but it was supposedly fixed in an update, but the version I am running is later than the patched version.
This is all new equipment, from the servers, switch, cables, and desktops.
Please Help!
VitServ1 and VitFile are Domain Controllers.
VitFile is a file server and an AV server running Symantec Endpoint Protection Manager Version 11.0.5002.333.
There are three users in this network, all using new HP desktops running Windows XP SP3.
The users have three mapped drives, H:, P:, and U:.
The problem is that sometimes it looks like one or two mapped drives are empty. Opening the P: will seems to work, but no files will be listed. After this, if they open H:, that drive is fine but still nothing listed on P:. Rebooting seems to fix this, but it happens ramdomly to different drives, and different users/computers.
I did see a couple of errors in the event logs on the XP machines saying that the number of TCP/IP concurrent connections have been reached, but the times don't match the problem.
I also have a few of Event ID: 2012: "While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem."
I have found a similar problem related to Symanect Endpoint but it was supposedly fixed in an update, but the version I am running is later than the patched version.
This is all new equipment, from the servers, switch, cables, and desktops.
Please Help!
Hazem KUNNANA
Be sure that you are not mapping the drives on the same server using different credentials.
ASKER
Nope, all three drives are mapped via a logon script (batch file)
Have u checked security permission on all three drives you need to click on individual drive and check the settings for sharing and security make sure list folders and sub folders are ticked.
The mojority of issues in win2008 when files folders drivers ate not listed is to do with sharing and security
The mojority of issues in win2008 when files folders drivers ate not listed is to do with sharing and security
ASKER
The share permissions are set for full control for the everyone group and the users group I created for all corporate users. The security permissions are set for full control on the corp users group on two of the directories and full control for the individual users on their home drives.
Ok what happens when you run script manually have you tried that ?
Also from client PC go through network to the server and tell me if you can see the folders their which are assigned to drive and try to access them see if you can access P drive from their and folerds are listed
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Is this a quadport nic in your server ?
can you shutdown all your vms, delete your hyper-v virtual network
delete the nics from your device manager
restart your physical host, let it detect the nics itself - then create your virtual network
or update your nics to the latest drivers from the vendor if the OS doesn't detects the nics automatically.
you should also test your network after disabling or removing symantec completely and observe
can you shutdown all your vms, delete your hyper-v virtual network
delete the nics from your device manager
restart your physical host, let it detect the nics itself - then create your virtual network
or update your nics to the latest drivers from the vendor if the OS doesn't detects the nics automatically.
you should also test your network after disabling or removing symantec completely and observe