Russ
Thu Mar 27 10:13:25 PDT 2008
Draino,
No offense here, but I really want to help and make SBS a wonderful
experience for you.
Looking at the last couple of posts of yours,
It appears this is your first SBS server?
For Most people it's best not to be messing with SBS,
SBS is not a regular Win2003 server, things are interconnected and rely on
other parts.
Despite how many years of IT experience you have, you need to forget 50% of
it when applying to SBS
It's best to Install everything on SBS and instead of Disabling or Hacking
your way through things.
So in other words Ignore what you don't want.
Disabling and Hacking around trying to get UBER Performance won't buy you
much.
For SBS to be happy, (And your self)
You should embrace some basics that SBS has to offer.
Not Doing this. Will Cause you MUCH pain and Grief in the long run.
and put your SBS in a Unsupported state.
(And you will HATE SBS)
Learn about RWW OWA OMA RPC over HTTP And you will find it's a really good
System.
I hope you reconsider your current path of hacking disabling etc.
Because now I just see you fighting your SBS box forever.
My 2 Cents.
Russ
--
SBITS.Biz
Microsoft Gold Certified Partner
Microsoft Certified Small Business Specialist.
MCP, MCPS, MCNPS, (MCP-SBS)
North America Remote SBS2003 Support -
http://www.SBITS.Biz
Information on Small Business Server 2008 -
http://www.sbs2008.com
Information on Essentials Business Server -
http://www.ebs2008.com
-
"-Draino-" <guest@unknown.com> wrote in message
news:O7EemdBkIHA.4356@TK2MSFTNGP02.phx.gbl...
> Thanks Brian,
>
> I will fix later today. My users say logon time are slow but they have
> been logging onto the workstations locally for years. Now that they have
> to log on to the "network" log on time will seem very slow to them.
>
> I checked the log on times myself at each workstation and the log on
> seemed within reason. Each user profile is about 50 megs total, so there
> is a delay to get that loaded.
>
> Should I put anything in the "Alternate DNS Server" box? Maybe 192.168.2.1
> or 127.0.0.1???
>
> On another note for using static IP addresses is that DHCP has been a
> problem because when ever I try to configure RRAS, just before the wizard
> is about to make changes it says that DHCP will be used to configure
> something. Maybe that is why I can't VPN into my Server, but not sure.
>
> If RRAS is only needed for VPN then I don't see a use for it. Maybe I can
> disable or delete it?
>
>
> Thanks,
>
> D
>
>
>
> "Brian Cryer" <brianc@127.0.0.1.activesol.co.uk> wrote in message
> news:OtfkSTBkIHA.4164@TK2MSFTNGP02.phx.gbl...
>> "-Draino-" <guest@unknown.com> wrote in message
>> news:9632B4A2-61D7-4952-BEB5-BEC98023FB45@microsoft.com...
>>>
>>> <snip>
>>>> Something else: since you are using static IP addresses can I confirm
>>>> that you are using the SBS server as your DNS server? If you are using
>>>> a router as your DNS server then you will get slow response times when
>>>> the pcs try to connect to the server (if they succeed at all).
>>>> --
>>>
>>>
>>> I am using the router as the the DNS server, 192.168.2.1
>>
>> That may well be your problem. Use your SBS server as your DNS server.
>>
>>> Workstation 1 is 192.168.2.2 and Workstation 2 is 192.16.2.3 and
>>> connected directly to the router.
>>>
>>> My SBS2003 is 192.168.2.16 and it also is connected directly to the
>>> router.
>>>
>>> Are you saying that on Workstation 1 & 2 I should change the "use the
>>> following DNS server from xxx.xxx.xxx.1 to xxx.xxx.xxx.16???
>>
>> Yes.
>>
>>> What about the Server itself?
>>
>> Be sure FIRST that the DNS service is correctly configured and working on
>> the server. Under Start > Administrative tools you should have DNS.
>> (There are probably other ways of getting to it, and there may well be a
>> wizard to configure it. I'm assuming its installed by default with SBS,
>> since I don't recall doing anything special to install it - but I could
>> be wrong.) Right click on your server and select properties, which will
>> let you edit all the pertinent properties of the SBS DNS server. Ensure
>> that on the "Forwarders" tab you have listed the IP address for your
>> router and/or the IP addresses that your router is using for its DNS.
>>
>> A simple way to test that its working properly is at the command prompt
>> to enter:
>> nslookup www.google.com 192.168.2.16
>> (given that 192.168.2.16 is the IP address of your server.) Also:
>> nslookup SERVERNAME 192.168.2.16
>> where SERVERNAME is the name of your SBS server should return virtually
>> straight away, whereas I would expect
>> nslookup SERVERNAME 192.168.2.1
>> to fail, because your router probably has no way of determing the IP
>> address of your server.
>>
>> I think this will result in your login times reducing because your
>> workstations will now be able to connect to your server. I don't know
>> what the situation is otherwise, perhaps if DNS fails to resolve a name
>> the pcs might be using WINS or a broadcast to try to identify the IP
>> address of your server. Don't know. What I do know is that when I was
>> fiddling on my home network recently to troubleshoot a problem I had the
>> router as DHCP server not the SBS box and as a consequence it took an age
>> for pcs to login - the fact that the router was the DHCP server in itself
>> wasn't significant it was that the pcs were interrogating the router for
>> the IP address of my server which was failing.
>>
>> Hope this helps. Post back if anything isn't clear.
>> --
>> Brian Cryer
>> www.cryer.co.uk/brian
>>
>>
>>