In news:BFDEC1DA-298C-46F5-B4D0-(E-Mail Removed),
Keith the confused <(E-Mail Removed)> typed:
> Ok I figured this one out.
>
> The default script assigned to users by sbs contains one line and
> executes setup.exe /sb_server_name. If you login to a server that has
> a static IP on a seperate subnet from the SB server then that
> setup.exe changes the default gateway to that of the sbserver. all
> dhcp clients on the other subnet were left alone by the script.
>
> When I removed the script from the admin account my problems went
> away.
Admins shouldn't have login scripts or roaming profiles or much of anything,
in my book.
>
> both servers on dif subnets were dhcp, dns servers.
> A router on each subnet was doing the routing. my SB server is a one
> nic server.
>
> After I figured this out I checked the same on a earlier install with
> two sites and the same was true.
>
>> I have a memer 2003 server(192.168.17.2) on a seperate subnet from
>> the 2003 Small Business Server(192.168.16.2). The two subnets are
>> connected Via a dedicated point to point t1. Every time the member
>> server runs the default sbs logon script, the default gateway
>> changes, to 192.168.16.1 and my member server becomes unavailable to
>> users on the remote subnet.
>>
>> I want to run terminal services in "application mode" on the member
>> server but each remote session causes the script to run and renders
>> the server useless. I can't find any online info that shows others
>> having this problem, but I'm sure this is the problem.
I don't use the default SBS login script so I'm not sure what it contains.
I'd post in an SBS group for more help. Also look into login scripts
assigned via group policy, not per user in ADUC - more flexible depending on
where the users are logging in.
>>
>> Untill the third morning I had to change it back... I just figured I
>> was an idiot and not hitting apply or OK... now I know I'm sain but
>> my customer still still thinks I am an Idiot? Help please...
|
Similar Threads
Linear Mode
