Re: Extremely slow logons

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



The firewall is the DHCP. It is a Sonicwall Pro 230.

I use the ISP's DNS (Time Warner).

It seems that the firewall DHCP sets all the machine to use the ISP's DNS.

You suggest me to set up DHCP on the SBS? How will my computers know to use
it as DHCP and not the firewall, besides a manual setting of all the
machines?


"Karl Middleton" <nospam@xxxxxxxxxx> wrote in message
news:eRScjxyhFHA.576@xxxxxxxxxxxxxxxxxxxxxxx
> Nicolas,
>
> Your problem sounds like name resolution problems. Where do your client
> computers point for DNS? SBS is happiest when it is your DHCP server, DNS
> server, WINS server. I am betting you still have the client computers
> pointing at the old NT box.
>
> Change them over and see if that improves things. SBS has a nice Connect
> Computer wizard that will join the clients to the SBS domain instead of
> the NT domain.
>
> Regards
> Karl from Oz
>
>
> "Nicolas Verhaeghe" <nospam_nicver@xxxxxxxxxxxxxxxx> wrote in message
> news:42d438d2$0$32200$39cecf19@xxxxxxxxxxxxxxxxxxxxx
>>I migrated my users from an NT4 domain to a SBS 2003 domain and now login
>>on is an excrutiatingly slow process.
>>
>> After entered the password, the message "Loading your personal settings"
>> is quickly replaced by a "Applying your personal settings" message which
>> stays on for 4 or 5 minutes before someone can use his computer.
>>
>> What is causing this problem?
>>
>> Another slowness is when I need to make a user local administrator. I go
>> to the Users control panel, when I am asked to provide a name for an
>> administrator. I choose to use a domain admnistrator account and it takes
>> also 5 minutes as well before I have access.
>>
>> What is wrong here?
>>
>> Is it the fact that the NT4 domain is still up and running?
>>
>
>


.



Relevant Pages

  • Re: DHCP on router or server
    ... Even if you move DHCP to the router, you'll discover that you have a problem with DNS lookups. ... Since DNS is an integral part of Active Directory, your clients should only be using internal DNS servers that have the various AD SRV records. ... First, I need to say that in a well designed system, SBS shouldn't be going down often enough for this to even be an issue. ... For companies that don't have the budget for a windows server, I have in rare instances set up a linux machine running BIND and configured it as a slave of the SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Site, DHCP Scope Issue
    ... user is going to call me tomorrow after they turn on the computers. ... When DHCP is disabled at the remote office, ... DNS) in that location. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Site, DHCP Scope Issue
    ... going to call me tomorrow after they turn on the computers. ... When DHCP is disabled at the remote office, ... Win2003 DC (running AD-integrated DNS) in that location. ...
    (microsoft.public.windows.server.sbs)
  • Re: Please help with small DHCP question
    ... should have log messages on either the client or the server. ... Connection-specific DNS Suffix. ... From the sounds of it the printer is operating as a DHCP source, ... sign that there is another DHCP source on the network would be that SBS ...
    (microsoft.public.windows.server.sbs)
  • Re: New disgruntled SBS 2008 premium user
    ... want us to disable our NAS dhcp and I can't do that because it's our ... AD registers info in DNS that is important to "find" the domain. ... clients must only use the SBS as their DNS address in their NIC ... If the router is ...
    (microsoft.public.windows.server.sbs)