My SBS 2000 Server has developed an issue where by if I
reboot the server it takes about 20 minutes to get to the
point of displaying a log on screen and then takes about
15 minutes to actually work through to the desktop of the
logging on user. The user is using roaming profiles, but
the profile size is only about 1MB and is stored on the
server. This is far longer than it used to take a week or
so ago.
If I look through the event log the System log shows a
gap (lack of entries) for the 15 minutes or so whilst the
logon is being processed. The Application log however,
shows several Userenv errors with Event ID 1000 stating
that:

Windows cannot obtain the domain controller name for your
computer network. Return value (2102).

I have also had a problem were my machine was unable to
access the Internet (via our ADSL router) although it
could ping other machines on this side of the router and
the router IP address itself, it could not ping any
hostname or IP address on the far side of the router.
Once the server has finished logging on the user it
performs fairly normally. This was resolved by restarting
the server. Everything else I tried made no difference.

There have also been problems of Terminal Service clients
unable to connect today even though all seems well. Also
the Performance Logs and Alerts service and the SNMP
Service both fail to start. The Performance Logs and
Alerts service starts if you try to start it but then
when you refresh the service list it shows it as not
started again. No error message is seen. The SNMP Service
returns an error:

Could not start the SNMP Service service on Local
Computer. The service did not return an error. This could
be an internal Windows error an internal service error.
If the problem persists, contact your system
administrator.

Sorry if this is a lot of information to take in and
consider but it has all started happening in the last two
days and so would suggest that to some degree it may all
be related.

Thank you in advance for any help, comments or
suggestions you may be able to make.

James

Re: Reboot and First Logon takes over 30 minutes by Marina

Marina
Tue Feb 10 15:36:05 CST 2004

How many nics in the server? Check the bindingorder (Network Connections,
Advanced, Advanced) and make sure the internal nic is on top.
Can you post the ipconfig/all please?

--
Regards,

Marina
Microsoft SBS-MVP

"James Sellwood" <anonymous@discussions.microsoft.com> schreef in bericht
news:dddf01c3efeb$50f396c0$a401280a@phx.gbl...
> My SBS 2000 Server has developed an issue where by if I
> reboot the server it takes about 20 minutes to get to the
> point of displaying a log on screen and then takes about
> 15 minutes to actually work through to the desktop of the
> logging on user. The user is using roaming profiles, but
> the profile size is only about 1MB and is stored on the
> server. This is far longer than it used to take a week or
> so ago.
> If I look through the event log the System log shows a
> gap (lack of entries) for the 15 minutes or so whilst the
> logon is being processed. The Application log however,
> shows several Userenv errors with Event ID 1000 stating
> that:
>
> Windows cannot obtain the domain controller name for your
> computer network. Return value (2102).
>
> I have also had a problem were my machine was unable to
> access the Internet (via our ADSL router) although it
> could ping other machines on this side of the router and
> the router IP address itself, it could not ping any
> hostname or IP address on the far side of the router.
> Once the server has finished logging on the user it
> performs fairly normally. This was resolved by restarting
> the server. Everything else I tried made no difference.
>
> There have also been problems of Terminal Service clients
> unable to connect today even though all seems well. Also
> the Performance Logs and Alerts service and the SNMP
> Service both fail to start. The Performance Logs and
> Alerts service starts if you try to start it but then
> when you refresh the service list it shows it as not
> started again. No error message is seen. The SNMP Service
> returns an error:
>
> Could not start the SNMP Service service on Local
> Computer. The service did not return an error. This could
> be an internal Windows error an internal service error.
> If the problem persists, contact your system
> administrator.
>
> Sorry if this is a lot of information to take in and
> consider but it has all started happening in the last two
> days and so would suggest that to some degree it may all
> be related.
>
> Thank you in advance for any help, comments or
> suggestions you may be able to make.
>
> James
>



Re: Reboot and First Logon takes over 30 minutes by James

James
Wed Feb 11 03:46:12 CST 2004

The server had 2 NICs at the time. I have since added a third (although
immediately disabled it) as I was worried it may be a faulty network card
causing the problem.
The binding order is correct, internal NIC at the top.
I would rather not post the ipconfig /all as it will show all our IP address
settings on this public newsgroup but I will outline what they show.

Internal NIC:
IP Address: 192.168.16.2
Subnet Mask: 255.255.255.0
Default Gateway:
DNS Servers: 192.168.16.2
Primary WINS: 192.168.16.2

External NIC:
IP Address: ISP Provided IP Address
Subnet Mask: ISP Provided Subnet Mask
Default Gateway: Broadband Router IP Address
DNS Servers: ISP Provided DNS Address
ISP Provided DNS Address

As far as I am aware this should be right. I have not had any problems
previously.

James



"Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in message
news:99cWb.4381$ks5.9197@typhoon.bart.nl...
> How many nics in the server? Check the bindingorder (Network Connections,
> Advanced, Advanced) and make sure the internal nic is on top.
> Can you post the ipconfig/all please?
>
> --
> Regards,
>
> Marina
> Microsoft SBS-MVP
>
> "James Sellwood" <anonymous@discussions.microsoft.com> schreef in bericht
> news:dddf01c3efeb$50f396c0$a401280a@phx.gbl...
> > My SBS 2000 Server has developed an issue where by if I
> > reboot the server it takes about 20 minutes to get to the
> > point of displaying a log on screen and then takes about
> > 15 minutes to actually work through to the desktop of the
> > logging on user. The user is using roaming profiles, but
> > the profile size is only about 1MB and is stored on the
> > server. This is far longer than it used to take a week or
> > so ago.
> > If I look through the event log the System log shows a
> > gap (lack of entries) for the 15 minutes or so whilst the
> > logon is being processed. The Application log however,
> > shows several Userenv errors with Event ID 1000 stating
> > that:
> >
> > Windows cannot obtain the domain controller name for your
> > computer network. Return value (2102).
> >
> > I have also had a problem were my machine was unable to
> > access the Internet (via our ADSL router) although it
> > could ping other machines on this side of the router and
> > the router IP address itself, it could not ping any
> > hostname or IP address on the far side of the router.
> > Once the server has finished logging on the user it
> > performs fairly normally. This was resolved by restarting
> > the server. Everything else I tried made no difference.
> >
> > There have also been problems of Terminal Service clients
> > unable to connect today even though all seems well. Also
> > the Performance Logs and Alerts service and the SNMP
> > Service both fail to start. The Performance Logs and
> > Alerts service starts if you try to start it but then
> > when you refresh the service list it shows it as not
> > started again. No error message is seen. The SNMP Service
> > returns an error:
> >
> > Could not start the SNMP Service service on Local
> > Computer. The service did not return an error. This could
> > be an internal Windows error an internal service error.
> > If the problem persists, contact your system
> > administrator.
> >
> > Sorry if this is a lot of information to take in and
> > consider but it has all started happening in the last two
> > days and so would suggest that to some degree it may all
> > be related.
> >
> > Thank you in advance for any help, comments or
> > suggestions you may be able to make.
> >
> > James
> >
>
>



Re: Reboot and First Logon takes over 30 minutes by Marina

Marina
Wed Feb 11 05:48:37 CST 2004

You better stick a router between you 2nd nic and the ADSL-modem, so you can
give that 2nd nic a private IP-range (different from your internal range).
Anyway, DNS on your 2nd nic should *only* point to your DNS-server. Change
that and rerun the ICW-wizard.
Make sure the external IP-range is not in the LAT of ISA.
Do you use RRAS as well? In that case, make sure you've applied the regedits
in 292822.

--
Regards,

Marina
Microsoft SBS-MVP

"James Sellwood" <JamesSellwood@microsoft.public.backoffice.smallbiz2000>
schreef in bericht news:uBJ0xQI8DHA.712@tk2msftngp13.phx.gbl...
> The server had 2 NICs at the time. I have since added a third (although
> immediately disabled it) as I was worried it may be a faulty network card
> causing the problem.
> The binding order is correct, internal NIC at the top.
> I would rather not post the ipconfig /all as it will show all our IP
address
> settings on this public newsgroup but I will outline what they show.
>
> Internal NIC:
> IP Address: 192.168.16.2
> Subnet Mask: 255.255.255.0
> Default Gateway:
> DNS Servers: 192.168.16.2
> Primary WINS: 192.168.16.2
>
> External NIC:
> IP Address: ISP Provided IP Address
> Subnet Mask: ISP Provided Subnet Mask
> Default Gateway: Broadband Router IP Address
> DNS Servers: ISP Provided DNS Address
> ISP Provided DNS Address
>
> As far as I am aware this should be right. I have not had any problems
> previously.
>
> James
>
>
>
> "Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in
message
> news:99cWb.4381$ks5.9197@typhoon.bart.nl...
> > How many nics in the server? Check the bindingorder (Network
Connections,
> > Advanced, Advanced) and make sure the internal nic is on top.
> > Can you post the ipconfig/all please?
> >
> > --
> > Regards,
> >
> > Marina
> > Microsoft SBS-MVP
> >
> > "James Sellwood" <anonymous@discussions.microsoft.com> schreef in
bericht
> > news:dddf01c3efeb$50f396c0$a401280a@phx.gbl...
> > > My SBS 2000 Server has developed an issue where by if I
> > > reboot the server it takes about 20 minutes to get to the
> > > point of displaying a log on screen and then takes about
> > > 15 minutes to actually work through to the desktop of the
> > > logging on user. The user is using roaming profiles, but
> > > the profile size is only about 1MB and is stored on the
> > > server. This is far longer than it used to take a week or
> > > so ago.
> > > If I look through the event log the System log shows a
> > > gap (lack of entries) for the 15 minutes or so whilst the
> > > logon is being processed. The Application log however,
> > > shows several Userenv errors with Event ID 1000 stating
> > > that:
> > >
> > > Windows cannot obtain the domain controller name for your
> > > computer network. Return value (2102).
> > >
> > > I have also had a problem were my machine was unable to
> > > access the Internet (via our ADSL router) although it
> > > could ping other machines on this side of the router and
> > > the router IP address itself, it could not ping any
> > > hostname or IP address on the far side of the router.
> > > Once the server has finished logging on the user it
> > > performs fairly normally. This was resolved by restarting
> > > the server. Everything else I tried made no difference.
> > >
> > > There have also been problems of Terminal Service clients
> > > unable to connect today even though all seems well. Also
> > > the Performance Logs and Alerts service and the SNMP
> > > Service both fail to start. The Performance Logs and
> > > Alerts service starts if you try to start it but then
> > > when you refresh the service list it shows it as not
> > > started again. No error message is seen. The SNMP Service
> > > returns an error:
> > >
> > > Could not start the SNMP Service service on Local
> > > Computer. The service did not return an error. This could
> > > be an internal Windows error an internal service error.
> > > If the problem persists, contact your system
> > > administrator.
> > >
> > > Sorry if this is a lot of information to take in and
> > > consider but it has all started happening in the last two
> > > days and so would suggest that to some degree it may all
> > > be related.
> > >
> > > Thank you in advance for any help, comments or
> > > suggestions you may be able to make.
> > >
> > > James
> > >
> >
> >
>
>



Re: Reboot and First Logon takes over 30 minutes by James

James
Wed Feb 11 06:13:47 CST 2004

I am confused? I may have not explained myself correctly

The server is 2000SBS which has ISA as firewall running. The internal NIC is
on the internal network and the external NIC is connected to the Broadband
Router which then connects to the ADSL line.


INTERNAL SERVER SERVER
NETWORK - INTERNAL - EXTERNAL - ROUTER -
ADSL Line
NIC NIC

The internal NIC points to the server as its DNS server. The DNS server
service has forwarders set up to point to the ISP Provided Internet based
DNS servers. The external NIC also points to the ISP Provided Internet based
DNS servers for its DNS. The external NIC uses an IP Address provided by the
ISP as being our side of the Router. This address range is not in ISA's LAT.
Is this wrong? It has been working fine. If there is a better way please let
me know, and why (security, functionality, speed ?).

We do use RRAS. I will take a look at that KB article, thanks.

James



"Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in message
news:pEoWb.4390$ks5.9659@typhoon.bart.nl...
> You better stick a router between you 2nd nic and the ADSL-modem, so you
can
> give that 2nd nic a private IP-range (different from your internal range).
> Anyway, DNS on your 2nd nic should *only* point to your DNS-server. Change
> that and rerun the ICW-wizard.
> Make sure the external IP-range is not in the LAT of ISA.
> Do you use RRAS as well? In that case, make sure you've applied the
regedits
> in 292822.
>
> --
> Regards,
>
> Marina
> Microsoft SBS-MVP
>
> "James Sellwood" <JamesSellwood@microsoft.public.backoffice.smallbiz2000>
> schreef in bericht news:uBJ0xQI8DHA.712@tk2msftngp13.phx.gbl...
> > The server had 2 NICs at the time. I have since added a third (although
> > immediately disabled it) as I was worried it may be a faulty network
card
> > causing the problem.
> > The binding order is correct, internal NIC at the top.
> > I would rather not post the ipconfig /all as it will show all our IP
> address
> > settings on this public newsgroup but I will outline what they show.
> >
> > Internal NIC:
> > IP Address: 192.168.16.2
> > Subnet Mask: 255.255.255.0
> > Default Gateway:
> > DNS Servers: 192.168.16.2
> > Primary WINS: 192.168.16.2
> >
> > External NIC:
> > IP Address: ISP Provided IP Address
> > Subnet Mask: ISP Provided Subnet Mask
> > Default Gateway: Broadband Router IP Address
> > DNS Servers: ISP Provided DNS Address
> > ISP Provided DNS Address
> >
> > As far as I am aware this should be right. I have not had any problems
> > previously.
> >
> > James
> >
> >
> >
> > "Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in
> message
> > news:99cWb.4381$ks5.9197@typhoon.bart.nl...
> > > How many nics in the server? Check the bindingorder (Network
> Connections,
> > > Advanced, Advanced) and make sure the internal nic is on top.
> > > Can you post the ipconfig/all please?
> > >
> > > --
> > > Regards,
> > >
> > > Marina
> > > Microsoft SBS-MVP
> > >
> > > "James Sellwood" <anonymous@discussions.microsoft.com> schreef in
> bericht
> > > news:dddf01c3efeb$50f396c0$a401280a@phx.gbl...
> > > > My SBS 2000 Server has developed an issue where by if I
> > > > reboot the server it takes about 20 minutes to get to the
> > > > point of displaying a log on screen and then takes about
> > > > 15 minutes to actually work through to the desktop of the
> > > > logging on user. The user is using roaming profiles, but
> > > > the profile size is only about 1MB and is stored on the
> > > > server. This is far longer than it used to take a week or
> > > > so ago.
> > > > If I look through the event log the System log shows a
> > > > gap (lack of entries) for the 15 minutes or so whilst the
> > > > logon is being processed. The Application log however,
> > > > shows several Userenv errors with Event ID 1000 stating
> > > > that:
> > > >
> > > > Windows cannot obtain the domain controller name for your
> > > > computer network. Return value (2102).
> > > >
> > > > I have also had a problem were my machine was unable to
> > > > access the Internet (via our ADSL router) although it
> > > > could ping other machines on this side of the router and
> > > > the router IP address itself, it could not ping any
> > > > hostname or IP address on the far side of the router.
> > > > Once the server has finished logging on the user it
> > > > performs fairly normally. This was resolved by restarting
> > > > the server. Everything else I tried made no difference.
> > > >
> > > > There have also been problems of Terminal Service clients
> > > > unable to connect today even though all seems well. Also
> > > > the Performance Logs and Alerts service and the SNMP
> > > > Service both fail to start. The Performance Logs and
> > > > Alerts service starts if you try to start it but then
> > > > when you refresh the service list it shows it as not
> > > > started again. No error message is seen. The SNMP Service
> > > > returns an error:
> > > >
> > > > Could not start the SNMP Service service on Local
> > > > Computer. The service did not return an error. This could
> > > > be an internal Windows error an internal service error.
> > > > If the problem persists, contact your system
> > > > administrator.
> > > >
> > > > Sorry if this is a lot of information to take in and
> > > > consider but it has all started happening in the last two
> > > > days and so would suggest that to some degree it may all
> > > > be related.
> > > >
> > > > Thank you in advance for any help, comments or
> > > > suggestions you may be able to make.
> > > >
> > > > James
> > > >
> > >
> > >
> >
> >
>
>



Re: Reboot and First Logon takes over 30 minutes by James

James
Wed Feb 11 06:17:40 CST 2004

I have read through the article and we are not experiencing any of these
issues. Everything else works fine. The only recent issue is the time delay
whilst booting and logging on.

Thanks

James


"Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in message
news:pEoWb.4390$ks5.9659@typhoon.bart.nl...
> You better stick a router between you 2nd nic and the ADSL-modem, so you
can
> give that 2nd nic a private IP-range (different from your internal range).
> Anyway, DNS on your 2nd nic should *only* point to your DNS-server. Change
> that and rerun the ICW-wizard.
> Make sure the external IP-range is not in the LAT of ISA.
> Do you use RRAS as well? In that case, make sure you've applied the
regedits
> in 292822.
>
> --
> Regards,
>
> Marina
> Microsoft SBS-MVP
>
> "James Sellwood" <JamesSellwood@microsoft.public.backoffice.smallbiz2000>
> schreef in bericht news:uBJ0xQI8DHA.712@tk2msftngp13.phx.gbl...
> > The server had 2 NICs at the time. I have since added a third (although
> > immediately disabled it) as I was worried it may be a faulty network
card
> > causing the problem.
> > The binding order is correct, internal NIC at the top.
> > I would rather not post the ipconfig /all as it will show all our IP
> address
> > settings on this public newsgroup but I will outline what they show.
> >
> > Internal NIC:
> > IP Address: 192.168.16.2
> > Subnet Mask: 255.255.255.0
> > Default Gateway:
> > DNS Servers: 192.168.16.2
> > Primary WINS: 192.168.16.2
> >
> > External NIC:
> > IP Address: ISP Provided IP Address
> > Subnet Mask: ISP Provided Subnet Mask
> > Default Gateway: Broadband Router IP Address
> > DNS Servers: ISP Provided DNS Address
> > ISP Provided DNS Address
> >
> > As far as I am aware this should be right. I have not had any problems
> > previously.
> >
> > James
> >
> >
> >
> > "Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in
> message
> > news:99cWb.4381$ks5.9197@typhoon.bart.nl...
> > > How many nics in the server? Check the bindingorder (Network
> Connections,
> > > Advanced, Advanced) and make sure the internal nic is on top.
> > > Can you post the ipconfig/all please?
> > >
> > > --
> > > Regards,
> > >
> > > Marina
> > > Microsoft SBS-MVP
> > >
> > > "James Sellwood" <anonymous@discussions.microsoft.com> schreef in
> bericht
> > > news:dddf01c3efeb$50f396c0$a401280a@phx.gbl...
> > > > My SBS 2000 Server has developed an issue where by if I
> > > > reboot the server it takes about 20 minutes to get to the
> > > > point of displaying a log on screen and then takes about
> > > > 15 minutes to actually work through to the desktop of the
> > > > logging on user. The user is using roaming profiles, but
> > > > the profile size is only about 1MB and is stored on the
> > > > server. This is far longer than it used to take a week or
> > > > so ago.
> > > > If I look through the event log the System log shows a
> > > > gap (lack of entries) for the 15 minutes or so whilst the
> > > > logon is being processed. The Application log however,
> > > > shows several Userenv errors with Event ID 1000 stating
> > > > that:
> > > >
> > > > Windows cannot obtain the domain controller name for your
> > > > computer network. Return value (2102).
> > > >
> > > > I have also had a problem were my machine was unable to
> > > > access the Internet (via our ADSL router) although it
> > > > could ping other machines on this side of the router and
> > > > the router IP address itself, it could not ping any
> > > > hostname or IP address on the far side of the router.
> > > > Once the server has finished logging on the user it
> > > > performs fairly normally. This was resolved by restarting
> > > > the server. Everything else I tried made no difference.
> > > >
> > > > There have also been problems of Terminal Service clients
> > > > unable to connect today even though all seems well. Also
> > > > the Performance Logs and Alerts service and the SNMP
> > > > Service both fail to start. The Performance Logs and
> > > > Alerts service starts if you try to start it but then
> > > > when you refresh the service list it shows it as not
> > > > started again. No error message is seen. The SNMP Service
> > > > returns an error:
> > > >
> > > > Could not start the SNMP Service service on Local
> > > > Computer. The service did not return an error. This could
> > > > be an internal Windows error an internal service error.
> > > > If the problem persists, contact your system
> > > > administrator.
> > > >
> > > > Sorry if this is a lot of information to take in and
> > > > consider but it has all started happening in the last two
> > > > days and so would suggest that to some degree it may all
> > > > be related.
> > > >
> > > > Thank you in advance for any help, comments or
> > > > suggestions you may be able to make.
> > > >
> > > > James
> > > >
> > >
> > >
> >
> >
>
>



Re: Reboot and First Logon takes over 30 minutes by Jim

Jim
Wed Feb 11 09:00:12 CST 2004

You will have problems if your external nic is pointing to your isp
dns. You will have problems if your internal nic is not at the top of
the binding order. I name my nics internal and external. No chance of
screwing up binding order then.

http://sbslinks.com/sbs2000router.htm

You do the edits in the 292822 article. Even if you are not having the
problems your server will do better as it prevents the problems from
ever happening.

"James Sellwood"
<JamesSellwood@microsoft.public.backoffice.smallbiz2000> wrote:

>I am confused? I may have not explained myself correctly
>
>The server is 2000SBS which has ISA as firewall running. The internal NIC is
>on the internal network and the external NIC is connected to the Broadband
>Router which then connects to the ADSL line.
>
>
>INTERNAL SERVER SERVER
>NETWORK - INTERNAL - EXTERNAL - ROUTER -
>ADSL Line
> NIC NIC
>
>The internal NIC points to the server as its DNS server. The DNS server
>service has forwarders set up to point to the ISP Provided Internet based
>DNS servers. The external NIC also points to the ISP Provided Internet based
>DNS servers for its DNS. The external NIC uses an IP Address provided by the
>ISP as being our side of the Router. This address range is not in ISA's LAT.
>Is this wrong? It has been working fine. If there is a better way please let
>me know, and why (security, functionality, speed ?).
>
>We do use RRAS. I will take a look at that KB article, thanks.
>
>James
>
>
>
>"Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in message
>news:pEoWb.4390$ks5.9659@typhoon.bart.nl...
>> You better stick a router between you 2nd nic and the ADSL-modem, so you
>can
>> give that 2nd nic a private IP-range (different from your internal range).
>> Anyway, DNS on your 2nd nic should *only* point to your DNS-server. Change
>> that and rerun the ICW-wizard.
>> Make sure the external IP-range is not in the LAT of ISA.
>> Do you use RRAS as well? In that case, make sure you've applied the
>regedits
>> in 292822.
>>
>> --
>> Regards,
>>
>> Marina
>> Microsoft SBS-MVP
>>
>> "James Sellwood" <JamesSellwood@microsoft.public.backoffice.smallbiz2000>
>> schreef in bericht news:uBJ0xQI8DHA.712@tk2msftngp13.phx.gbl...
>> > The server had 2 NICs at the time. I have since added a third (although
>> > immediately disabled it) as I was worried it may be a faulty network
>card
>> > causing the problem.
>> > The binding order is correct, internal NIC at the top.
>> > I would rather not post the ipconfig /all as it will show all our IP
>> address
>> > settings on this public newsgroup but I will outline what they show.
>> >
>> > Internal NIC:
>> > IP Address: 192.168.16.2
>> > Subnet Mask: 255.255.255.0
>> > Default Gateway:
>> > DNS Servers: 192.168.16.2
>> > Primary WINS: 192.168.16.2
>> >
>> > External NIC:
>> > IP Address: ISP Provided IP Address
>> > Subnet Mask: ISP Provided Subnet Mask
>> > Default Gateway: Broadband Router IP Address
>> > DNS Servers: ISP Provided DNS Address
>> > ISP Provided DNS Address
>> >
>> > As far as I am aware this should be right. I have not had any problems
>> > previously.
>> >
>> > James
>> >
>> >
>> >
>> > "Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in
>> message
>> > news:99cWb.4381$ks5.9197@typhoon.bart.nl...
>> > > How many nics in the server? Check the bindingorder (Network
>> Connections,
>> > > Advanced, Advanced) and make sure the internal nic is on top.
>> > > Can you post the ipconfig/all please?
>> > >
>> > > --
>> > > Regards,
>> > >
>> > > Marina
>> > > Microsoft SBS-MVP
>> > >
>> > > "James Sellwood" <anonymous@discussions.microsoft.com> schreef in
>> bericht
>> > > news:dddf01c3efeb$50f396c0$a401280a@phx.gbl...
>> > > > My SBS 2000 Server has developed an issue where by if I
>> > > > reboot the server it takes about 20 minutes to get to the
>> > > > point of displaying a log on screen and then takes about
>> > > > 15 minutes to actually work through to the desktop of the
>> > > > logging on user. The user is using roaming profiles, but
>> > > > the profile size is only about 1MB and is stored on the
>> > > > server. This is far longer than it used to take a week or
>> > > > so ago.
>> > > > If I look through the event log the System log shows a
>> > > > gap (lack of entries) for the 15 minutes or so whilst the
>> > > > logon is being processed. The Application log however,
>> > > > shows several Userenv errors with Event ID 1000 stating
>> > > > that:
>> > > >
>> > > > Windows cannot obtain the domain controller name for your
>> > > > computer network. Return value (2102).
>> > > >
>> > > > I have also had a problem were my machine was unable to
>> > > > access the Internet (via our ADSL router) although it
>> > > > could ping other machines on this side of the router and
>> > > > the router IP address itself, it could not ping any
>> > > > hostname or IP address on the far side of the router.
>> > > > Once the server has finished logging on the user it
>> > > > performs fairly normally. This was resolved by restarting
>> > > > the server. Everything else I tried made no difference.
>> > > >
>> > > > There have also been problems of Terminal Service clients
>> > > > unable to connect today even though all seems well. Also
>> > > > the Performance Logs and Alerts service and the SNMP
>> > > > Service both fail to start. The Performance Logs and
>> > > > Alerts service starts if you try to start it but then
>> > > > when you refresh the service list it shows it as not
>> > > > started again. No error message is seen. The SNMP Service
>> > > > returns an error:
>> > > >
>> > > > Could not start the SNMP Service service on Local
>> > > > Computer. The service did not return an error. This could
>> > > > be an internal Windows error an internal service error.
>> > > > If the problem persists, contact your system
>> > > > administrator.
>> > > >
>> > > > Sorry if this is a lot of information to take in and
>> > > > consider but it has all started happening in the last two
>> > > > days and so would suggest that to some degree it may all
>> > > > be related.
>> > > >
>> > > > Thank you in advance for any help, comments or
>> > > > suggestions you may be able to make.
>> > > >
>> > > > James
>> > > >
>> > >
>> > >
>> >
>> >
>>
>>
>

Jim B. SBS MVP
remove the mvp to send email

Re: Reboot and First Logon takes over 30 minutes by Duncan

Duncan
Wed Feb 11 20:39:17 CST 2004

In article <dddf01c3efeb$50f396c0$a401280a@phx.gbl>,
anonymous@discussions.microsoft.com says...
> My SBS 2000 Server has developed an issue where by if I
> reboot the server it takes about 20 minutes to get to the
> point of displaying a log on screen and then takes about
> 15 minutes to actually work through to the desktop of the
> logging on user. The user is using roaming profiles, but
> the profile size is only about 1MB and is stored on the
> server. This is far longer than it used to take a week or
> so ago.
> If I look through the event log the System log shows a
> gap (lack of entries) for the 15 minutes or so whilst the
> logon is being processed. The Application log however,
> shows several Userenv errors with Event ID 1000 stating
> that:
>
> Windows cannot obtain the domain controller name for your
> computer network. Return value (2102).
>
> I have also had a problem were my machine was unable to
> access the Internet (via our ADSL router) although it
> could ping other machines