hi

i have been running an sbs2000 installation for 2 years (compaq proliant =
dl350, 512mb ram).

recently, several components of the server failed simultaneously. for =
example when i try to stop a service, the service manager tries to shut =
it down and then states that it cannot get the state of the service and =
service shows up as "Stopping" forever (accessing the properties of a =
service is also impossible: the MMC stops responding).
I cannot access the "network and dial-up connections" window nor does =
the network icon appear on the system tray. The server does not respond =
to incoming VPN connections and severall other odd behaviours.

The strange thing is that from the client computers everything looks =
fine: login is normal, outllook works fine (although most of the times =
exchange cannot deliver outbound messages) and we can access all file =
shares on the server perfectly.

Whenever I try to reboot the server takes a very long time to boot up =
when compared to another Windows 2000 Server (not DC) that exists on the =
network.
The server is running ISA (on which I already limited the caching =
behaviour since it was using a lot of memory and was showing a 700mb =
pagefile), Exchange and has some file shares.

I really have no clue on what to do and I would really appreciate all =
feedback.

Thank you
Pedro Ramilo

Re: sbs2000 services don't stop, vpn won't connect and so on... by Marina

Marina
Sun Oct 17 19:15:58 CDT 2004

Hi Pedro,

Is the server fully patched? Can you post the ipconfig/all from the server
please?

--
Regards,

Marina
Microsoft SBS-MVP

"Pedro Ramilo" <pramilo@DONTLIKESPAMsapo.pt> schreef in bericht
news:uGWZo7JtEHA.2788@TK2MSFTNGP09.phx.gbl...
hi

i have been running an sbs2000 installation for 2 years (compaq proliant
dl350, 512mb ram).

recently, several components of the server failed simultaneously. for
example when i try to stop a service, the service manager tries to shut it
down and then states that it cannot get the state of the service and service
shows up as "Stopping" forever (accessing the properties of a service is
also impossible: the MMC stops responding).
I cannot access the "network and dial-up connections" window nor does the
network icon appear on the system tray. The server does not respond to
incoming VPN connections and severall other odd behaviours.

The strange thing is that from the client computers everything looks fine:
login is normal, outllook works fine (although most of the times exchange
cannot deliver outbound messages) and we can access all file shares on the
server perfectly.

Whenever I try to reboot the server takes a very long time to boot up when
compared to another Windows 2000 Server (not DC) that exists on the network.
The server is running ISA (on which I already limited the caching behaviour
since it was using a lot of memory and was showing a 700mb pagefile),
Exchange and has some file shares.

I really have no clue on what to do and I would really appreciate all
feedback.

Thank you
Pedro Ramilo



Re: sbs2000 services don't stop, vpn won't connect and so on... by Pedro

Pedro
Mon Oct 18 19:02:08 CDT 2004

hi

first of all thank you for your interest in my post.

I must say that the server is fully patched (win2k SP4, ISA Sp2 and FP1, =
Exchange SP3 and windows update runs regularly)
I first detected this problem after a reboot when I installed two =
updates in exchange: kb836488 and kb870540 (I did not install kb 824282 =
since I understood that it had been superseeded by kb870540). After that =
I ran windows update which among some critical updates, installed new =
drivers for my network cards. I also "messed" a little with Local Policy =
and Domain Policy but unfortunantelly I cannot recall which settings I =
changed.

After all that I rebooted the server and since then I have been having =
these problems. I'm not sure if they are related to any of the recent =
updates but I already uninstalled the updates applyed to exchange and =
tryed to "move back" to the old drivers of the network cards (this last =
task I'm not sure if it was well suceeded since these problems affect =
almost all of the windows components). None of these actions worked.

Bellow is transcription of the ipconfig command you asked:
One last thing: I have previously experienced a slowlyness problem, some =
odd behaviours and some rare connectivity problems on the client side =
with this server due to a defective network cable that connected the =
server to the internal netwok and replacing the cable solved the =
problem. This time the sintoms are different in some ways (the clients =
don't seem to have any troubles) so i'm not sure if I should try this =
approach.

Thank you very much
Pedro Ramilo

------------------------------------- ipconfig/all =
----------------------------------------------

Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : sbs2000
Primary DNS Suffix . . . . . . . : GCE.PT
Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : GCE.PT

Ethernet adapter Placa Rede Interna :



Connection-specific DNS Suffix . :=20
Description . . . . . . . . . . . : Compaq NC3163 Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-02-A5-EA-78-AF

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.16.1

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :=20

DNS Servers . . . . . . . . . . . : 192.168.16.1
Primary WINS Server . . . . . . . : 192.168.16.1


Ethernet adapter Rede Externa:



Connection-specific DNS Suffix . :=20
Description . . . . . . . . . . . : Compaq NC3123 Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-02-A5-43-EE-48

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.0.0.2

Subnet Mask . . . . . . . . . . . : 255.0.0.0

Default Gateway . . . . . . . . . : 10.0.0.138

DNS Servers . . . . . . . . . . . : 10.0.0.138
NetBIOS over Tcpip. . . . . . . . : Disabled

-------------------------------------------------------------------------=
---------------





"Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in =
message news:ercqneKtEHA.2596@TK2MSFTNGP15.phx.gbl...
> Hi Pedro,
>=20
> Is the server fully patched? Can you post the ipconfig/all from the =
server
> please?
>=20
> --=20
> Regards,
>=20
> Marina
> Microsoft SBS-MVP
>=20
> "Pedro Ramilo" <pramilo@DONTLIKESPAMsapo.pt> schreef in bericht
> news:uGWZo7JtEHA.2788@TK2MSFTNGP09.phx.gbl...
> hi
>=20
> i have been running an sbs2000 installation for 2 years (compaq =
proliant
> dl350, 512mb ram).
>=20
> recently, several components of the server failed simultaneously. for
> example when i try to stop a service, the service manager tries to =
shut it
> down and then states that it cannot get the state of the service and =
service
> shows up as "Stopping" forever (accessing the properties of a service =
is
> also impossible: the MMC stops responding).
> I cannot access the "network and dial-up connections" window nor does =
the
> network icon appear on the system tray. The server does not respond to
> incoming VPN connections and severall other odd behaviours.
>=20
> The strange thing is that from the client computers everything looks =
fine:
> login is normal, outllook works fine (although most of the times =
exchange
> cannot deliver outbound messages) and we can access all file shares on =
the
> server perfectly.
>=20
> Whenever I try to reboot the server takes a very long time to boot up =
when
> compared to another Windows 2000 Server (not DC) that exists on the =
network.
> The server is running ISA (on which I already limited the caching =
behaviour
> since it was using a lot of memory and was showing a 700mb pagefile),
> Exchange and has some file shares.
>=20
> I really have no clue on what to do and I would really appreciate all
> feedback.
>=20
> Thank you
> Pedro Ramilo
>=20
>

Re: sbs2000 services don't stop, vpn won't connect and so on... by Marina

Marina
Mon Oct 18 19:22:57 CDT 2004

Hi Pedro,

Never ever install hardware drivers with Windows Update.
DNS on your external nic should only point to your server-IP. Check the
bindingorder in Network Connections, Advanced, Advanced and make sure the
internal nic is on top. Rerun ICW.
Go to Windows Update and do install all the critical updates that you see.
Anything in the eventlogs?

--
Regards,

Marina
Microsoft SBS-MVP

"Pedro Ramilo" <pramilo@DONTLIKESPAMsapo.pt> schreef in bericht
news:OPoxi7WtEHA.1048@tk2msftngp13.phx.gbl...
hi

first of all thank you for your interest in my post.

I must say that the server is fully patched (win2k SP4, ISA Sp2 and FP1,
Exchange SP3 and windows update runs regularly)
I first detected this problem after a reboot when I installed two updates in
exchange: kb836488 and kb870540 (I did not install kb 824282 since I
understood that it had been superseeded by kb870540). After that I ran
windows update which among some critical updates, installed new drivers for
my network cards. I also "messed" a little with Local Policy and Domain
Policy but unfortunantelly I cannot recall which settings I changed.

After all that I rebooted the server and since then I have been having these
problems. I'm not sure if they are related to any of the recent updates but
I already uninstalled the updates applyed to exchange and tryed to "move
back" to the old drivers of the network cards (this last task I'm not sure
if it was well suceeded since these problems affect almost all of the
windows components). None of these actions worked.

Bellow is transcription of the ipconfig command you asked:
One last thing: I have previously experienced a slowlyness problem, some odd
behaviours and some rare connectivity problems on the client side with this
server due to a defective network cable that connected the server to the
internal netwok and replacing the cable solved the problem. This time the
sintoms are different in some ways (the clients don't seem to have any
troubles) so i'm not sure if I should try this approach.

Thank you very much
Pedro Ramilo

-------------------------------------
ipconfig/all ----------------------------------------------

Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : sbs2000
Primary DNS Suffix . . . . . . . : GCE.PT
Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : GCE.PT

Ethernet adapter Placa Rede Interna :



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Compaq NC3163 Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-02-A5-EA-78-AF

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.16.1

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 192.168.16.1
Primary WINS Server . . . . . . . : 192.168.16.1


Ethernet adapter Rede Externa:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Compaq NC3123 Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-02-A5-43-EE-48

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.0.0.2

Subnet Mask . . . . . . . . . . . : 255.0.0.0

Default Gateway . . . . . . . . . : 10.0.0.138

DNS Servers . . . . . . . . . . . : 10.0.0.138
NetBIOS over Tcpip. . . . . . . . : Disabled

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





"Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in message
news:ercqneKtEHA.2596@TK2MSFTNGP15.phx.gbl...
> Hi Pedro,
>
> Is the server fully patched? Can you post the ipconfig/all from the server
> please?
>
> --
> Regards,
>
> Marina
> Microsoft SBS-MVP
>
> "Pedro Ramilo" <pramilo@DONTLIKESPAMsapo.pt> schreef in bericht
> news:uGWZo7JtEHA.2788@TK2MSFTNGP09.phx.gbl...
> hi
>
> i have been running an sbs2000 installation for 2 years (compaq proliant
> dl350, 512mb ram).
>
> recently, several components of the server failed simultaneously. for
> example when i try to stop a service, the service manager tries to shut it
> down and then states that it cannot get the state of the service and
service
> shows up as "Stopping" forever (accessing the properties of a service is
> also impossible: the MMC stops responding).
> I cannot access the "network and dial-up connections" window nor does the
> network icon appear on the system tray. The server does not respond to
> incoming VPN connections and severall other odd behaviours.
>
> The strange thing is that from the client computers everything looks fine:
> login is normal, outllook works fine (although most of the times exchange
> cannot deliver outbound messages) and we can access all file shares on the
> server perfectly.
>
> Whenever I try to reboot the server takes a very long time to boot up when
> compared to another Windows 2000 Server (not DC) that exists on the
network.
> The server is running ISA (on which I already limited the caching
behaviour
> since it was using a lot of memory and was showing a 700mb pagefile),
> Exchange and has some file shares.
>
> I really have no clue on what to do and I would really appreciate all
> feedback.
>
> Thank you
> Pedro Ramilo
>
>