Every so often Server doesnt allow users to access its resources.

It started off every 3 days this issue happened but after removing unused
programs to free up RAM this issue seems to happen every 20 days.

Setup:

1 - Windows 2003 Server Small business edition. with all the latest Updates.
I removed Exchange, WSUS, and Sharepoint as they are not needed and using
too much RAM.
Server Role: File Server, and Quickbooks Database

5 - XP Workstations.


Symptoms:
Everything will work fine and then after several days the users cannot
access files or quickbooks. No mapped drives are found and the login script
will not run. If i go to the server and open AD users and computers i get
this error: " Naming Information cannot be located for the following reason:
The Server is not operational

If your are tryring to connect to a domain controller running windows 2k
verify that sp3 or later is installed on the domain controller, or use the
win2k admin tools "

This is what the clients say if i go to Start>Run \\ServerName

\\Server Name is not accessable. You might not have permisssion to use the
network resource. Contact the administrator of

this server to find out if you have access permissions.
The specified server cannot perform the requested operation.

The only way i know how to resolve this is reboot the server.

Any suggestions on why this is happening. and how to fix it for good.

Adding the SBS newsgoup where this issue would best be addressed.

Start by posting the output of an ipconfig/all from a command prompt on the
SBS server.

In the mean time you might also want to download, install and run the SBS
best practices analyzer.
http://www.microsoft.com/downloads/d...displaylang=en


Dan V wrote:
> It started off every 3 days this issue happened but after removing
> unused programs to free up RAM this issue seems to happen every 20
> days.
> Setup:
>
> 1 - Windows 2003 Server Small business edition. with all the latest
> Updates. I removed Exchange, WSUS, and Sharepoint as they are not
> needed and using too much RAM.
> Server Role: File Server, and Quickbooks Database
>
> 5 - XP Workstations.
>
>
> Symptoms:
> Everything will work fine and then after several days the users cannot
> access files or quickbooks. No mapped drives are found and the login
> script will not run. If i go to the server and open AD users and
> computers i get this error: " Naming Information cannot be located
> for the following reason: The Server is not operational
>
> If your are tryring to connect to a domain controller running windows
> 2k verify that sp3 or later is installed on the domain controller, or
> use the win2k admin tools "
>
> This is what the clients say if i go to Start>Run \\ServerName
>
> \\Server Name is not accessable. You might not have permisssion to
> use the network resource. Contact the administrator of
>
> this server to find out if you have access permissions.
> The specified server cannot perform the requested operation.
>
> The only way i know how to resolve this is reboot the server.
>
> Any suggestions on why this is happening. and how to fix it for good.

--
/kj

C:\Documents and Settings\Administrator>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : SERVER
Primary Dns Suffix . . . . . . . : domain.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : domain.local

Ethernet adapter Server Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-15-C5-F6-9C-62
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.253
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.253
Primary WINS Server . . . . . . . : 192.168.1.253
"kj [SBS MVP]" <> wrote in message
news:...
> Adding the SBS newsgoup where this issue would best be addressed.
>
> Start by posting the output of an ipconfig/all from a command prompt on
> the SBS server.
>
> In the mean time you might also want to download, install and run the SBS
> best practices analyzer.
> http://www.microsoft.com/downloads/d...displaylang=en
>
>
> Dan V wrote:
>> It started off every 3 days this issue happened but after removing
>> unused programs to free up RAM this issue seems to happen every 20
>> days.
>> Setup:
>>
>> 1 - Windows 2003 Server Small business edition. with all the latest
>> Updates. I removed Exchange, WSUS, and Sharepoint as they are not
>> needed and using too much RAM.
>> Server Role: File Server, and Quickbooks Database
>>
>> 5 - XP Workstations.
>>
>>
>> Symptoms:
>> Everything will work fine and then after several days the users cannot
>> access files or quickbooks. No mapped drives are found and the login
>> script will not run. If i go to the server and open AD users and
>> computers i get this error: " Naming Information cannot be located
>> for the following reason: The Server is not operational
>>
>> If your are tryring to connect to a domain controller running windows
>> 2k verify that sp3 or later is installed on the domain controller, or
>> use the win2k admin tools "
>>
>> This is what the clients say if i go to Start>Run \\ServerName
>>
>> \\Server Name is not accessable. You might not have permisssion to
>> use the network resource. Contact the administrator of
>>
>> this server to find out if you have access permissions.
>> The specified server cannot perform the requested operation.
>>
>> The only way i know how to resolve this is reboot the server.
>>
>> Any suggestions on why this is happening. and how to fix it for good.
>
> --
> /kj
>

Here is the results of the analyzer tool

ExchangeVDir registry does not exist ( i removed exchange cause it was not
used)
Help and Support Service missing
Task Offloading is enabled

"Dan" <security54 at gmail dot com> wrote in message
news:...
> C:\Documents and Settings\Administrator>ipconfig/all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : SERVER
> Primary Dns Suffix . . . . . . . : domain.local
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : Yes
> DNS Suffix Search List. . . . . . : domain.local
>
> Ethernet adapter Server Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
> Physical Address. . . . . . . . . : 00-15-C5-F6-9C-62
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.253
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.253
> Primary WINS Server . . . . . . . : 192.168.1.253
> "kj [SBS MVP]" <> wrote in message
> news:...
>> Adding the SBS newsgoup where this issue would best be addressed.
>>
>> Start by posting the output of an ipconfig/all from a command prompt on
>> the SBS server.
>>
>> In the mean time you might also want to download, install and run the SBS
>> best practices analyzer.
>> http://www.microsoft.com/downloads/d...displaylang=en
>>
>>
>> Dan V wrote:
>>> It started off every 3 days this issue happened but after removing
>>> unused programs to free up RAM this issue seems to happen every 20
>>> days.
>>> Setup:
>>>
>>> 1 - Windows 2003 Server Small business edition. with all the latest
>>> Updates. I removed Exchange, WSUS, and Sharepoint as they are not
>>> needed and using too much RAM.
>>> Server Role: File Server, and Quickbooks Database
>>>
>>> 5 - XP Workstations.
>>>
>>>
>>> Symptoms:
>>> Everything will work fine and then after several days the users cannot
>>> access files or quickbooks. No mapped drives are found and the login
>>> script will not run. If i go to the server and open AD users and
>>> computers i get this error: " Naming Information cannot be located
>>> for the following reason: The Server is not operational
>>>
>>> If your are tryring to connect to a domain controller running windows
>>> 2k verify that sp3 or later is installed on the domain controller, or
>>> use the win2k admin tools "
>>>
>>> This is what the clients say if i go to Start>Run \\ServerName
>>>
>>> \\Server Name is not accessable. You might not have permisssion to
>>> use the network resource. Contact the administrator of
>>>
>>> this server to find out if you have access permissions.
>>> The specified server cannot perform the requested operation.
>>>
>>> The only way i know how to resolve this is reboot the server.
>>>
>>> Any suggestions on why this is happening. and how to fix it for good.
>>
>> --
>> /kj
>>
>
>

Disable TOE particularly on a Broadcom NIC. The others are typical when
built in functionality has been ripped out.

It'd be a good idea to check and update the driver package for you NIC too.

Dan wrote:
> Here is the results of the analyzer tool
>
> ExchangeVDir registry does not exist ( i removed exchange cause it
> was not used)
> Help and Support Service missing
> Task Offloading is enabled
>
> "Dan" <security54 at gmail dot com> wrote in message
> news:...
>> C:\Documents and Settings\Administrator>ipconfig/all
>>
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : SERVER
>> Primary Dns Suffix . . . . . . . : domain.local
>> Node Type . . . . . . . . . . . . : Unknown
>> IP Routing Enabled. . . . . . . . : Yes
>> WINS Proxy Enabled. . . . . . . . : Yes
>> DNS Suffix Search List. . . . . . : domain.local
>>
>> Ethernet adapter Server Local Area Connection:
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
>> Ethernet Physical Address. . . . . . . . . : 00-15-C5-F6-9C-62
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.1.253
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.1.1
>> DNS Servers . . . . . . . . . . . : 192.168.1.253
>> Primary WINS Server . . . . . . . : 192.168.1.253
>> "kj [SBS MVP]" <> wrote in message
>> news:...
>>> Adding the SBS newsgoup where this issue would best be addressed.
>>>
>>> Start by posting the output of an ipconfig/all from a command
>>> prompt on the SBS server.
>>>
>>> In the mean time you might also want to download, install and run
>>> the SBS best practices analyzer.
>>> http://www.microsoft.com/downloads/d...displaylang=en
>>>
>>>
>>> Dan V wrote:
>>>> It started off every 3 days this issue happened but after removing
>>>> unused programs to free up RAM this issue seems to happen every 20
>>>> days.
>>>> Setup:
>>>>
>>>> 1 - Windows 2003 Server Small business edition. with all the latest
>>>> Updates. I removed Exchange, WSUS, and Sharepoint as they are not
>>>> needed and using too much RAM.
>>>> Server Role: File Server, and Quickbooks Database
>>>>
>>>> 5 - XP Workstations.
>>>>
>>>>
>>>> Symptoms:
>>>> Everything will work fine and then after several days the users
>>>> cannot access files or quickbooks. No mapped drives are found and
>>>> the login script will not run. If i go to the server and open AD
>>>> users and computers i get this error: " Naming Information cannot
>>>> be located for the following reason: The Server is not operational
>>>>
>>>> If your are tryring to connect to a domain controller running
>>>> windows 2k verify that sp3 or later is installed on the domain
>>>> controller, or use the win2k admin tools "
>>>>
>>>> This is what the clients say if i go to Start>Run \\ServerName
>>>>
>>>> \\Server Name is not accessable. You might not have permisssion to
>>>> use the network resource. Contact the administrator of
>>>>
>>>> this server to find out if you have access permissions.
>>>> The specified server cannot perform the requested operation.
>>>>
>>>> The only way i know how to resolve this is reboot the server.
>>>>
>>>> Any suggestions on why this is happening. and how to fix it for
>>>> good.
>>>
>>> --
>>> /kj

--
/kj

i ran this command to disable TOE Netsh int ip set chimney DISABLED

but i still have the main issue do you know what would cause that.

tia
"kj [SBS MVP]" <> wrote in message
news:...
> Disable TOE particularly on a Broadcom NIC. The others are typical when
> built in functionality has been ripped out.
>
> It'd be a good idea to check and update the driver package for you NIC
> too.
>
> Dan wrote:
>> Here is the results of the analyzer tool
>>
>> ExchangeVDir registry does not exist ( i removed exchange cause it
>> was not used)
>> Help and Support Service missing
>> Task Offloading is enabled
>>
>> "Dan" <security54 at gmail dot com> wrote in message
>> news:...
>>> C:\Documents and Settings\Administrator>ipconfig/all
>>>
>>> Windows IP Configuration
>>>
>>> Host Name . . . . . . . . . . . . : SERVER
>>> Primary Dns Suffix . . . . . . . : domain.local
>>> Node Type . . . . . . . . . . . . : Unknown
>>> IP Routing Enabled. . . . . . . . : Yes
>>> WINS Proxy Enabled. . . . . . . . : Yes
>>> DNS Suffix Search List. . . . . . : domain.local
>>>
>>> Ethernet adapter Server Local Area Connection:
>>>
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
>>> Ethernet Physical Address. . . . . . . . . : 00-15-C5-F6-9C-62
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.1.253
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>> DNS Servers . . . . . . . . . . . : 192.168.1.253
>>> Primary WINS Server . . . . . . . : 192.168.1.253
>>> "kj [SBS MVP]" <> wrote in message
>>> news:...
>>>> Adding the SBS newsgoup where this issue would best be addressed.
>>>>
>>>> Start by posting the output of an ipconfig/all from a command
>>>> prompt on the SBS server.
>>>>
>>>> In the mean time you might also want to download, install and run
>>>> the SBS best practices analyzer.
>>>> http://www.microsoft.com/downloads/d...displaylang=en
>>>>
>>>>
>>>> Dan V wrote:
>>>>> It started off every 3 days this issue happened but after removing
>>>>> unused programs to free up RAM this issue seems to happen every 20
>>>>> days.
>>>>> Setup:
>>>>>
>>>>> 1 - Windows 2003 Server Small business edition. with all the latest
>>>>> Updates. I removed Exchange, WSUS, and Sharepoint as they are not
>>>>> needed and using too much RAM.
>>>>> Server Role: File Server, and Quickbooks Database
>>>>>
>>>>> 5 - XP Workstations.
>>>>>
>>>>>
>>>>> Symptoms:
>>>>> Everything will work fine and then after several days the users
>>>>> cannot access files or quickbooks. No mapped drives are found and
>>>>> the login script will not run. If i go to the server and open AD
>>>>> users and computers i get this error: " Naming Information cannot
>>>>> be located for the following reason: The Server is not operational
>>>>>
>>>>> If your are tryring to connect to a domain controller running
>>>>> windows 2k verify that sp3 or later is installed on the domain
>>>>> controller, or use the win2k admin tools "
>>>>>
>>>>> This is what the clients say if i go to Start>Run \\ServerName
>>>>>
>>>>> \\Server Name is not accessable. You might not have permisssion to
>>>>> use the network resource. Contact the administrator of
>>>>>
>>>>> this server to find out if you have access permissions.
>>>>> The specified server cannot perform the requested operation.
>>>>>
>>>>> The only way i know how to resolve this is reboot the server.
>>>>>
>>>>> Any suggestions on why this is happening. and how to fix it for
>>>>> good.
>>>>
>>>> --
>>>> /kj
>
> --
> /kj
>

If you look at Task Manager, how much available RAM do you have when the
problem happens, and how much after a reboot?


"Dan V" <dvalenti54athotmail.com> wrote in message
news:%...
> It started off every 3 days this issue happened but after removing unused
> programs to free up RAM this issue seems to happen every 20 days.
>
> Setup:
>
> 1 - Windows 2003 Server Small business edition. with all the latest
> Updates. I removed Exchange, WSUS, and Sharepoint as they are not needed
> and using too much RAM.
> Server Role: File Server, and Quickbooks Database
>
> 5 - XP Workstations.
>
>
> Symptoms:
> Everything will work fine and then after several days the users cannot
> access files or quickbooks. No mapped drives are found and the login
> script will not run. If i go to the server and open AD users and computers
> i get this error: " Naming Information cannot be located for the following
> reason:
> The Server is not operational
>
> If your are tryring to connect to a domain controller running windows 2k
> verify that sp3 or later is installed on the domain controller, or use the
> win2k admin tools "
>
> This is what the clients say if i go to Start>Run \\ServerName
>
> \\Server Name is not accessable. You might not have permisssion to use the
> network resource. Contact the administrator of
>
> this server to find out if you have access permissions.
> The specified server cannot perform the requested operation.
>
> The only way i know how to resolve this is reboot the server.
>
> Any suggestions on why this is happening. and how to fix it for good.
>
>

The server only has 1 gb but its been like this for 5 years and all of a
sudden this is happening.
The server idles around 800 -900 MB

Also note i disabled TOE and updated to the latest NIC drivers. Not sure if
that will fix this issue. I read on the net that others have this issue and
its with server SMB 2008 and MS released a hotfix but i cant find any fix
for 2003SMB

thanks for the help

"JohnB" <> wrote in message
news:...
> If you look at Task Manager, how much available RAM do you have when the
> problem happens, and how much after a reboot?
>
>
> "Dan V" <dvalenti54athotmail.com> wrote in message
> news:%...
>> It started off every 3 days this issue happened but after removing unused
>> programs to free up RAM this issue seems to happen every 20 days.
>>
>> Setup:
>>
>> 1 - Windows 2003 Server Small business edition. with all the latest
>> Updates. I removed Exchange, WSUS, and Sharepoint as they are not needed
>> and using too much RAM.
>> Server Role: File Server, and Quickbooks Database
>>
>> 5 - XP Workstations.
>>
>>
>> Symptoms:
>> Everything will work fine and then after several days the users cannot
>> access files or quickbooks. No mapped drives are found and the login
>> script will not run. If i go to the server and open AD users and
>> computers i get this error: " Naming Information cannot be located for
>> the following reason:
>> The Server is not operational
>>
>> If your are tryring to connect to a domain controller running windows 2k
>> verify that sp3 or later is installed on the domain controller, or use
>> the win2k admin tools "
>>
>> This is what the clients say if i go to Start>Run \\ServerName
>>
>> \\Server Name is not accessable. You might not have permisssion to use
>> the network resource. Contact the administrator of
>>
>> this server to find out if you have access permissions.
>> The specified server cannot perform the requested operation.
>>
>> The only way i know how to resolve this is reboot the server.
>>
>> Any suggestions on why this is happening. and how to fix it for good.
>>
>>
>
>

Next check the SBS event logs for warnings and errors. Check System,
Applications, Directory Services, and DNS.

When the problem arises are you able to ping the SBS server by address and
by name?

Dan wrote:
> The server only has 1 gb but its been like this for 5 years and all
> of a sudden this is happening.
> The server idles around 800 -900 MB
>
> Also note i disabled TOE and updated to the latest NIC drivers. Not
> sure if that will fix this issue. I read on the net that others have
> this issue and its with server SMB 2008 and MS released a hotfix but
> i cant find any fix for 2003SMB
>
> thanks for the help
>
> "JohnB" <> wrote in message
> news:...
>> If you look at Task Manager, how much available RAM do you have when
>> the problem happens, and how much after a reboot?
>>
>>
>> "Dan V" <dvalenti54athotmail.com> wrote in message
>> news:%...
>>> It started off every 3 days this issue happened but after removing
>>> unused programs to free up RAM this issue seems to happen every 20
>>> days. Setup:
>>>
>>> 1 - Windows 2003 Server Small business edition. with all the latest
>>> Updates. I removed Exchange, WSUS, and Sharepoint as they are not
>>> needed and using too much RAM.
>>> Server Role: File Server, and Quickbooks Database
>>>
>>> 5 - XP Workstations.
>>>
>>>
>>> Symptoms:
>>> Everything will work fine and then after several days the users
>>> cannot access files or quickbooks. No mapped drives are found and
>>> the login script will not run. If i go to the server and open AD
>>> users and computers i get this error: " Naming Information cannot
>>> be located for the following reason:
>>> The Server is not operational
>>>
>>> If your are tryring to connect to a domain controller running
>>> windows 2k verify that sp3 or later is installed on the domain
>>> controller, or use the win2k admin tools "
>>>
>>> This is what the clients say if i go to Start>Run \\ServerName
>>>
>>> \\Server Name is not accessable. You might not have permisssion to
>>> use the network resource. Contact the administrator of
>>>
>>> this server to find out if you have access permissions.
>>> The specified server cannot perform the requested operation.
>>>
>>> The only way i know how to resolve this is reboot the server.
>>>
>>> Any suggestions on why this is happening. and how to fix it for
>>> good.

--
/kj

On 05/05/10 23:44, Dan wrote:
> i ran this command to disable TOE Netsh int ip set chimney DISABLED
>
> but i still have the main issue do you know what would cause that.
>

There isn't a standard SBS 2003 fault which causes this symptom, if
that's what you're asking. DNS is often at the root of intermittent
funnies, and while you gave us the ipconfig from the server, it's
actually more likely to be workstation DNS configuration that is at
fault. Could you check an affected workstation also, ideally when the
fault is present? This should also show whether the DHCP server has
problems, which can also cause odd intermittent behaviour.

The clients should ideally get their DNS information from DHCP from the
SBS, but if there's a reason this isn't done, then the clients should be
configured with the SBS IP address only for DNS. Any other DNS server
listed on a client *will* at some point cause intermittent loss of
resources.

After DNS and DHCP, and if the BPA doesn't show anything relevant, as it
seems, then suspicion switches to networking hardware and its drivers.
NICs quite definitely do *not* 'either work or not', and can cause some
very odd connection symptoms. It's certainly worth checking whether
there are new drivers every so often, and I believe the BPA warns if
drivers are old, even though it doesn't know if there are later ones.

--
Joe