Sysvol issues

--------------------------------------------------------------------------------

Hey all,

I have upgraded my domain from 2000 to 2008. Everything went well except out XP clients are starting to spew userenv 1030, 1058 errors. Vista clients don't seem to have this problem. I have combed the net and tried MANY different fixes/diags. None have worked so far. The error points to "the system cannot find the path specified". What is very interesting is that when I browse to either \\DC\Sysvol or \\domain\Sysvol nothing shows up in the xp clients. everything is there in the vista clients.

Any hints??

Thanks,

Dylan
ascii_fireAsked:
Who is Participating?
 
Darius GhassemConnect With a Mentor Commented:
What AV do you have running? Can you do a netdiag then post results. Are you getting any errors on Server 2008? Make sure the clients only point to the internal DNS server and the server needs to be that way to.
0
 
ascii_fireAuthor Commented:
eTrust is our AV.  I have disable real time scan of the Sysvol on those DC's.  No DNS errors, everything resolves correctly.  No FRS errors, they are replicating to all DC's.  I can see all the polices from a vista machine, but when I browse from the xp machines the sysvol\DomainName folders is empty.\

I used dcdiag and the only error is NCSecDesc, which is in regards to RODC, which I am not using.

I have also run all the dfsdiag tests and they come back clean.
0
 
Darius GhassemConnect With a Mentor Commented:
Do you have SP3 on XP machines? There was an issue with eTrust AV with an update within a 2008 domain. Have you tried removing the AV from the clients? When you ping the domain from the clients do they get the correct IP of the DC?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
ascii_fireAuthor Commented:
The machine I am testing has SP3.  I'll try removing the AV from the clients.  I can ping the domain name fine and its correct.
0
 
ascii_fireAuthor Commented:
Actually I am using a real machine and a virtual for testing.  The virtual machine does not have any AV on it and it still shows the same errors and odd behaviors.
0
 
Darius GhassemCommented:
You can try this on the XP machines. I haven't had this issue to re-create it on 2008 domain but I believe this issue would still be fixed with the fix. The update was causing the same issue you were discribing.

http://support.microsoft.com/kb/910206/EN-US/
0
 
ascii_fireAuthor Commented:
I'm not sure that this applies to my situation.  All the scenarios deal with cross forest issues and roaming profiles.  
0
 
Darius GhassemCommented:
0
 
ascii_fireAuthor Commented:
Here are the errors.  I am logged in with an admin account on the xp machine and all permissions seem to be correct on the sysvol folders.  When I go to \\parkcounty.local\sysvol or \\soserver\sysvol (PDC) nothing shows up with the XP machine.  The same thing on vista shows all the correct files and all are the same in the 5 locations (4 DC's and then by \\domainName\sysvol).  I am using the same account on the vista machine.

Points now at max.

Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by the policy engine.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Windows cannot access the file gpt.ini for GPO CN={3A000003-562B-4EA3-8688-192E0E593EE6},CN=Policies,CN=System,DC=ParkCounty,DC=local. The file must be present at the location <\\ParkCounty.local\SysVol\ParkCounty.local\Policies\{3A000003-562B-4EA3-8688-192E0E593EE6}\gpt.ini>. (The system cannot find the path specified. ). Group Policy processing aborted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
 
ascii_fireAuthor Commented:
No go on the above two links.  
0
 
ascii_fireAuthor Commented:
By the way thank you very much for trying to help me with this issue!!!
0
 
ascii_fireAuthor Commented:
I just created a new folder in the \\domainName\sysvol folder.  It replicated to all other DC's sysvol folders.  I can only see this in XP.  So I then went to the PDC and search for the test folder.  It shows up under c:\Windowsrkcounty.local.  Most of my Domain name is there parkcounty.local.  Very Weird
0
 
ascii_fireAuthor Commented:
Actually it only replicated to the PDC.
0
 
Darius GhassemCommented:
Are you sure all of the clients are connected to the same domain? Can you do an ipconfig /all for the server, XP client, and Vista client?
0
 
ascii_fireAuthor Commented:
I am wanting to get this issue fixed so I can Migrate to the new DFSR.  Didn't want any problems during the migration process.

Maybe Migrating would fix this issue????
0
 
Darius GhassemCommented:
I don't know about that but since you are having the weird problem it might be the cause. I just can't be for sure.
0
 
Darius GhassemCommented:
0
 
ascii_fireAuthor Commented:
I've already treid all of that.  Darn.
0
 
Darius GhassemCommented:
Can you give me an ipconfig /all for XP, Server, and Vista?
0
 
ascii_fireAuthor Commented:
One thing that I have noticed on the DC's (although I can't see how it would be a problem if the Vista clients can resolve the correct location) is that when I went from 2000 to 2008 it recreated the winnt folder to Windows.  It apparently made some sort of link from winnt to windows as the winnt folder is still there.  when you try to click on the winnt folder it says winnt is not accessible access denied.  But if I type in the path c:\winnt\sysvol.  I can get to this folder and all sub folders.  

If this was the problem you would think that all machines would not be able to get to the correct location not just the xp machines.

Stumped
0
 
ascii_fireAuthor Commented:
All of the XP machines are doing this not just my test system listed below

XP - little complicated because of the Vmware stuff I have going.  
Windows IP Configuration
        Host Name . . . . . . . . . . . . : ch8
        Primary Dns Suffix  . . . . . . . : ParkCounty.local
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : ParkCounty.local

Ethernet adapter VMware Network Adapter VMnet8:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for
VMnet8
        Physical Address. . . . . . . . . : 00-50-56-C0-00-08
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.145.1
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet1:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for
VMnet1
        Physical Address. . . . . . . . . : 00-50-56-C0-00-01
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.89.1
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Cont
roller
        Physical Address. . . . . . . . . : 00-14-22-28-FD-0A
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.204.111
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        IP Address. . . . . . . . . . . . : 192.168.1.236 - THIS IS THE PRIMARY IP FOR THE NIC CARD.
        Subnet Mask . . . . . . . . . . . : 255.255.252.0
        Default Gateway . . . . . . . . . : 192.168.1.2
        DNS Servers . . . . . . . . . . . : 192.168.0.11
                                            192.168.0.21


VISTA - Same thing with the VMWare stuff

C:\Windows\system32>ipconfig -all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : ch6
   Primary Dns Suffix  . . . . . . . : ParkCounty.local
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : ParkCounty.local

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) 82566DM-2 Gigabit Network Connec
tion
   Physical Address. . . . . . . . . : 00-21-9B-45-3A-89
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.223(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 192.168.204.222(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.2
   DNS Servers . . . . . . . . . . . : 192.168.0.11
                                       192.168.0.21
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet
1
   Physical Address. . . . . . . . . : 00-50-56-C0-00-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::c8df:1cbd:60f9:e6d0%12(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.74.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet
8
   Physical Address. . . . . . . . . : 00-50-56-C0-00-08
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::788e:4d91:23c6:6a0a%14(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.130.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 6:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{9DEC5F17-518F-40E3-AC72-D7C7C45B3
D99}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{08EE7296-D889-48EE-B0C4-68D495DA4
D1C}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{93099F62-1A44-4347-BE6E-098AC6496
344}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes


Server 2008
C:\Windows\system32>ipconfig -all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : soserver1
   Primary Dns Suffix  . . . . . . . : ParkCounty.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : ParkCounty.local

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
   Physical Address. . . . . . . . . : 00-06-5B-EE-F3-33
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.0.11(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.252.0
   Default Gateway . . . . . . . . . : 192.168.1.2
   DNS Servers . . . . . . . . . . . : 192.168.0.11
                                       192.168.0.21
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection*:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{D3B58FF6-19D1-4F4D-8501-C2928C58E
6CB}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes




0
 
Darius GhassemCommented:
Yeah you would think that but did you a in-place upgrade to 2008 or a clean install?
0
 
ascii_fireAuthor Commented:
I had to do an in place upgrade.  A lot of the sites I see talk about NIC cards causing the problem.  This was a global problem though, not just certain clients.  I had some strange issues with the nics on the DCs and had to remove the adpaters and reinstall them (some times mulitple times).  The problem was that when I would put in my ips in and then go back and look at the setting (network settings only not ipcong.  Ipconfig showed the corret info) the ip and dns settings would all be 0.0.0.0.  under advanced I would see both the 0.0.0.0 and the real ip.  Very weird.  I could ping these machines via ip or host name and everything else.  Another strange issue I am having with them is that if I ping itself with host name it returns:
C:\Windows\system32>ping soserver1

Pinging soserver1.ParkCounty.local [::1] from ::1 with 3
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

Ping statistics for ::1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Again if this was the cause you would think that vista would fail too.  I have unckecked all the IPv6 settings on the DC's
0
 
Darius GhassemCommented:
When you put the CD in did it give you an upgrade option?
0
 
ascii_fireAuthor Commented:
Yes.  In fact there were several things that had to be done before that was an option.
0
 
Darius GhassemCommented:
So, is all your Servers 2008 now?
0
 
ascii_fireAuthor Commented:
All of my DC's are.  and I am runnig at a 2008 Func. level.  I still have 2000 and 2003 member servers including 2-2000 exchange servers.  Which are next for an upgrade to 2008sev/2007exch
0
 
ascii_fireAuthor Commented:
This is too weird.  I can add a new group policy and it shows up in all 5 locations \\dc\sysvol X4 and \\DomainName\sysvol.  But again only in the vista clent.  
0
 
Darius GhassemCommented:
I have multiple 2008 networks and I never had anything like this happen. Can you take a screenshoot of your DNS and post?
0
 
ascii_fireAuthor Commented:
Which part of DNS do you mean??
0
 
Darius GhassemCommented:
When you go into DNS then expand the zone.
0
 
ascii_fireAuthor Commented:
Here ya go
DNS.doc
0
 
ascii_fireAuthor Commented:
In the network and sharing center should public folder sharing be turned on??
0
 
ascii_fireAuthor Commented:
So when I create a test folder in \\server\sysvol on an xp machine.  It creates a folder on the root drive called WindowsrkCounty.local.

When I do this on a vista machine it creates it in the right place.  

How can I tell where the xp machines are resolving the sysvol location??
0
 
ascii_fireAuthor Commented:
So I decided to check so w2k machines in out domain.  They are not plagued with this problem.  Looks like only XP Clinets both SP2 and SP3.

This is so strange.
0
 
ascii_fireAuthor Commented:
Scratch that.  I think that they are also affected.  There were no error messages in the logs, but when I test browsing to the folders it behaves just like the XP Clients.
0
 
Darius GhassemCommented:
I haven't had this happen before. Are you sure you disabled IPv6 on the servers.
0
 
ascii_fireAuthor Commented:
They are all unchecked.
0
 
Darius GhassemCommented:
Try to download the client extensions then install to see if this helps.

http://www.microsoft.com/downloads/details.aspx?FamilyID=e60b5c8f-d7dc-4b27-a261-247ce3f6c4f8&displaylang=en
0
 
ascii_fireAuthor Commented:
Didn't work.
0
 
Darius GhassemCommented:
See if this helps. I still haven't been able to recreate this problem. I have been trying but I can't seem to re-create it.

http://blogs.technet.com/networking/archive/2008/07/25/netbios-browsing-across-subnets-may-fail-after-upgrading-to-windows-server-2008.aspx
0
 
ascii_fireAuthor Commented:
Looks like there is no computer browser service on any of the DC's.  I started it on the PDC and no change..  Should it be started on all of them?  I get different results of browstat status, depending on if I run it on the DC or one of the two clients (xp, vista).

Thanks,

D
0
 
Darius GhassemCommented:
You browser service should be started if you want to browse the network. Also, the computer browser should be started on a 2008 if it holds the master browser service which should be your PDC.
0
 
ascii_fireAuthor Commented:
What is strange is that I have never had trouble browsing the network.  

Still no luck.
0
 
ascii_fireAuthor Commented:
Not sure how to interprit some of the results.  I found a consol tool for browstat browcon.  It reports that I have 5 master Browsers.  One of them is my PDC and the other 4 are workstations???

It also lists 16 backup browsers all but one are member servers.
0
 
ascii_fireAuthor Commented:
Well I got an XP client to report back from browstat what looks to be a sucessful message.  I am now getting browsing is active on domain with the correct server.  

Still userenv errors.

UGHH!
0
 
Darius GhassemCommented:
You need to disable the master bowser settings in any other computer that isn't the PDC.

http://support.microsoft.com/kb/135404

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/2000/Q_21488701.html
0
 
ascii_fireAuthor Commented:
I'm not sure of the browcon util.  It reported 4 other machines as the MB.  I have changed the registry settings to not maintain a list, and reset one of the machines.  It still shows up on the list.  When I run the browstat command browstat getmaster 1 parkcounty.  it returns just the one and its correct.
0
 
ascii_fireAuthor Commented:
When I run browstat status on the PDC it returns unable to retrieve server list error 1130??

Doing this command on another DC seems to work fine.
0
 
Darius GhassemCommented:
Enable Netbios over TCP\IP on the NIC
0
 
ascii_fireAuthor Commented:
It's always been on.
0
 
ascii_fireAuthor Commented:
I GOT IT!!!!!!!!!

I'm not sure why it worked, but I ended up copying the entire folder under sysvol to the rest of the DC's and I now can see them in XP and GP are being processed.


Daruisq  Thank you so much for spending ALL this time helping me.  You get all the points!!
0
 
Darius GhassemCommented:
That is great!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.