Hi!
Thank You, that solved my problem. Everything works now perfectly!
- Partapiru -
"Doug Sherman [MVP]" <(E-Mail Removed)> kirjoitti
viestissä:(E-Mail Removed)...
> Assuming that the 193.100.100.100 gateway can reach these other subnets,
> then for each such subnet you would run the following command on the
> server:
>
> route -p add <IPofRemoteNetwork> mask <subnet mask of remote network>
> 193.100.100.100.
>
> For example, to reach a 192.168.1.x subnet you would run this command on
> the
> server:
>
> route -p add 192.168.1.0 mask 255.255.255.0 193.100.100.100.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "Partapiru" <(E-Mail Removed)> wrote in message
> news:e$(E-Mail Removed)...
>> Thanks for quick answering!
>>
>> There was a little mistake in my first message, the gw address is
>> 193.100.100.100 and so it is in th same subnet as Intranet nic. In this
>> subnet is also another web server (wsus) and clients have no problem
>> connecting it from other subnets. The setup in vlan is same (allowing
> http,
>> https all) for both wsus and intranet's addresses. First I tried to put
> the
>> gateway address in Intranet nic but it didn't work and server warned
>> about
>> this kind of multiple gateways configuration. In microsoft kb articles
> they
>> recommend using static route for solution. I tried all kind of route
>> commands but nothing worked.
>>
>> "Doug Sherman [MVP]" <(E-Mail Removed)> kirjoitti
>> viestissä:(E-Mail Removed)...
>> > If all of the intranet users are on the same
> 193.100.100.0/255.255.255.248
>> > subnet as the 193.100.100.101 NIC, then this is not a routing issue.
> Try:
>> >
>> > Right click My Network Places and select Properties. Click
>> > Advanced/Advanced settings and make sure the Local Area Connection for
> the
>> > intranet NIC is at the top of the binding order.
>> >
>> > If however, there are clients on other subnets and the gateway to those
>> > subnets is 193.100.100.1, you have multiple problems:
>> >
>> > 1. The 193.100.100.101 NIC has no route to the other subnets.
>> >
>> > 2. 193.100.100.101 cannot use the 193.100.100.1 gateway because the
>> > addresses are not on the same subnet.
>> >
>> > Doug Sherman
>> > MCSE, MCSA, MCP+I, MVP
>> >
>> > "Partapiru" <(E-Mail Removed)> wrote in message
>> > news:#(E-Mail Removed)...
>> >> I have a problem with my W2K3 Sp1. It's web server, first nic has a
> site
>> > in
>> >> internet and second in intranet, both on their own subnets. Internet
> site
>> > is
>> >> straight behind FW and intranet is in its own vlan, which has also two
> AD
>> >> domain controllers. Server is a member in AD domain for user
>> > authentication
>> >> in intranet..
>> >>
>> >> First nic (Internet):
>> >> ip 194.100.100.101
>> >> mask 255.255.255.240
>> >> gw 194.100.100.1
>> >>
>> >> Second nic (Intranet):
>> >> ip 193.100.100.101
>> >> mask 255.255.255.248
>> >> no gw address, because server gave warning about multiple default
>> > gateways.
>> >> (subnets gw address is 193.100.100.1)
>> >>
>> >> Problem is, that users can't connect to intranet, they get "site not
>> >> available...". Intranet's nic doesn't answer to ping. Earlier when
>> >> both
>> > nics
>> >> were in same subnet everything worked fine. I've got information that
>> >> problem could be solved using route command. Is it possible and if it
> is,
>> >> what would be right command?
>> >>
>> >> - Partapiru -
>> >>
>> >>
>> >
>> >
>>
>>
>
>
|
Similar Threads
Linear Mode
