Problem with two computers, running XP Pro, having two network cards each
Charles Nadeau
It work beautifully except for one detail:
When I am at the "server" and copy something to the workstation it uses
the 1000Base-T card.
When doing the other way around, it takes the 100Base-T card.
Here is the current configuration for the "server":
Windows IP Configuration
Host Name . . . . . . . . . . . . : diskbox
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 T Desktop
Adapter
Physical Address. . . . . . . . . : 00-02-B3-99-51-52
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 210.252.128.8
143.90.130.58
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810X Family
PCI Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-07-95-1E-15-9D
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 210.252.128.8
143.90.130.58
And the one for the workstation:
Windows IP Configuration
Host Name . . . . . . . . . . . . : FUKUOKA
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
Ethernet Controller (3C905C-TX Compatible)
Physical Address. . . . . . . . . : 00-E0-81-20-D3-9E
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 210.252.128.8
143.90.130.58
Ethernet adapter Local Area Connection 4:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 T Server
Adapter #2
Physical Address. . . . . . . . . : 00-03-47-23-D6-30
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 210.252.128.8
143.90.130.58
On both computers the 1000base-T card is the first in the binding order.
I disabled the IP routing on both machines. What else can I do?
Thanks a lot for your help!!
Charles
Charles Nadeau
http://radio.weblogs.com/0111823/
Ron Lowe wrote:
>
> "Charles Nadeau" <cha...@elf.coara.or.jp> wrote in message news:3DDCD464...@elf.coara.or.jp...
> > Hello,
> >
> > I am having a problem with two computers having two network cards each
> > on my network.
> >
> > First a bit of background: On my LAN I have two computers I use mainly
> > for Non Linear video Editing (NLE): a workstation where I run my editing
> > program and a "server" in which I have a 550 GB RAID 5 array. They are
> > both connected to a switch through their 100Base-T network cards and
> > they both run Windows XP pro.
> >
> > This setup does not move fast enough the videos I am editing. Therefore
> > I added a 1000Base-T card to each of these two computers and connected
> > the 1000Base-T cards together with a Cat 5E cross-connect cable.
> >
> > The network address/netmask/gateway of these two computers are:
> > Workstation:
> > 100Base-T: 192.168.0.4/255.255.255.0/192.168.0.1
> > 1000Base-T: 10.10.10.1/255.255.255.248/10.10.10.0
> > "Server":
> > 100Base-T: 192.168.0.7/255.255.255.0/192.168.0.1
> > 1000Base-T 10.10.10.2/255.255.255.248/10.10.10.0
> >
> > What I want to do is to force the traffic between these two computers to
> > use the 1000Base-T link exclusively and keep all traffic going to the
> > Internet and the other computers on the network through the 100Base-T
> > cards and the switch (which is connected to a router).
> >
> > I modified the routing table on both machines (with IP routing enabled
> > on both machines).
> > On the workstation I entered:
> > route add 192.168.0.7 mask 255.255.255.255 10.10.10.2 metric 1
> > On the server I entered:
> > route add 192.168.0.4 mask 255.255.255.255 10.10.10.1 metric 1
> > This forced traffic between the two computers on the 1000Base-T link.
> > However after this modification the two computers couldn't find where
> > the DNS servers were. I therefore undid this modification to the routing
> > table since I could access neither the Internet nor my mail server.
> >
> > I then tried without doing any modifications to the routing table to
> > enable IP routing on both computers. The result was slightly better but
> > surfing the web was slower and Outlook couldn't find its mail server.
> >
> > The IP configuration of these two computers is:
> >
> > Workstation:
> >
> > Windows IP Configuration
> > Host Name . . . . . . . . . . . . : FUKUOKA
> > Primary Dns Suffix . . . . . . . :
> > Node Type . . . . . . . . . . . . : Unknown
> > IP Routing Enabled. . . . . . . . : Yes
> > WINS Proxy Enabled. . . . . . . . : No
> > Ethernet adapter Local Area Connection:
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
> > Ethernet Controller (3C905C-TX Compatible)
> > Physical Address. . . . . . . . . : 00-E0-81-20-D3-9E
> > Dhcp Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.0.4
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.0.1
> > DNS Servers . . . . . . . . . . . : 210.252.128.8
> > 143.90.130.58
> > Ethernet adapter Local Area Connection 4:
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Intel(R) PRO/1000 T Server
> > Adapter #2
> > Physical Address. . . . . . . . . : 00-03-47-23-D6-30
> > Dhcp Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 10.10.10.1
> > Subnet Mask . . . . . . . . . . . : 255.255.255.248
> > Default Gateway . . . . . . . . . : 10.10.10.0
> > DNS Servers . . . . . . . . . . . : 210.252.128.8
> > 143.90.130.58
> >
> > "Server":
> >
> > Windows IP Configuration
> > Host Name . . . . . . . . . . . . : diskbox
> > Primary Dns Suffix . . . . . . . :
> > Node Type . . . . . . . . . . . . : Unknown
> > IP Routing Enabled. . . . . . . . : Yes
> > WINS Proxy Enabled. . . . . . . . : No
> > Ethernet adapter Local Area Connection 2:
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Intel(R) PRO/1000 T Desktop
> > Adapter
> > Physical Address. . . . . . . . . : 00-02-B3-99-51-52
> > Dhcp Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 10.10.10.2
> > Subnet Mask . . . . . . . . . . . : 255.255.255.248
> > Default Gateway . . . . . . . . . : 10.10.10.0
> > DNS Servers . . . . . . . . . . . : 210.252.128.8
> > 143.90.130.58
> > Ethernet adapter Local Area Connection:
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Realtek RTL8139/810X Family
> > PCI Fast Ethernet NIC
> > Physical Address. . . . . . . . . : 00-07-95-1E-15-9D
> > Dhcp Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.0.2
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.0.1
> > DNS Servers . . . . . . . . . . . : 210.252.128.8
> > 143.90.130.58
> > I undid this change too.
> >
> > My question now is how should I modify the routing table to achieve the
> > goal I stated above? Is the routing table the only way to do it? Any
> > other parameter I should check/set?
> > Thanks for your collaboration!
> >
> > Charles Nadeau
> > http://radio.weblogs.com/0111823/
>
> First, I havn't tried this, but here's how I'd start:
>
> 1) Don't add any static routes.
> Leave the route tables alone.
>
> Set up the TCP/IP properties like this:
> 100Mbit : 192.168.0.x / 255.255.255.0 / 192.168.0.1
> 1000Mbit: 10.10.10.x / 255.255.255.0
>
> Notice I do not specify a Default Gateway on the 1000Mbit connection.
> This is really a 'per machine' setting, and each machine should be left
> pointing only to your router on 192.168.0.1
>
> This will set up the routes in a default configuration:
> Traffic for the 192.168.0.x subnet will go out the 100Mbit card;
> Traffic for the 10.10.10.x subnet will go out the 1000Mbit card;
> Traffic for all other subnets will go to the router.
>
> Test this configuration by pinging the other 1000Mbit machine:
> a) using it's 10.10.10.x IP address .. observe traffic on the 1000Mbit lan.
> b) using it's 192.168.0.x address ... observe traffic on the 100Mbit lan.
> Ping the default GW on 192.168.0.1;
> Ping another machine on 192.168.0.x.
>
>
> 2) Don't enable IP forwarding on either machines.
> We are not going to use them as routers.
>
> 3) There are now 2 routes between the 2 machines, on different subnets.
> The issue is now to ensure that file and print sharing choose the 1000Mbit connection first.
>
> Go to:
> Network Connections folder | Advanced menu | Advanced Settings...
>
> In the Adapters and Bindings tab, look at the 'Connections' box.
> Select the 1000Mbit connection, and then click the green up arrow to
> shift it to the top of the binding order.
>
> This should force Windows Networking to use the 1000Mbit connection first.
> So connections to the 'server' will be on the 1000Mbit connection.
> It should then fall back on the 100Mbit connection if it can't set up a session on the
> first-bound adapter. So connections to other PCs will still work.
>
> --
> Best Regards,
> Ron Lowe.
> MS-MVP - Windows Networking
Ron Lowe
> Ron,
>
> It work beautifully except for one detail:
> When I am at the "server" and copy something to the workstation it uses
> the 1000Base-T card.
> When doing the other way around, it takes the 100Base-T card.
>
> Here is the current configuration for the "server":
>
>
OK, so far so good.
The listing you made looks good.
I'm not sure why one machine is ignoring the binding order.
In old NT4 days, there used to be a registry entry called
IgnoreBindingOrder, but I don't think it applies any more.
What we can perhaps do is force name resolution to a specific IP address.
XP-XP uses 2 seperate methods for File+Print sharing:
DirectHosting of SMB over TCP/IP;
NetBIOS over TCP/IP.
Both are tried together, and the first one to answer wins.
The name resolution sequence under XP is to use DNS / Hosts resolution
first, before falling back on NetBIOS, so to be sure, we will force name resolution
both for DNS and NetBIOS.
Go to C:\windows\system32\drivers\etc.
There are 2 files we will edit:
- hosts,
- lmhosts.sam
First, hosts:
dbl-click 'hosts' | Select program from a list | choose Notepad.
There is 1 entry:
127.0.0.1 localhost
Add the following 2 lines:
10.10.10.3 fukuoka
10.10.10.2 diskbox
Be sure to have a 'return' at the end of the last line.
File | save, and close notepad.
Go to a command prompt and 'ping diskbox'.
Check it resolves to 10.10.10.2
Then 'ping fukuoka'
Check it resolves to 10.10.10.3
Do this on both machines.
Now, LMHOSTS.
First, re-name lmhosts.sam to lmhosts ( with no extension ).
(.sam is a SAMple file, and is not live )
dbl-click 'lmhosts' | Select program from a list | choose Notepad.
There are no actual entries in this file, just comments.
Scroll past all the comment lines.
Append the following:
10.10.10.3 fukuoka #PRE
10.10.10.2 diskbox #PRE
Be sure to have a 'return' at the end of the last line.
File | save, and close notepad.
In Network Connections folder, select either LAN connection, | properties;
TCP/IP | Properties | Advanced button | WINS tab;
Ensure LMHosts lookup is enabled( checked).
( I want to be sure that if name resolution falls through to netbios for whatever reason, the lmhosts file is read. )
Do not touch the Import button.
OK your way out.
Go to a command prompt, and issue the following commands:
nbtstat -R
( should reply with "Succesfull purge and reload of remote name table")
nbtstat -c
( should see 3 entries for each machine, with lifetime of "-1", meaning 'never expires' )
Do this on both machines.
Now, try mapping a network drive from the client to the server.
Charles Nadeau
I followed carefully your instructions and it lead to the same result:
It works from the "server" to the workstation but not the other way
around. Anything else I should check?
Thanks for your time and patience!
Charles Nadeau
http://radio.weblogs.com/0111823/
Charles Nadeau
Ron Lowe wrote:
>
> "Charles Nadeau" <cha...@elf.coara.or.jp> wrote in message news:3DDD769E...@elf.coara.or.jp...
> > Ron,
> >
> > It work beautifully except for one detail:
> > When I am at the "server" and copy something to the workstation it uses
> > the 1000Base-T card.
> > When doing the other way around, it takes the 100Base-T card.
> >
> > Here is the current configuration for the "server":
> >
> >
> <snippage>
>
> OK, so far so good.
> The listing you made looks good.
>
> I'm not sure why one machine is ignoring the binding order.
> In old NT4 days, there used to be a registry entry called
> IgnoreBindingOrder, but I don't think it applies any more.
Ron,
First, sorry for the late reply. I started an hectic business trip a
couple of days after I received this message and then I went on
Christmas holidays from which I just came back.
After a couple of reboot of the two machines, it finally works. I didn't
touch anything, just rebooted a couple of time.
Thanks a lot for your patience and advises.