Routing nightmare

Hi guys,

This is my setup at home:

Various clients running XP Pro or MCE2005 in domain mode.
Server running Small Business 2003
Admin client (My PC) running MCE2005
Linksys Router (wired, wifi, internet) & Access points

Currently my PC accesses the server via the router as do the rest of the
clients.
The router is the active DHCP server, the SB2003 server is the primary DNS
server.
My PC and the server both have 2 NICs and i want to use a crossover to
connect my PC directly to the server to get a 1Gb connection (i shovel a lot
of video data to & fro) but still leave the rest of the network as-is. Ie
internet and access to other clients via the router but any connection to
the server via the direct connection.

I'm assusming that i need to put both 2nd NICs on a different subnet and
fiddle with the ROUTE command on the SB server and my PC.

Can someone enlighten me?

Cheers!

In news:Qwy2g.6640$(E-Mail Removed),
Gremlin <(E-Mail Removed)> stated, which I commented on below:
> Hi guys,
>
> This is my setup at home:
>
> Various clients running XP Pro or MCE2005 in domain mode.
> Server running Small Business 2003
> Admin client (My PC) running MCE2005
> Linksys Router (wired, wifi, internet) & Access points
>
> Currently my PC accesses the server via the router as do the rest of
> the clients.
> The router is the active DHCP server, the SB2003 server is the
> primary DNS server.
> My PC and the server both have 2 NICs and i want to use a crossover to
> connect my PC directly to the server to get a 1Gb connection (i
> shovel a lot of video data to & fro) but still leave the rest of the
> network as-is. Ie internet and access to other clients via the router
> but any connection to the server via the direct connection.
>
> I'm assusming that i need to put both 2nd NICs on a different subnet
> and fiddle with the ROUTE command on the SB server and my PC.
>
> Can someone enlighten me?
>
> Cheers!

Easiest way is to acquire a gigabit capable switch with multiple gigabit
ports. If all the NICs are gigabit NICs, and they are set to autodetect,
they'll configure themselves at the fastest possible speed. This way they'll
communicate at 1 gig, as well as all other machines that are capable as well
as others that are not.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.

It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only thing in life is change. Anything more is a blackhole consuming
unnecessary energy. - [Me]

But note that the machines won't automatically use this connection to
transfer data just because it exists. File sharing uses computer names, not
IP addresses. If the machine's name resolves to the IP of the existing NIC,
that's the one that will be used. Nothing will go over the gigabit subnet.

Ace Fekay [MVP] wrote:
> In news:Qwy2g.6640$(E-Mail Removed),
> Gremlin <(E-Mail Removed)> stated, which I commented on
> below:
>> Hi guys,
>>
>> This is my setup at home:
>>
>> Various clients running XP Pro or MCE2005 in domain mode.
>> Server running Small Business 2003
>> Admin client (My PC) running MCE2005
>> Linksys Router (wired, wifi, internet) & Access points
>>
>> Currently my PC accesses the server via the router as do the rest of
>> the clients.
>> The router is the active DHCP server, the SB2003 server is the
>> primary DNS server.
>> My PC and the server both have 2 NICs and i want to use a crossover
>> to connect my PC directly to the server to get a 1Gb connection (i
>> shovel a lot of video data to & fro) but still leave the rest of the
>> network as-is. Ie internet and access to other clients via the router
>> but any connection to the server via the direct connection.
>>
>> I'm assusming that i need to put both 2nd NICs on a different subnet
>> and fiddle with the ROUTE command on the SB server and my PC.
>>
>> Can someone enlighten me?
>>
>> Cheers!
>
> Easiest way is to acquire a gigabit capable switch with multiple
> gigabit ports. If all the NICs are gigabit NICs, and they are set to
> autodetect, they'll configure themselves at the fastest possible
> speed. This way they'll communicate at 1 gig, as well as all other
> machines that are capable as well as others that are not.

"Ace Fekay [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In news:Qwy2g.6640$(E-Mail Removed),
> Gremlin <(E-Mail Removed)> stated, which I commented on
> below:
>> Hi guys,
>>
>> This is my setup at home:
>>
>> Various clients running XP Pro or MCE2005 in domain mode.
>> Server running Small Business 2003
>> Admin client (My PC) running MCE2005
>> Linksys Router (wired, wifi, internet) & Access points
>>
>> Currently my PC accesses the server via the router as do the rest of
>> the clients.
>> The router is the active DHCP server, the SB2003 server is the
>> primary DNS server.
>> My PC and the server both have 2 NICs and i want to use a crossover to
>> connect my PC directly to the server to get a 1Gb connection (i
>> shovel a lot of video data to & fro) but still leave the rest of the
>> network as-is. Ie internet and access to other clients via the router
>> but any connection to the server via the direct connection.
>>
>> I'm assusming that i need to put both 2nd NICs on a different subnet
>> and fiddle with the ROUTE command on the SB server and my PC.
>>
>> Can someone enlighten me?
>>
>> Cheers!
>
> Easiest way is to acquire a gigabit capable switch with multiple gigabit
> ports. If all the NICs are gigabit NICs, and they are set to autodetect,
> they'll configure themselves at the fastest possible speed. This way
> they'll communicate at 1 gig, as well as all other machines that are
> capable as well as others that are not.
>
Ah but i only need one fast connection hence the (cheap!) crossover cable
direct to to the server. Most of the clients around the house are wireless
anyway. Besides, i thought someone here would appreciate the challenge. ;-)

Cheers,
Glenn

In news:3DP2g.3380$(E-Mail Removed),
Gremlin <(E-Mail Removed)> stated, which I commented on below:

> Ah but i only need one fast connection hence the (cheap!) crossover
> cable direct to to the server. Most of the clients around the house
> are wireless anyway. Besides, i thought someone here would appreciate
> the challenge. ;-)
> Cheers,
> Glenn

I was trying to offer a way to hook them all up. :-)

In news:OBqC%(E-Mail Removed),
Bill Grant <not.available@online> stated, which I commented on below:
> But note that the machines won't automatically use this connection
> to transfer data just because it exists. File sharing uses computer
> names, not IP addresses. If the machine's name resolves to the IP of
> the existing NIC, that's the one that will be used. Nothing will go
> over the gigabit subnet.

File sharing can use NetBIOS names, DNS FQDN or IP addresses in a UNC.
Network Neighborhood (or My Network PLaces, whatebver you want to call it),
uses NetBIOS names. So Bill, I'm not sure what you're saying here. If the
machine only has one connection (one NIC), it will use that to communicate
no matter what protocol it uses to commincate.

Maybe I'm misunderstanding what you're saying. Can you elaborate?

Ace Fekay [MVP] wrote:
> In news:OBqC%(E-Mail Removed),
> Bill Grant <not.available@online> stated, which I commented on below:
>> But note that the machines won't automatically use this connection
>> to transfer data just because it exists. File sharing uses computer
>> names, not IP addresses. If the machine's name resolves to the IP of
>> the existing NIC, that's the one that will be used. Nothing will go
>> over the gigabit subnet.
>
> File sharing can use NetBIOS names, DNS FQDN or IP addresses in a UNC.
> Network Neighborhood (or My Network PLaces, whatebver you want to
> call it), uses NetBIOS names. So Bill, I'm not sure what you're
> saying here. If the machine only has one connection (one NIC), it
> will use that to communicate no matter what protocol it uses to
> commincate.
> Maybe I'm misunderstanding what you're saying. Can you elaborate?

What I was saying is that simply adding a second NIC to the two machines
to increase the throughput between them will just work automatically.
Gremlin was talking about adding a second NIC to each machine. Did you see
the thread a few days ago where the OP installed gigabit NICs in his servers
to speed up backup? He was complaining that no traffic was using the second
NIC.

Traffic will only use the second NIC if the machine name resolves to its
IP address.

In news:3DP2g.3380$(E-Mail Removed),
Gremlin <(E-Mail Removed)> stated, which I commented on below:
> Ah but i only need one fast connection hence the (cheap!) crossover
> cable direct to to the server. Most of the clients around the house
> are wireless anyway. Besides, i thought someone here would appreciate
> the challenge. ;-)
> Cheers,
> Glenn

You know, after re-reading everything, you're right, a crossover will work
since each PC has two NICs. Yes, a separate subnet would be required. You
may get into a situation possibly getting duplicate name errors because each
NIC is registering it's name with their respective IPs. On the second NIC,
disable NetBIOS (IP Prop, Advanced, WINS tab to eliminate that issue,
disable "Register This Connection" (IP Prop, Adv, DNS tab), provide an IP
address, maybe such as 192.168.50.1 for the first, 192.168.50.2 for the
other and leave the gateway blank on both machines. The primary NIC will be
the one with the gate. In Network and Dialup settings, make sure the primary
NIC is at the top of the binding order. Connect between the two machines
using the 192.168.50.x address via a UNC. Remember only IP can be used
(unless you give it a different host name in DNS, but by IP is suggested.
This way that NIC will be used.

Cheers!

Ace

In news:OFgK2$$(E-Mail Removed),
Bill Grant <not.available@online> stated, which I commented on below:
> What I was saying is that simply adding a second NIC to the two
> machines to increase the throughput between them will just work
> automatically. Gremlin was talking about adding a second NIC to each
> machine. Did you see the thread a few days ago where the OP installed
> gigabit NICs in his servers to speed up backup? He was complaining
> that no traffic was using the second NIC.
>
> Traffic will only use the second NIC if the machine name resolves
> to its IP address.

Sorry for the misunderstanding. I forgot about the dual NICs for a moment. I
didn't see that other thread, but I can see why it was happening. See my
other response to Gremlin in this thread about the dual NICs, which I
elaborated on.

Cheers!

Ace

"Ace Fekay [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In news:3DP2g.3380$(E-Mail Removed),
> Gremlin <(E-Mail Removed)> stated, which I commented on
> below:
>> Ah but i only need one fast connection hence the (cheap!) crossover
>> cable direct to to the server. Most of the clients around the house
>> are wireless anyway. Besides, i thought someone here would appreciate
>> the challenge. ;-)
>> Cheers,
>> Glenn
>
> You know, after re-reading everything, you're right, a crossover will work
> since each PC has two NICs. Yes, a separate subnet would be required. You
> may get into a situation possibly getting duplicate name errors because
> each NIC is registering it's name with their respective IPs. On the second
> NIC, disable NetBIOS (IP Prop, Advanced, WINS tab to eliminate that issue,
> disable "Register This Connection" (IP Prop, Adv, DNS tab), provide an IP
> address, maybe such as 192.168.50.1 for the first, 192.168.50.2 for the
> other and leave the gateway blank on both machines. The primary NIC will
> be the one with the gate. In Network and Dialup settings, make sure the
> primary NIC is at the top of the binding order. Connect between the two
> machines using the 192.168.50.x address via a UNC. Remember only IP can be
> used (unless you give it a different host name in DNS, but by IP is
> suggested. This way that NIC will be used.
>

I did get it working pretty much like that so i could access shares using
the UNC. I didn't get as far as messing with the bindings etc. though.
I was thinking i might be able to achieve a cleaner solution by manually
editing the routing table on the server and my pc. ie all traffic bound for
the server would automatically go via the 2nd NIC and the same from the
server to my PC.

I'm sure i slept through the ROUTE command bits during network classes! :-)

Cheers,
Glenn