look at using the 'route' command from the command prompt and then use
the -p switch at the end to make it persistant and survive a reboot.
e.g.
route add 10.154.3.64 mask 255.255.255.0 10.154.3.131 -p
Regards,
Alex
"Len B" <gonehome@optusnet:con:au> wrote in message
news:(E-Mail Removed)...
>I don't know where to look to find the answer to this situation. If you
>could give me some keywords to use, or point me in the right direction,
>that would be great.
>
> Starting situation
> N 10.154.3.128/255.255.255.224 (32 IPs) Controller = SBS2003
> S 10.154.3.96/255.255.255.224 (32 IPs) Controller = Win2k Server
>
> I changed it to
> N 10.154.3.128/255.255.255.224 (32 IPs) SBS2003
> S 10.154.3.64/255.255.255.192 (64 IPs) Win2k
> by replacing the scope in DHCP in S.
>
> After changes, route table on N contained this entry
>
> Destination Subnet Mask Gateway Interface
> 10.154.3.96 255.255.255.255.224 10.154.3.131 10.154.3.130
>
> I changed it to
>
> Destination Subnet Mask Gateway Interface
> 10.154.3.64 255.255.255.255.192 10.154.3.131 10.154.3.130
>
> I know that the routes are stored in the registry and the table is built
> at boot time but I shouldn't have to hack the registry, should I?
>
> What should I search on to understand what is (not) happening? Can you
> please point me at an article or a webpage to enlighten me? Should I have
> done something more than just replace the scope?
>
> As I was re-reading this I just had a silly thought about adding to N a
> scope matching the one on S and excluding all the addresses???
>
>
> --
> Len
> __________________________________________________ ____
>
>
|
Similar Threads
Linear Mode
