Different route to server

I've got Windows Server 2008 on my network, which is acting mainly as a file
server. It's reached via my wireless/wired router, which has a 100Mb
Ethernet connection. That's fine for all of the wireless connections, but
I'd also like to make use of the second NICs on the server itself, and the
desktop which is in the same vicinity, which can both support Gigabit LAN.

I've bought a suitable crossover cable, and have managed to prove that I can
transfer files across it, but I get problems with many things like Remote
Desktop etc. How can I force any traffic from the nearby desktop destined
for the server to go via the Gigabit LAN, but at the same time, ensure that
any Internet traffic goes directly to the router?

I hope that makes sense. I did wonder if I could just refer to connections
requiring Gigabit connection by the Static IP address I'd assigned, but that
didn't seem to work. I read something about Auto Metric, but didn't really
understand what I was reading, nor was fully convinced that it was totally
relevant.

Thanks

John

"John Whitworth" <sexyjw@g_EEEEEEEEEEEEEEEEE_mail.com> wrote in message
news:484ee14b$0$26085$(E-Mail Removed)...
> I've got Windows Server 2008 on my network, which is acting mainly as a
> file server. It's reached via my wireless/wired router, which has a 100Mb
> Ethernet connection. That's fine for all of the wireless connections, but
> I'd also like to make use of the second NICs on the server itself, and the
> desktop which is in the same vicinity, which can both support Gigabit LAN.
>
> I've bought a suitable crossover cable, and have managed to prove that I
> can transfer files across it, but I get problems with many things like
> Remote Desktop etc. How can I force any traffic from the nearby desktop
> destined for the server to go via the Gigabit LAN, but at the same time,
> ensure that any Internet traffic goes directly to the router?
>
> I hope that makes sense. I did wonder if I could just refer to connections
> requiring Gigabit connection by the Static IP address I'd assigned, but
> that didn't seem to work. I read something about Auto Metric, but didn't
> really understand what I was reading, nor was fully convinced that it was
> totally relevant.
>
> Thanks
>
> John

Connecting a machine to two networks is like opening a can of worms. It's
hard to see exactly what is what.

The first thing to do is make sure that the two NICs are in different IP
subnets. The next thing to do is ensure that only one NIC (the one connected
to the Internet router) has a default gateway set. Internet traffic will
always use that interface.

The main problem is name resolution. If there are two IP addresses
associated with the machine's name you will have odd problems if the name
resolves to the "wrong" IP. People do not usually use IP addresses when they
share files. They use machine names.

If you can make sure that the machine name resolves to the "right" IP
address the traffic will go through the "right" interface. For example if
the packet is addressed to 192.168.12.12 and the machine has a 192.168.12.x
interface, that is where it will go. Direct delivery takes priority over
default routing.

"Bill Grant" <not.available@online> wrote in message
news:%(E-Mail Removed)...
>
> Connecting a machine to two networks is like opening a can of worms. It's
> hard to see exactly what is what.
>
> The first thing to do is make sure that the two NICs are in different IP
> subnets. The next thing to do is ensure that only one NIC (the one
> connected to the Internet router) has a default gateway set. Internet
> traffic will always use that interface.
>
> The main problem is name resolution. If there are two IP addresses
> associated with the machine's name you will have odd problems if the name
> resolves to the "wrong" IP. People do not usually use IP addresses when
> they share files. They use machine names.
>
> If you can make sure that the machine name resolves to the "right" IP
> address the traffic will go through the "right" interface. For example if
> the packet is addressed to 192.168.12.12 and the machine has a
> 192.168.12.x interface, that is where it will go. Direct delivery takes
> priority over default routing.

Thanks Bill. Regarding the subnet, do you effectively mean that both of the
directly connected NICs should share a different first 3 numbers? I.e. if my
router and all existing clients are using 192.168.0.x, then I could set the
two directly connected NICs as follows:

Server 1GB NIC: 192.168.255.1
Subnet mask: 255.255.255.0

Desktop 1GB NIC: 192.168.255.2
Subnet mask: 255.255.255.0

Thanks

John

"John Whitworth" <sexyjw@g_EEEEEEEEEEEEEEEEE_mail.com> wrote in message
news:484f941c$0$26076$(E-Mail Removed)...
>
> "Bill Grant" <not.available@online> wrote in message
> news:%(E-Mail Removed)...
>>
>> Connecting a machine to two networks is like opening a can of worms.
>> It's hard to see exactly what is what.
>>
>> The first thing to do is make sure that the two NICs are in different
>> IP subnets. The next thing to do is ensure that only one NIC (the one
>> connected to the Internet router) has a default gateway set. Internet
>> traffic will always use that interface.
>>
>> The main problem is name resolution. If there are two IP addresses
>> associated with the machine's name you will have odd problems if the name
>> resolves to the "wrong" IP. People do not usually use IP addresses when
>> they share files. They use machine names.
>>
>> If you can make sure that the machine name resolves to the "right" IP
>> address the traffic will go through the "right" interface. For example if
>> the packet is addressed to 192.168.12.12 and the machine has a
>> 192.168.12.x interface, that is where it will go. Direct delivery takes
>> priority over default routing.
>
> Thanks Bill. Regarding the subnet, do you effectively mean that both of
> the directly connected NICs should share a different first 3 numbers? I.e.
> if my router and all existing clients are using 192.168.0.x, then I could
> set the two directly connected NICs as follows:
>
> Server 1GB NIC: 192.168.255.1
> Subnet mask: 255.255.255.0
>
> Desktop 1GB NIC: 192.168.255.2
> Subnet mask: 255.255.255.0
>
> Thanks
>
> John

Yes indeed. The second network should be in a different IP subnet.