Setting up a second ethernet card dedicated to one target

As I said, please be patient, I don't know anything about this subject. What's obvious to you and missing may not be obvious to me.
I've looked up Network Routing Table and managed to get my computer to show me the connections but I can't see a way of attaching a file or picture to this post.
Is there any way of doing that?

Use Dropbox or similar.

Dafydd.

Ok, thanks for that, here's a link to the Route Table... I hope it means more to you than to me.

http://puu.sh/9hVvD/29188d4f73.png

I have no idea how the Mach3 CNC Windows program routes the messages through the ESS_v10r2d1b.dll plugin that it uses. Anyway, that's the software I'm trying to bully into working.

Bear in mind that I know nothing about this..... but...
I'm suspicious of lines like 224.0.0.0 240.0.0.0 on-link 10.9.9.8 because to my ignorant eye they seem to link traffic between those addresses. I would have not expected to see any cross connection between anything other than those starting 10
That's just using logic without any understanding of networking principles.

I'm not convinced because if you look at this Wireshark capture of the second LAN.....

http://puu.sh/9hZ5s/2413f408fc.png

there's traffic on that when there should be nothing. I'm not running the Mach3 software and the computer EMMA-PC isn't even plugged in. Why is it trying to reach that computer on the static ip addressed one?

What does this line in the Route table mean?

224.0.0.0 240.0.0.0 on-link 10.9.9.8

to me that's saying anything on 224 to 240 can try 10.9.9.8 if it can't b reached by an entry before it in the table?
EMMA-PC is never going to be found by earlier entries because it's unreachable. Should I be removing that line from the table? How about the line...

255.255.255.255 255.255.255.255 on-link 10.9.9.8

does that mean that anything can use 10.9.9.8 if it's not able to connect with any of the previous links in the table?

I've never seen a routing table before, I've just read this.... http://en.wikipedia.org/wiki/Routing_table
and that's my understanding of what it's saying but I may be completely wrong.

In this case, while checking the table is a good idea, your setup should just work. But your wireshark use means we would have a lot more to figure out over a traceroute command and result.
Bob

Ok here's the Wireshark output of the second ethernet card.

http://puu.sh/9i2iL/7a14331850.png

You can see that Dropbox and messages to EMMA-PC are in there. I need to make sure that if those can't find their destination, they don't try to use 10.9.9.8

That's why I thought those Route table entries I mentioned were doing that. What does this entry...

255.255.255.255 255.255.255.255 10.9.9.8 do? Doesn't that route anything that's failed to find its destination further up the table to 10.9.9.8? If that's the case, I surely need to delete that line?

I don't think I can help. I would have done the traceroute but since you need this to work, maybe the company that does your support can step in.
Bob

Thanks for trying to help Bob, it's much appreciated. I do all my own IT since I work for myself from home. This is an odd situation that's completely outside the normal things I have to sort out. I think I'll get bold, do a little more reading and then chop those entries out of the table. They just look wrong to me.
From the very little I've read, any message starts at the top of that table and tries the first route listed. If it fails, it goes on down the table.
If that's how it works, I need to delete the entries that tell it to connect to 10.9.9.8 because nothing should ever try to do that. When 10.9.9.8 tries to contact 10.9.9.9 it will always succeed at the first definition of that in the table because the SmoothStepper is always connected to that LAN card.

Maybe someone can confirm my logic or tell me how it really works?

One of my little tools last year on my bench was a device on the second ethernet port and I did add the route to nail it down. However here I can't seem to get a clean traceroute output to the target to see if there is a route issue.

Wireshark is great stuff but why the aversion to my one request?
Bob

Sorry Bob, was that referring to TRACEROUTE?
It was a deviation from my train of thought and it didn't answer the key question that I asked in that post about that particular line in the Route file I highlighted. That's why I glossed over it because I was still grappling with what the route table entries mean and how it works. I think that's pivotal to me understanding what the problem is.
I'll take a look at TRACEROUTE tomorrow when I'm not so tired.
I appreciate your help.

Working on Android app to auto-magically connect to a device on the network without the user revealing or being asked what IP it is. Fun fun fun oh there's a squirrel.

I don't want to share the possible route add command or commands until I get that trace.
Bob

Renewed energy after a good nights sleep so it's time to try to make sense of this problem again.
Three questions....
1. I've found traceroute and some information about it on the internet. It tells me to enter tracert domain.com where domain.com is where I want to trace to.

ok, now I'm really confused. The SmoothStepper has an ip address of 10.9.9.9 not a domain name. I tried typing tracert 10.9.9.9 and it returned the following...

Tracing route to 10.9.9.9 over a maximum of 30 hops.
1 <1 ms <1 ms <1 ms 10.9.9.9
Trace complete.

Presumably that means it found it? I have no idea.

2. I know that I can occasionally reach 10.9.9.9 What I was asking was how to stop any other traffic from trying to use the second LAN at 10.9.9.8

3. I could really use a definitive answer as to what the following lines in the Route Table do...
224.0.0.0 240.0.0.0 On-link 10.9.9.8
255.255.255.255 255.255.255.255 On-link 10.9.9.8
Do these mean that anything that isn't routed further up the table will attempt to use 10.9.9.8?
This is a key question because I know for certain that EMMA-PC does not exist on the network at the moment so it won't be found. Does that last line guarantee that if will try to find EMMA-PC on 10.9.9.8? That's the question I'd really like answered.

By repeatedly trying to connect, I eventually managed to get the SmoothStepper card to link up with the Mach3 windows program.
While this was running I took a look at Wireshark and the traffic was 99% dominated by packets 10.9.9.9 and 10.9.9.8. It was clear that it was happily chatting to the card, with the odd packet for orphand network computers thrown in.

I closed the program and tried to reconnect and it wouldn't. I opened up Wireshark and kept trying to connect it. Here is the output....

http://puu.sh/9iIwE/c9b25c1965.png

You'll notice that after each attempt to connect, there's a line such as this...

fe80::f9a7:2827:9daff02::c SSDP 208 M-SEARCH * HTTP/1.1

sometimes there's a similar line before it like...
fe80::f9a7:2827:9daff02::1:2 DHCPv6 150 Solicit XID: 0xcf1ef7 CID: 0001000115177130bcaec5bd260b

It would appear that this is what's stopping it connecting.
Any ideas what that traffic might be or how to stop it reaching 10.9.9.8?

I've turned off everything in the Local Are Connection Properties except the line...
Internet Protocol Version 4 (TCP/IPv4)
This has stopped some of the traffic and I can now get the ESS to connect but only after a few failed attempts. It always fails at first and I keep retrying.
It never connects while I'm retrying, but if I stop trying and wait, sometimes it starts on its own. This only happens after the two lines 57 and 58 on the attached Wireshark output. I've tried this several times and it's always the same.
On the Wireshark output, you can see me repeatedly trying to connect fro line 39 to 55. Then there's finally something back from the ESS on 56 followed by the 'who has' line at 57 then the 'frame check sequence incorrect' error when it finally wakes up and all is well.

So is this an issue with the ESS or my computer?

http://puu.sh/9iQrF/9b04947193.jpg

In fact, if you look at the title of the thread, that's what it was precisely about.
Things change as discussion develops and the problem takes different twists and turns as things are discovered.
You're no more a mind reader than I am, I'm simply trying to find out why the Mach3 program won't talk to the SmoothStepper.
If that means that some elements of the discussion become irrelevant then so be it.

The target would ignore packets without it's IP address and you went on about how it seems to not work from time to time so I was looking to see if the route was good.

Sorry but I've been doing networks for far too long so I took this as it sounded. That the route to 10.x.x.x was somehow wrong.

It's not and now with that out of the way, look at your default gateway entries.
Bob

I'm sorry it's been frustrating, I did say it was a strange request, that I didn't know much about it and that patience would be required!
I'm sure it's frustrating when you know what you're talking about, I'm pulling my hair out because this is supposed to be something that everyone just plugs in and it works! Yeah right...
Leaving me to get a default gateway right is like asking me to split the atom. I don't really know what a gateway is or what's required of it. hopefully all of the information I've posted will mean something to you. Some of it makes sense to me. Wireshark has taught be a lot of what's going on and it's a revelation. I've managed to massively reduce the traffic on the second LAN by turning off everything except the Internet Protocol Version 4 but it still tries to connect Dropbox and EMMA-PC which I'd rather it didn't.
Even when it finally connects, it's still not right. I tried moving on with the Mach3 installation which then goes on to update the FPGA on the Smoothstepper target and that hangs at 50% so something is still stopping it.
I really appreciate your help, just bear in mind I'm only following what little I know in an attempt to throw up information that might help resolve the problem.

Someone in the Warp9 Forum suggested that I reset the TCP-IP settings using the following...
1) Set a system restore point
2) Right click on the Command Prompt utility and run as administrator
3) Enter the following at the prompt and hit enter... netsh int ip reset resettcpip.txt
4) Restart the computer.

Bingo! This all works now.

I'd still be interested to know how to stop Dropbox and EMMA-PC orphan traffic from reaching 10.9.9.8 adaptor. In fact the only thing that should be able to reach that adaptor is then 10.9.9.9 Smoothstepper board.

Perhaps you can tell me how to do that?
Many thanks,
Roger