Prev: Connect to my company's application sharing server missing in
Next: Blocked by cbl.abuseat.org
From: Richard K on 26 May 2010 22:20
I have been through the gpupdate /force part from the server and this is a
brand new server. I have suspicions that it may be more of a network issue
since we had some problems with an older server through the years it was in
service. What I do know is that it is frustrating for the users and rolling
down to me. I still say this wreaks of a switch issue. This client is only
a count of 14 with 1 SBS 2008 server just recently installed. on this new
Dell server. It's packed with the latest and greatest including 16gb RAM so
I'm confident he is running well.

There is only 1 internal switch... Netgear 24port 100/1000 switch. I have a
24port 10/100 switch that I am going to swap out just to see if it makes a
difference. Because all users are experiencing this at the same time and
the fact that I have not faced this same issue on any other SBS 2008
network... the switch is still the only wild card.

let me ask one more question.... if the printers and drive maps are applied
via gp preferences why would they go away if a network connection drops?
Does the gp need to be live all of the time or is it I am just happening on
one of those 90 minute GP updates from the server that all clients see at
the same time and things are timing out with the server because of bad
connection issues?

By chance to cover all bases... has anyone seen any issues with service pack
updates on the server clients that may be causing the problem?

Thanks!

-Richard K


"Larry Struckmeyer[SBS-MVP]" <lstruckmeyer(a)mis-wizards.com> wrote in message
news:4e68351513c7a8cccac5a4692f6d(a)news.microsoft.com...
> "After a few minutes" either to lose or to reappear is not exactly what I
> would expect if it were a GP issue. Policies are applied at the refresh
> cycle for GP, which is 90 minutes by default.
>
> This is a clue, if *not* 90 minutes that the GP is ok, it is the network
> connectivity that is failing. My guess would be the switch or the NIC in
> the SBS, since it affects all clients at the same time.
>
> You could also try gpupdate /force from a command prompt of one of the
> stations to see if that restores the mappings. If intermittent
> connectivity is the issue it should fail, fail, fail, then succeed as the
> connections are restored.
>
> -
> Larry
> Please post the resolution to your
> issue so others may benefit
> -
> Get Your SBS Health Check at
> www.sbsbpa.com
>
>
>> Ok, makes sense that I need to look at it from more of a client issue.
>> The current gp does the drive mappings and printer mappings and when
>> they are lost it's everything (all drives disappear and all printers
>> disappear) and when it happens to one user it's happening to other
>> users as well which does wreak of intermittent network issues. After
>> a few minutes they end up all coming back.
>>
>> I'm confident the network settings are good because I have very
>> similar setups at other server environments so I'm wondering if I have
>> a switch issue. Because this is intermittent it's going to make it
>> that much harder to diagnose. Thoughts on where to start and what to
>> look at?
>>
>> -Richard
>>
>> "Cliff Galiher - MVP" <cgaliher(a)gmail.com> wrote in message
>> news:636EB961-95EB-4CFF-B093-55550E3ADF80(a)microsoft.com...
>>
>>> A key concept to keep in mind with these types of situations is that
>>> group policies are (And have to me, if you think about it logicially)
>>> applied by the client. In other words, the client reads the group
>>> policy from the server and then applies it. If a problem occurs, the
>>> client *attempts* to report the problem back to the server, but there
>>> is no gaurantee that this will succeed if the problem that caused the
>>> group policy in the first place still exists.
>>>
>>> In other words, although the SBS logs can be somewhat helpful, when
>>> it comes to group policies, the logs that matter are the clients.
>>> When printers or drive mappings are failing, especially if the
>>> problems are intermittent, the problem is almost always network
>>> related. The server will get the report that the problem failed, but
>>> since the server did not try to initiate contact with the actual
>>> fielshare or printer via SMB, the nserver is not able to report with
>>> any detail what went wrong.
>>>
>>> Look to your clients and make sure all of your network settings are
>>> in order.
>>>
>>> -Cliff
>>>
>>> "Richard K" <rkokoski(a)foxdtechllc.com> wrote in message
>>> news:OAOw8YD$KHA.980(a)TK2MSFTNGP04.phx.gbl...
>>>
>>>> SBS2008
>>>> Win XP Pro + Windows 7 Pro clients
>>>> I have successfully implemented GP policies for mapping drivers,
>>>> printers and shortcut shares. Things have been working fine until
>>>> yesterday. Now users are reporting to me that randomly their drives
>>>> and printer maps are appearing/disappearing. When I look into the
>>>> SBS2008 Application log I'm getting Event ID 4098 popping up with
>>>> the source being Group Policy Drive Maps or Group Policy Printers.
>>>> Below is the text of the Application log event. I did some research
>>>> and am reading about an issue popping up with a recent .NET update
>>>> on the server which could make sense.
>>>>
>>>> Users are frustrated and it is killing their production. Has anyone
>>>> else encountered this?
>>>>
>>>> -Richard K
>>>>
>>>> Log Name: Application
>>>> Source: Group Policy Printers
>>>> Date: 5/25/2010 1:48:26 PM
>>>> Event ID: 4098
>>>> Task Category: (2)
>>>> Level: Warning
>>>> Keywords: Classic
>>>> User: SYSTEM
>>>> Computer: CMASERVER.cma.local
>>>> Description:
>>>> The user 'fax' preference item in the 'CMA - Deploy Printer Policy
>>>> {2C696556-F13A-4691-899E-5CB5C0AAA798}' Group Policy object did not
>>>> apply
>>>> because it failed with error code '0x8007007b The filename,
>>>> directory
>>>> name, or volume label syntax is incorrect.' This error was
>>>> suppressed.
>>>> Event Xml:
>>>> <Event
>>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>>> <System>
>>>> <Provider Name="Group Policy Printers" />
>>>> <EventID Qualifiers="34305">4098</EventID>
>>>> <Level>3</Level>
>>>> <Task>2</Task>
>>>> <Keywords>0x80000000000000</Keywords>
>>>> <TimeCreated SystemTime="2010-05-25T17:48:26.000Z" />
>>>> <EventRecordID>1624865</EventRecordID>
>>>> <Channel>Application</Channel>
>>>> <Computer>CMASERVER.cma.local</Computer>
>>>> <Security UserID="S-1-5-18" />
>>>> </System>
>>>> <EventData>
>>>> <Data>user</Data>
>>>> <Data>fax</Data>
>>>> <Data>CMA - Deploy Printer Policy
>>>> {2C696556-F13A-4691-899E-5CB5C0AAA798}</Data>
>>>> <Data>0x8007007b The filename, directory name, or volume label
>>>> syntax
>>>> is incorrect.</Data>
>>>> </EventData>
>>>> </Event>
>>>> Log Name: Application
>>>> Source: Group Policy Drive Maps
>>>> Date: 5/25/2010 1:48:26 PM
>>>> Event ID: 4098
>>>> Task Category: (2)
>>>> Level: Warning
>>>> Keywords: Classic
>>>> User: SYSTEM
>>>> Computer: CMASERVER.cma.local
>>>> Description:
>>>> The user 'Q:' preference item in the 'CMA - Map Drives Policy
>>>> {7B6BBF47-EB1E-45D2-8696-07A168FD580D}' Group Policy object did not
>>>> apply
>>>> because it failed with error code '0x80070035 The network path was
>>>> not
>>>> found.' This error was suppressed.
>>>> Event Xml:
>>>> <Event
>>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>>> <System>
>>>> <Provider Name="Group Policy Drive Maps" />
>>>> <EventID Qualifiers="34305">4098</EventID>
>>>> <Level>3</Level>
>>>> <Task>2</Task>
>>>> <Keywords>0x80000000000000</Keywords>
>>>> <TimeCreated SystemTime="2010-05-25T17:48:26.000Z" />
>>>> <EventRecordID>1624864</EventRecordID>
>>>> <Channel>Application</Channel>
>>>> <Computer>CMASERVER.cma.local</Computer>
>>>> <Security UserID="S-1-5-18" />
>>>> </System>
>>>> <EventData>
>>>> <Data>user</Data>
>>>> <Data>Q:</Data>
>>>> <Data>CMA - Map Drives Policy
>>>> {7B6BBF47-EB1E-45D2-8696-07A168FD580D}</Data>
>>>> <Data>0x80070035 The network path was not found.</Data>
>>>> </EventData>
>>>> </Event>
>
>
From: Cliff Galiher - MVP on 27 May 2010 04:16
I'll be blunt; I'm not going to go into the speculation game of what
specifically could cause the printers to disappear. Suffice it to say that
there are a lot of moving parts, I can tell you the process that the OS uses
to apply those group policies and then, instead of speculating, the best
thing to do is apply some analytical troubleshooting. This is a core skill
any IT pro needs and it cannot be taught. 'nuf said on that subject.

To answer your second question, I have a variety of environments running SBS
and non-SBS servers, with XP, Vista, and Win7 clients. I have not seen a
specific update or service pack combination that breaks this functionality.
Since there are literally thousands of possible such configurations, I can't
say definitively that one does not exist, but it isn't one I've seen. More
specifically, I certainly have several environments where all OS's are
"current" and that definitely works.

This is likely not software/OS but is more likely hardware or driver
related.

-Cliff


"Richard K" <rkokoski(a)foxdtechllc.com> wrote in message
news:#lc7lMU$KHA.1448(a)TK2MSFTNGP06.phx.gbl...
> I have been through the gpupdate /force part from the server and this is a
> brand new server. I have suspicions that it may be more of a network
> issue since we had some problems with an older server through the years it
> was in service. What I do know is that it is frustrating for the users
> and rolling down to me. I still say this wreaks of a switch issue. This
> client is only a count of 14 with 1 SBS 2008 server just recently
> installed. on this new Dell server. It's packed with the latest and
> greatest including 16gb RAM so I'm confident he is running well.
>
> There is only 1 internal switch... Netgear 24port 100/1000 switch. I have
> a 24port 10/100 switch that I am going to swap out just to see if it makes
> a difference. Because all users are experiencing this at the same time
> and the fact that I have not faced this same issue on any other SBS 2008
> network... the switch is still the only wild card.
>
> let me ask one more question.... if the printers and drive maps are
> applied via gp preferences why would they go away if a network connection
> drops? Does the gp need to be live all of the time or is it I am just
> happening on one of those 90 minute GP updates from the server that all
> clients see at the same time and things are timing out with the server
> because of bad connection issues?
>
> By chance to cover all bases... has anyone seen any issues with service
> pack updates on the server clients that may be causing the problem?
>
> Thanks!
>
> -Richard K
>
>
> "Larry Struckmeyer[SBS-MVP]" <lstruckmeyer(a)mis-wizards.com> wrote in
> message news:4e68351513c7a8cccac5a4692f6d(a)news.microsoft.com...
>> "After a few minutes" either to lose or to reappear is not exactly what I
>> would expect if it were a GP issue. Policies are applied at the refresh
>> cycle for GP, which is 90 minutes by default.
>>
>> This is a clue, if *not* 90 minutes that the GP is ok, it is the network
>> connectivity that is failing. My guess would be the switch or the NIC in
>> the SBS, since it affects all clients at the same time.
>>
>> You could also try gpupdate /force from a command prompt of one of the
>> stations to see if that restores the mappings. If intermittent
>> connectivity is the issue it should fail, fail, fail, then succeed as the
>> connections are restored.
>>
>> -
>> Larry
>> Please post the resolution to your
>> issue so others may benefit
>> -
>> Get Your SBS Health Check at
>> www.sbsbpa.com
>>
>>
>>> Ok, makes sense that I need to look at it from more of a client issue.
>>> The current gp does the drive mappings and printer mappings and when
>>> they are lost it's everything (all drives disappear and all printers
>>> disappear) and when it happens to one user it's happening to other
>>> users as well which does wreak of intermittent network issues. After
>>> a few minutes they end up all coming back.
>>>
>>> I'm confident the network settings are good because I have very
>>> similar setups at other server environments so I'm wondering if I have
>>> a switch issue. Because this is intermittent it's going to make it
>>> that much harder to diagnose. Thoughts on where to start and what to
>>> look at?
>>>
>>> -Richard
>>>
>>> "Cliff Galiher - MVP" <cgaliher(a)gmail.com> wrote in message
>>> news:636EB961-95EB-4CFF-B093-55550E3ADF80(a)microsoft.com...
>>>
>>>> A key concept to keep in mind with these types of situations is that
>>>> group policies are (And have to me, if you think about it logicially)
>>>> applied by the client. In other words, the client reads the group
>>>> policy from the server and then applies it. If a problem occurs, the
>>>> client *attempts* to report the problem back to the server, but there
>>>> is no gaurantee that this will succeed if the problem that caused the
>>>> group policy in the first place still exists.
>>>>
>>>> In other words, although the SBS logs can be somewhat helpful, when
>>>> it comes to group policies, the logs that matter are the clients.
>>>> When printers or drive mappings are failing, especially if the
>>>> problems are intermittent, the problem is almost always network
>>>> related. The server will get the report that the problem failed, but
>>>> since the server did not try to initiate contact with the actual
>>>> fielshare or printer via SMB, the nserver is not able to report with
>>>> any detail what went wrong.
>>>>
>>>> Look to your clients and make sure all of your network settings are
>>>> in order.
>>>>
>>>> -Cliff
>>>>
>>>> "Richard K" <rkokoski(a)foxdtechllc.com> wrote in message
>>>> news:OAOw8YD$KHA.980(a)TK2MSFTNGP04.phx.gbl...
>>>>
>>>>> SBS2008
>>>>> Win XP Pro + Windows 7 Pro clients
>>>>> I have successfully implemented GP policies for mapping drivers,
>>>>> printers and shortcut shares. Things have been working fine until
>>>>> yesterday. Now users are reporting to me that randomly their drives
>>>>> and printer maps are appearing/disappearing. When I look into the
>>>>> SBS2008 Application log I'm getting Event ID 4098 popping up with
>>>>> the source being Group Policy Drive Maps or Group Policy Printers.
>>>>> Below is the text of the Application log event. I did some research
>>>>> and am reading about an issue popping up with a recent .NET update
>>>>> on the server which could make sense.
>>>>>
>>>>> Users are frustrated and it is killing their production. Has anyone
>>>>> else encountered this?
>>>>>
>>>>> -Richard K
>>>>>
>>>>> Log Name: Application
>>>>> Source: Group Policy Printers
>>>>> Date: 5/25/2010 1:48:26 PM
>>>>> Event ID: 4098
>>>>> Task Category: (2)
>>>>> Level: Warning
>>>>> Keywords: Classic
>>>>> User: SYSTEM
>>>>> Computer: CMASERVER.cma.local
>>>>> Description:
>>>>> The user 'fax' preference item in the 'CMA - Deploy Printer Policy
>>>>> {2C696556-F13A-4691-899E-5CB5C0AAA798}' Group Policy object did not
>>>>> apply
>>>>> because it failed with error code '0x8007007b The filename,
>>>>> directory
>>>>> name, or volume label syntax is incorrect.' This error was
>>>>> suppressed.
>>>>> Event Xml:
>>>>> <Event
>>>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>>>> <System>
>>>>> <Provider Name="Group Policy Printers" />
>>>>> <EventID Qualifiers="34305">4098</EventID>
>>>>> <Level>3</Level>
>>>>> <Task>2</Task>
>>>>> <Keywords>0x80000000000000</Keywords>
>>>>> <TimeCreated SystemTime="2010-05-25T17:48:26.000Z" />
>>>>> <EventRecordID>1624865</EventRecordID>
>>>>> <Channel>Application</Channel>
>>>>> <Computer>CMASERVER.cma.local</Computer>
>>>>> <Security UserID="S-1-5-18" />
>>>>> </System>
>>>>> <EventData>
>>>>> <Data>user</Data>
>>>>> <Data>fax</Data>
>>>>> <Data>CMA - Deploy Printer Policy
>>>>> {2C696556-F13A-4691-899E-5CB5C0AAA798}</Data>
>>>>> <Data>0x8007007b The filename, directory name, or volume label
>>>>> syntax
>>>>> is incorrect.</Data>
>>>>> </EventData>
>>>>> </Event>
>>>>> Log Name: Application
>>>>> Source: Group Policy Drive Maps
>>>>> Date: 5/25/2010 1:48:26 PM
>>>>> Event ID: 4098
>>>>> Task Category: (2)
>>>>> Level: Warning
>>>>> Keywords: Classic
>>>>> User: SYSTEM
>>>>> Computer: CMASERVER.cma.local
>>>>> Description:
>>>>> The user 'Q:' preference item in the 'CMA - Map Drives Policy
>>>>> {7B6BBF47-EB1E-45D2-8696-07A168FD580D}' Group Policy object did not
>>>>> apply
>>>>> because it failed with error code '0x80070035 The network path was
>>>>> not
>>>>> found.' This error was suppressed.
>>>>> Event Xml:
>>>>> <Event
>>>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>>>> <System>
>>>>> <Provider Name="Group Policy Drive Maps" />
>>>>> <EventID Qualifiers="34305">4098</EventID>
>>>>> <Level>3</Level>
>>>>> <Task>2</Task>
>>>>> <Keywords>0x80000000000000</Keywords>
>>>>> <TimeCreated SystemTime="2010-05-25T17:48:26.000Z" />
>>>>> <EventRecordID>1624864</EventRecordID>
>>>>> <Channel>Application</Channel>
>>>>> <Computer>CMASERVER.cma.local</Computer>
>>>>> <Security UserID="S-1-5-18" />
>>>>> </System>
>>>>> <EventData>
>>>>> <Data>user</Data>
>>>>> <Data>Q:</Data>
>>>>> <Data>CMA - Map Drives Policy
>>>>> {7B6BBF47-EB1E-45D2-8696-07A168FD580D}</Data>
>>>>> <Data>0x80070035 The network path was not found.</Data>
>>>>> </EventData>
>>>>> </Event>
>>
>>
From: Larry Struckmeyer[SBS-MVP] on 27 May 2010 06:42
gpupdate is a command to update the local station, that is the station from
which you issue the command. It does not "push" the update down to the stations.
The force part is to cause the local station to refresh the policy regardless
of the version number in the policy, as by default matching versions are
not updated but skipped over.

That this is a new server is, for me at least, new info, and as such I suggest
you run the SBS BPA and fix anything it finds. Such things as TOE, outdated
NIC drivers, teamed nics and others disclosed by the BPA can affect the quality
of life for a LAN.

Switch, patch cord, server nic is still my guess.

-
Larry
Please post the resolution to your
issue so others may benefit
-
Get Your SBS Health Check at
www.sbsbpa.com


> I have been through the gpupdate /force part from the server and this
> is a brand new server. I have suspicions that it may be more of a
> network issue since we had some problems with an older server through
> the years it was in service. What I do know is that it is frustrating
> for the users and rolling down to me. I still say this wreaks of a
> switch issue. This client is only a count of 14 with 1 SBS 2008
> server just recently installed. on this new Dell server. It's packed
> with the latest and greatest including 16gb RAM so I'm confident he is
> running well.
>
> There is only 1 internal switch... Netgear 24port 100/1000 switch. I
> have a 24port 10/100 switch that I am going to swap out just to see if
> it makes a difference. Because all users are experiencing this at the
> same time and the fact that I have not faced this same issue on any
> other SBS 2008 network... the switch is still the only wild card.
>
> let me ask one more question.... if the printers and drive maps are
> applied via gp preferences why would they go away if a network
> connection drops? Does the gp need to be live all of the time or is it
> I am just happening on one of those 90 minute GP updates from the
> server that all clients see at the same time and things are timing out
> with the server because of bad connection issues?
>
> By chance to cover all bases... has anyone seen any issues with
> service pack updates on the server clients that may be causing the
> problem?
>
> Thanks!
>
> -Richard K
>
> "Larry Struckmeyer[SBS-MVP]" <lstruckmeyer(a)mis-wizards.com> wrote in
> message news:4e68351513c7a8cccac5a4692f6d(a)news.microsoft.com...
>
>> "After a few minutes" either to lose or to reappear is not exactly
>> what I would expect if it were a GP issue. Policies are applied at
>> the refresh cycle for GP, which is 90 minutes by default.
>>
>> This is a clue, if *not* 90 minutes that the GP is ok, it is the
>> network connectivity that is failing. My guess would be the switch
>> or the NIC in the SBS, since it affects all clients at the same time.
>>
>> You could also try gpupdate /force from a command prompt of one of
>> the stations to see if that restores the mappings. If intermittent
>> connectivity is the issue it should fail, fail, fail, then succeed as
>> the connections are restored.
>>
>> -
>> Larry
>> Please post the resolution to your
>> issue so others may benefit
>> -
>> Get Your SBS Health Check at
>> www.sbsbpa.com
>>> Ok, makes sense that I need to look at it from more of a client
>>> issue. The current gp does the drive mappings and printer mappings
>>> and when they are lost it's everything (all drives disappear and all
>>> printers disappear) and when it happens to one user it's happening
>>> to other users as well which does wreak of intermittent network
>>> issues. After a few minutes they end up all coming back.
>>>
>>> I'm confident the network settings are good because I have very
>>> similar setups at other server environments so I'm wondering if I
>>> have a switch issue. Because this is intermittent it's going to
>>> make it that much harder to diagnose. Thoughts on where to start
>>> and what to look at?
>>>
>>> -Richard
>>>
>>> "Cliff Galiher - MVP" <cgaliher(a)gmail.com> wrote in message
>>> news:636EB961-95EB-4CFF-B093-55550E3ADF80(a)microsoft.com...
>>>
>>>> A key concept to keep in mind with these types of situations is
>>>> that group policies are (And have to me, if you think about it
>>>> logicially) applied by the client. In other words, the client
>>>> reads the group policy from the server and then applies it. If a
>>>> problem occurs, the client *attempts* to report the problem back to
>>>> the server, but there is no gaurantee that this will succeed if the
>>>> problem that caused the group policy in the first place still
>>>> exists.
>>>>
>>>> In other words, although the SBS logs can be somewhat helpful, when
>>>> it comes to group policies, the logs that matter are the clients.
>>>> When printers or drive mappings are failing, especially if the
>>>> problems are intermittent, the problem is almost always network
>>>> related. The server will get the report that the problem failed,
>>>> but since the server did not try to initiate contact with the
>>>> actual fielshare or printer via SMB, the nserver is not able to
>>>> report with any detail what went wrong.
>>>>
>>>> Look to your clients and make sure all of your network settings are
>>>> in order.
>>>>
>>>> -Cliff
>>>>
>>>> "Richard K" <rkokoski(a)foxdtechllc.com> wrote in message
>>>> news:OAOw8YD$KHA.980(a)TK2MSFTNGP04.phx.gbl...
>>>>
>>>>> SBS2008
>>>>> Win XP Pro + Windows 7 Pro clients
>>>>> I have successfully implemented GP policies for mapping drivers,
>>>>> printers and shortcut shares. Things have been working fine until
>>>>> yesterday. Now users are reporting to me that randomly their
>>>>> drives
>>>>> and printer maps are appearing/disappearing. When I look into the
>>>>> SBS2008 Application log I'm getting Event ID 4098 popping up with
>>>>> the source being Group Policy Drive Maps or Group Policy Printers.
>>>>> Below is the text of the Application log event. I did some
>>>>> research
>>>>> and am reading about an issue popping up with a recent .NET update
>>>>> on the server which could make sense.
>>>>> Users are frustrated and it is killing their production. Has
>>>>> anyone else encountered this?
>>>>>
>>>>> -Richard K
>>>>>
>>>>> Log Name: Application
>>>>> Source: Group Policy Printers
>>>>> Date: 5/25/2010 1:48:26 PM
>>>>> Event ID: 4098
>>>>> Task Category: (2)
>>>>> Level: Warning
>>>>> Keywords: Classic
>>>>> User: SYSTEM
>>>>> Computer: CMASERVER.cma.local
>>>>> Description:
>>>>> The user 'fax' preference item in the 'CMA - Deploy Printer Policy
>>>>> {2C696556-F13A-4691-899E-5CB5C0AAA798}' Group Policy object did
>>>>> not
>>>>> apply
>>>>> because it failed with error code '0x8007007b The filename,
>>>>> directory
>>>>> name, or volume label syntax is incorrect.' This error was
>>>>> suppressed.
>>>>> Event Xml:
>>>>> <Event
>>>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>>>> <System>
>>>>> <Provider Name="Group Policy Printers" />
>>>>> <EventID Qualifiers="34305">4098</EventID>
>>>>> <Level>3</Level>
>>>>> <Task>2</Task>
>>>>> <Keywords>0x80000000000000</Keywords>
>>>>> <TimeCreated SystemTime="2010-05-25T17:48:26.000Z" />
>>>>> <EventRecordID>1624865</EventRecordID>
>>>>> <Channel>Application</Channel>
>>>>> <Computer>CMASERVER.cma.local</Computer>
>>>>> <Security UserID="S-1-5-18" />
>>>>> </System>
>>>>> <EventData>
>>>>> <Data>user</Data>
>>>>> <Data>fax</Data>
>>>>> <Data>CMA - Deploy Printer Policy
>>>>> {2C696556-F13A-4691-899E-5CB5C0AAA798}</Data>
>>>>> <Data>0x8007007b The filename, directory name, or volume label
>>>>> syntax
>>>>> is incorrect.</Data>
>>>>> </EventData>
>>>>> </Event>
>>>>> Log Name: Application
>>>>> Source: Group Policy Drive Maps
>>>>> Date: 5/25/2010 1:48:26 PM
>>>>> Event ID: 4098
>>>>> Task Category: (2)
>>>>> Level: Warning
>>>>> Keywords: Classic
>>>>> User: SYSTEM
>>>>> Computer: CMASERVER.cma.local
>>>>> Description:
>>>>> The user 'Q:' preference item in the 'CMA - Map Drives Policy
>>>>> {7B6BBF47-EB1E-45D2-8696-07A168FD580D}' Group Policy object did
>>>>> not
>>>>> apply
>>>>> because it failed with error code '0x80070035 The network path was
>>>>> not
>>>>> found.' This error was suppressed.
>>>>> Event Xml:
>>>>> <Event
>>>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>>>> <System>
>>>>> <Provider Name="Group Policy Drive Maps" />
>>>>> <EventID Qualifiers="34305">4098</EventID>
>>>>> <Level>3</Level>
>>>>> <Task>2</Task>
>>>>> <Keywords>0x80000000000000</Keywords>
>>>>> <TimeCreated SystemTime="2010-05-25T17:48:26.000Z" />
>>>>> <EventRecordID>1624864</EventRecordID>
>>>>> <Channel>Application</Channel>
>>>>> <Computer>CMASERVER.cma.local</Computer>
>>>>> <Security UserID="S-1-5-18" />
>>>>> </System>
>>>>> <EventData>
>>>>> <Data>user</Data>
>>>>> <Data>Q:</Data>
>>>>> <Data>CMA - Map Drives Policy
>>>>> {7B6BBF47-EB1E-45D2-8696-07A168FD580D}</Data>
>>>>> <Data>0x80070035 The network path was not found.</Data>
>>>>> </EventData>
>>>>> </Event>


From: Richard K on 27 May 2010 07:37
I'm going to try the switch and patch cord change outs today. FYI, I have
run through the BPA and cleaned up all of the issues it mentioned.
Something is telling me it's hardware as well so let's see what I find.

thanks!

-Richard

"Larry Struckmeyer[SBS-MVP]" <lstruckmeyer(a)mis-wizards.com> wrote in message
news:4e68351513e998cccb7eda151765(a)news.microsoft.com...
> gpupdate is a command to update the local station, that is the station
> from which you issue the command. It does not "push" the update down to
> the stations. The force part is to cause the local station to refresh the
> policy regardless of the version number in the policy, as by default
> matching versions are not updated but skipped over.
>
> That this is a new server is, for me at least, new info, and as such I
> suggest you run the SBS BPA and fix anything it finds. Such things as
> TOE, outdated NIC drivers, teamed nics and others disclosed by the BPA can
> affect the quality of life for a LAN.
>
> Switch, patch cord, server nic is still my guess.
>
> -
> Larry
> Please post the resolution to your
> issue so others may benefit
> -
> Get Your SBS Health Check at
> www.sbsbpa.com
>
>
>> I have been through the gpupdate /force part from the server and this
>> is a brand new server. I have suspicions that it may be more of a
>> network issue since we had some problems with an older server through
>> the years it was in service. What I do know is that it is frustrating
>> for the users and rolling down to me. I still say this wreaks of a
>> switch issue. This client is only a count of 14 with 1 SBS 2008
>> server just recently installed. on this new Dell server. It's packed
>> with the latest and greatest including 16gb RAM so I'm confident he is
>> running well.
>>
>> There is only 1 internal switch... Netgear 24port 100/1000 switch. I
>> have a 24port 10/100 switch that I am going to swap out just to see if
>> it makes a difference. Because all users are experiencing this at the
>> same time and the fact that I have not faced this same issue on any
>> other SBS 2008 network... the switch is still the only wild card.
>>
>> let me ask one more question.... if the printers and drive maps are
>> applied via gp preferences why would they go away if a network
>> connection drops? Does the gp need to be live all of the time or is it
>> I am just happening on one of those 90 minute GP updates from the
>> server that all clients see at the same time and things are timing out
>> with the server because of bad connection issues?
>>
>> By chance to cover all bases... has anyone seen any issues with
>> service pack updates on the server clients that may be causing the
>> problem?
>>
>> Thanks!
>>
>> -Richard K
>>
>> "Larry Struckmeyer[SBS-MVP]" <lstruckmeyer(a)mis-wizards.com> wrote in
>> message news:4e68351513c7a8cccac5a4692f6d(a)news.microsoft.com...
>>
>>> "After a few minutes" either to lose or to reappear is not exactly
>>> what I would expect if it were a GP issue. Policies are applied at
>>> the refresh cycle for GP, which is 90 minutes by default.
>>>
>>> This is a clue, if *not* 90 minutes that the GP is ok, it is the
>>> network connectivity that is failing. My guess would be the switch
>>> or the NIC in the SBS, since it affects all clients at the same time.
>>>
>>> You could also try gpupdate /force from a command prompt of one of
>>> the stations to see if that restores the mappings. If intermittent
>>> connectivity is the issue it should fail, fail, fail, then succeed as
>>> the connections are restored.
>>>
>>> -
>>> Larry
>>> Please post the resolution to your
>>> issue so others may benefit
>>> -
>>> Get Your SBS Health Check at
>>> www.sbsbpa.com
>>>> Ok, makes sense that I need to look at it from more of a client
>>>> issue. The current gp does the drive mappings and printer mappings
>>>> and when they are lost it's everything (all drives disappear and all
>>>> printers disappear) and when it happens to one user it's happening
>>>> to other users as well which does wreak of intermittent network
>>>> issues. After a few minutes they end up all coming back.
>>>>
>>>> I'm confident the network settings are good because I have very
>>>> similar setups at other server environments so I'm wondering if I
>>>> have a switch issue. Because this is intermittent it's going to
>>>> make it that much harder to diagnose. Thoughts on where to start
>>>> and what to look at?
>>>>
>>>> -Richard
>>>>
>>>> "Cliff Galiher - MVP" <cgaliher(a)gmail.com> wrote in message
>>>> news:636EB961-95EB-4CFF-B093-55550E3ADF80(a)microsoft.com...
>>>>
>>>>> A key concept to keep in mind with these types of situations is
>>>>> that group policies are (And have to me, if you think about it
>>>>> logicially) applied by the client. In other words, the client
>>>>> reads the group policy from the server and then applies it. If a
>>>>> problem occurs, the client *attempts* to report the problem back to
>>>>> the server, but there is no gaurantee that this will succeed if the
>>>>> problem that caused the group policy in the first place still
>>>>> exists.
>>>>>
>>>>> In other words, although the SBS logs can be somewhat helpful, when
>>>>> it comes to group policies, the logs that matter are the clients.
>>>>> When printers or drive mappings are failing, especially if the
>>>>> problems are intermittent, the problem is almost always network
>>>>> related. The server will get the report that the problem failed,
>>>>> but since the server did not try to initiate contact with the
>>>>> actual fielshare or printer via SMB, the nserver is not able to
>>>>> report with any detail what went wrong.
>>>>>
>>>>> Look to your clients and make sure all of your network settings are
>>>>> in order.
>>>>>
>>>>> -Cliff
>>>>>
>>>>> "Richard K" <rkokoski(a)foxdtechllc.com> wrote in message
>>>>> news:OAOw8YD$KHA.980(a)TK2MSFTNGP04.phx.gbl...
>>>>>
>>>>>> SBS2008
>>>>>> Win XP Pro + Windows 7 Pro clients
>>>>>> I have successfully implemented GP policies for mapping drivers,
>>>>>> printers and shortcut shares. Things have been working fine until
>>>>>> yesterday. Now users are reporting to me that randomly their
>>>>>> drives
>>>>>> and printer maps are appearing/disappearing. When I look into the
>>>>>> SBS2008 Application log I'm getting Event ID 4098 popping up with
>>>>>> the source being Group Policy Drive Maps or Group Policy Printers.
>>>>>> Below is the text of the Application log event. I did some
>>>>>> research
>>>>>> and am reading about an issue popping up with a recent .NET update
>>>>>> on the server which could make sense.
>>>>>> Users are frustrated and it is killing their production. Has
>>>>>> anyone else encountered this?
>>>>>>
>>>>>> -Richard K
>>>>>>
>>>>>> Log Name: Application
>>>>>> Source: Group Policy Printers
>>>>>> Date: 5/25/2010 1:48:26 PM
>>>>>> Event ID: 4098
>>>>>> Task Category: (2)
>>>>>> Level: Warning
>>>>>> Keywords: Classic
>>>>>> User: SYSTEM
>>>>>> Computer: CMASERVER.cma.local
>>>>>> Description:
>>>>>> The user 'fax' preference item in the 'CMA - Deploy Printer Policy
>>>>>> {2C696556-F13A-4691-899E-5CB5C0AAA798}' Group Policy object did
>>>>>> not
>>>>>> apply
>>>>>> because it failed with error code '0x8007007b The filename,
>>>>>> directory
>>>>>> name, or volume label syntax is incorrect.' This error was
>>>>>> suppressed.
>>>>>> Event Xml:
>>>>>> <Event
>>>>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>>>>> <System>
>>>>>> <Provider Name="Group Policy Printers" />
>>>>>> <EventID Qualifiers="34305">4098</EventID>
>>>>>> <Level>3</Level>
>>>>>> <Task>2</Task>
>>>>>> <Keywords>0x80000000000000</Keywords>
>>>>>> <TimeCreated SystemTime="2010-05-25T17:48:26.000Z" />
>>>>>> <EventRecordID>1624865</EventRecordID>
>>>>>> <Channel>Application</Channel>
>>>>>> <Computer>CMASERVER.cma.local</Computer>
>>>>>> <Security UserID="S-1-5-18" />
>>>>>> </System>
>>>>>> <EventData>
>>>>>> <Data>user</Data>
>>>>>> <Data>fax</Data>
>>>>>> <Data>CMA - Deploy Printer Policy
>>>>>> {2C696556-F13A-4691-899E-5CB5C0AAA798}</Data>
>>>>>> <Data>0x8007007b The filename, directory name, or volume label
>>>>>> syntax
>>>>>> is incorrect.</Data>
>>>>>> </EventData>
>>>>>> </Event>
>>>>>> Log Name: Application
>>>>>> Source: Group Policy Drive Maps
>>>>>> Date: 5/25/2010 1:48:26 PM
>>>>>> Event ID: 4098
>>>>>> Task Category: (2)
>>>>>> Level: Warning
>>>>>> Keywords: Classic
>>>>>> User: SYSTEM
>>>>>> Computer: CMASERVER.cma.local
>>>>>> Description:
>>>>>> The user 'Q:' preference item in the 'CMA - Map Drives Policy
>>>>>> {7B6BBF47-EB1E-45D2-8696-07A168FD580D}' Group Policy object did
>>>>>> not
>>>>>> apply
>>>>>> because it failed with error code '0x80070035 The network path was
>>>>>> not
>>>>>> found.' This error was suppressed.
>>>>>> Event Xml:
>>>>>> <Event
>>>>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>>>>> <System>
>>>>>> <Provider Name="Group Policy Drive Maps" />
>>>>>> <EventID Qualifiers="34305">4098</EventID>
>>>>>> <Level>3</Level>
>>>>>> <Task>2</Task>
>>>>>> <Keywords>0x80000000000000</Keywords>
>>>>>> <TimeCreated SystemTime="2010-05-25T17:48:26.000Z" />
>>>>>> <EventRecordID>1624864</EventRecordID>
>>>>>> <Channel>Application</Channel>
>>>>>> <Computer>CMASERVER.cma.local</Computer>
>>>>>> <Security UserID="S-1-5-18" />
>>>>>> </System>
>>>>>> <EventData>
>>>>>> <Data>user</Data>
>>>>>> <Data>Q:</Data>
>>>>>> <Data>CMA - Map Drives Policy
>>>>>> {7B6BBF47-EB1E-45D2-8696-07A168FD580D}</Data>
>>>>>> <Data>0x80070035 The network path was not found.</Data>
>>>>>> </EventData>
>>>>>> </Event>
>
>
From: Larry Struckmeyer[SBS-MVP] on 27 May 2010 08:09
That "something" is Cliff and I shouting. (in lower case) <g>

-
Larry
Please post the resolution to your
issue so others may benefit
-
Get Your SBS Health Check at
www.sbsbpa.com


> I'm going to try the switch and patch cord change outs today. FYI, I
> have run through the BPA and cleaned up all of the issues it
> mentioned. Something is telling me it's hardware as well so let's see
> what I find.
>
> thanks!
>
> -Richard
>
> "Larry Struckmeyer[SBS-MVP]" <lstruckmeyer(a)mis-wizards.com> wrote in
> message news:4e68351513e998cccb7eda151765(a)news.microsoft.com...
>
>> gpupdate is a command to update the local station, that is the
>> station from which you issue the command. It does not "push" the
>> update down to the stations. The force part is to cause the local
>> station to refresh the policy regardless of the version number in the
>> policy, as by default matching versions are not updated but skipped
>> over.
>>
>> That this is a new server is, for me at least, new info, and as such
>> I suggest you run the SBS BPA and fix anything it finds. Such things
>> as TOE, outdated NIC drivers, teamed nics and others disclosed by the
>> BPA can affect the quality of life for a LAN.
>>
>> Switch, patch cord, server nic is still my guess.
>>
>> -
>> Larry
>> Please post the resolution to your
>> issue so others may benefit
>> -
>> Get Your SBS Health Check at
>> www.sbsbpa.com
>>> I have been through the gpupdate /force part from the server and
>>> this is a brand new server. I have suspicions that it may be more
>>> of a network issue since we had some problems with an older server
>>> through the years it was in service. What I do know is that it is
>>> frustrating for the users and rolling down to me. I still say this
>>> wreaks of a switch issue. This client is only a count of 14 with 1
>>> SBS 2008 server just recently installed. on this new Dell server.
>>> It's packed with the latest and greatest including 16gb RAM so I'm
>>> confident he is running well.
>>>
>>> There is only 1 internal switch... Netgear 24port 100/1000 switch.
>>> I have a 24port 10/100 switch that I am going to swap out just to
>>> see if it makes a difference. Because all users are experiencing
>>> this at the same time and the fact that I have not faced this same
>>> issue on any other SBS 2008 network... the switch is still the only
>>> wild card.
>>>
>>> let me ask one more question.... if the printers and drive maps are
>>> applied via gp preferences why would they go away if a network
>>> connection drops? Does the gp need to be live all of the time or is
>>> it I am just happening on one of those 90 minute GP updates from the
>>> server that all clients see at the same time and things are timing
>>> out with the server because of bad connection issues?
>>>
>>> By chance to cover all bases... has anyone seen any issues with
>>> service pack updates on the server clients that may be causing the
>>> problem?
>>>
>>> Thanks!
>>>
>>> -Richard K
>>>
>>> "Larry Struckmeyer[SBS-MVP]" <lstruckmeyer(a)mis-wizards.com> wrote in
>>> message news:4e68351513c7a8cccac5a4692f6d(a)news.microsoft.com...
>>>
>>>> "After a few minutes" either to lose or to reappear is not exactly
>>>> what I would expect if it were a GP issue. Policies are applied at
>>>> the refresh cycle for GP, which is 90 minutes by default.
>>>>
>>>> This is a clue, if *not* 90 minutes that the GP is ok, it is the
>>>> network connectivity that is failing. My guess would be the switch
>>>> or the NIC in the SBS, since it affects all clients at the same
>>>> time.
>>>>
>>>> You could also try gpupdate /force from a command prompt of one of
>>>> the stations to see if that restores the mappings. If intermittent
>>>> connectivity is the issue it should fail, fail, fail, then succeed
>>>> as the connections are restored.
>>>>
>>>> -
>>>> Larry
>>>> Please post the resolution to your
>>>> issue so others may benefit
>>>> -
>>>> Get Your SBS Health Check at
>>>> www.sbsbpa.com
>>>>> Ok, makes sense that I need to look at it from more of a client
>>>>> issue. The current gp does the drive mappings and printer mappings
>>>>> and when they are lost it's everything (all drives disappear and
>>>>> all printers disappear) and when it happens to one user it's
>>>>> happening to other users as well which does wreak of intermittent
>>>>> network issues. After a few minutes they end up all coming back.
>>>>>
>>>>> I'm confident the network settings are good because I have very
>>>>> similar setups at other server environments so I'm wondering if I
>>>>> have a switch issue. Because this is intermittent it's going to
>>>>> make it that much harder to diagnose. Thoughts on where to start
>>>>> and what to look at?
>>>>>
>>>>> -Richard
>>>>>
>>>>> "Cliff Galiher - MVP" <cgaliher(a)gmail.com> wrote in message
>>>>> news:636EB961-95EB-4CFF-B093-55550E3ADF80(a)microsoft.com...
>>>>>
>>>>>> A key concept to keep in mind with these types of situations is
>>>>>> that group policies are (And have to me, if you think about it
>>>>>> logicially) applied by the client. In other words, the client
>>>>>> reads the group policy from the server and then applies it. If a
>>>>>> problem occurs, the client *attempts* to report the problem back
>>>>>> to the server, but there is no gaurantee that this will succeed
>>>>>> if the problem that caused the group policy in the first place
>>>>>> still exists.
>>>>>>
>>>>>> In other words, although the SBS logs can be somewhat helpful,
>>>>>> when it comes to group policies, the logs that matter are the
>>>>>> clients. When printers or drive mappings are failing, especially
>>>>>> if the problems are intermittent, the problem is almost always
>>>>>> network related. The server will get the report that the problem
>>>>>> failed, but since the server did not try to initiate contact with
>>>>>> the actual fielshare or printer via SMB, the nserver is not able
>>>>>> to report with any detail what went wrong.
>>>>>>
>>>>>> Look to your clients and make sure all of your network settings
>>>>>> are in order.
>>>>>>
>>>>>> -Cliff
>>>>>>
>>>>>> "Richard K" <rkokoski(a)foxdtechllc.com> wrote in message
>>>>>> news:OAOw8YD$KHA.980(a)TK2MSFTNGP04.phx.gbl...
>>>>>>
>>>>>>> SBS2008
>>>>>>> Win XP Pro + Windows 7 Pro clients
>>>>>>> I have successfully implemented GP policies for mapping drivers,
>>>>>>> printers and shortcut shares. Things have been working fine
>>>>>>> until
>>>>>>> yesterday. Now users are reporting to me that randomly their
>>>>>>> drives
>>>>>>> and printer maps are appearing/disappearing. When I look into
>>>>>>> the
>>>>>>> SBS2008 Application log I'm getting Event ID 4098 popping up
>>>>>>> with
>>>>>>> the source being Group Policy Drive Maps or Group Policy
>>>>>>> Printers.
>>>>>>> Below is the text of the Application log event. I did some
>>>>>>> research
>>>>>>> and am reading about an issue popping up with a recent .NET
>>>>>>> update
>>>>>>> on the server which could make sense.
>>>>>>> Users are frustrated and it is killing their production. Has
>>>>>>> anyone else encountered this?
>>>>>>> -Richard K
>>>>>>>
>>>>>>> Log Name: Application
>>>>>>> Source: Group Policy Printers
>>>>>>> Date: 5/25/2010 1:48:26 PM
>>>>>>> Event ID: 4098
>>>>>>> Task Category: (2)
>>>>>>> Level: Warning
>>>>>>> Keywords: Classic
>>>>>>> User: SYSTEM
>>>>>>> Computer: CMASERVER.cma.local
>>>>>>> Description:
>>>>>>> The user 'fax' preference item in the 'CMA - Deploy Printer
>>>>>>> Policy
>>>>>>> {2C696556-F13A-4691-899E-5CB5C0AAA798}' Group Policy object did
>>>>>>> not
>>>>>>> apply
>>>>>>> because it failed with error code '0x8007007b The filename,
>>>>>>> directory
>>>>>>> name, or volume label syntax is incorrect.' This error was
>>>>>>> suppressed.
>>>>>>> Event Xml:
>>>>>>> <Event
>>>>>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>>>>>> <System>
>>>>>>> <Provider Name="Group Policy Printers" />
>>>>>>> <EventID Qualifiers="34305">4098</EventID>
>>>>>>> <Level>3</Level>
>>>>>>> <Task>2</Task>
>>>>>>> <Keywords>0x80000000000000</Keywords>
>>>>>>> <TimeCreated SystemTime="2010-05-25T17:48:26.000Z" />
>>>>>>> <EventRecordID>1624865</EventRecordID>
>>>>>>> <Channel>Application</Channel>
>>>>>>> <Computer>CMASERVER.cma.local</Computer>
>>>>>>> <Security UserID="S-1-5-18" />
>>>>>>> </System>
>>>>>>> <EventData>
>>>>>>> <Data>user</Data>
>>>>>>> <Data>fax</Data>
>>>>>>> <Data>CMA - Deploy Printer Policy
>>>>>>> {2C696556-F13A-4691-899E-5CB5C0AAA798}</Data>
>>>>>>> <Data>0x8007007b The filename, directory name, or volume label
>>>>>>> syntax
>>>>>>> is incorrect.</Data>
>>>>>>> </EventData>
>>>>>>> </Event>
>>>>>>> Log Name: Application
>>>>>>> Source: Group Policy Drive Maps
>>>>>>> Date: 5/25/2010 1:48:26 PM
>>>>>>> Event ID: 4098
>>>>>>> Task Category: (2)
>>>>>>> Level: Warning
>>>>>>> Keywords: Classic
>>>>>>> User: SYSTEM
>>>>>>> Computer: CMASERVER.cma.local
>>>>>>> Description:
>>>>>>> The user 'Q:' preference item in the 'CMA - Map Drives Policy
>>>>>>> {7B6BBF47-EB1E-45D2-8696-07A168FD580D}' Group Policy object did
>>>>>>> not
>>>>>>> apply
>>>>>>> because it failed with error code '0x80070035 The network path
>>>>>>> was
>>>>>>> not
>>>>>>> found.' This error was suppressed.
>>>>>>> Event Xml:
>>>>>>> <Event
>>>>>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>>>>>> <System>
>>>>>>> <Provider Name="Group Policy Drive Maps" />
>>>>>>> <EventID Qualifiers="34305">4098</EventID>
>>>>>>> <Level>3</Level>
>>>>>>> <Task>2</Task>
>>>>>>> <Keywords>0x80000000000000</Keywords>
>>>>>>> <TimeCreated SystemTime="2010-05-25T17:48:26.000Z" />
>>>>>>> <EventRecordID>1624864</EventRecordID>
>>>>>>> <Channel>Application</Channel>
>>>>>>> <Computer>CMASERVER.cma.local</Computer>
>>>>>>> <Security UserID="S-1-5-18" />
>>>>>>> </System>
>>>>>>> <EventData>
>>>>>>> <Data>user</Data>
>>>>>>> <Data>Q:</Data>
>>>>>>> <Data>CMA - Map Drives Policy
>>>>>>> {7B6BBF47-EB1E-45D2-8696-07A168FD580D}</Data>
>>>>>>> <Data>0x80070035 The network path was not found.</Data>
>>>>>>> </EventData>
>>>>>>> </Event>


First  |  Prev  | 
Pages: 1 2
Prev: Connect to my company's application sharing server missing in
Next: Blocked by cbl.abuseat.org