Need help setting up direct connection between NAS and PC using 10gb ethernet cards ($5 paypal reward)

[littlemissdata]

Hi Everyone,

I'm so close to getting this done I just want to reward the person who can help. Please explain it to me like I'm 5.

I have 2 PCs and a 1gb ethernet router
[ TRUENAS PC 12.0-U5 ]
[ WORKSTATION Windows 10 Pro for Workstations]
they are both connected to the ethernet router and everything works great when i visit \\192.168.0.216 in WIndows Explorer I can access my TrueNas from Windows 10.

I installed this Intel 10Gb SFP NIC Network Card (X520-10G-1S-X8) on each PC and the right cable, this 10G SFP+ fiber optic cable connecting the two.

I plugged the 10Gb SFP+ cable and connected the 2 PCs directly. What on earth do I do to set it up so I can have a high speed 10Gb connection between those two PCs. Please someone explain it to me like I'm 5. I can post screenshots if needed.

 

[NugentS]

How about a network diagram please, including IP addresses.
The direct connection will need to be on its own subnet and you may need to edit the hosts file on the PC & TrueNAS so it knows where to go]

But the first step is to get the cabling and IP addressing correct

 

[littlemissdata]

My router for the 1Gb ethernet has IP addresses starting with 192.168.0.1 it works.

But the 10Gb direct connection does not.

Here's the Truenas screenshot. currently i set a 10.0.10.2/16 static IP for the 10Gb connection. I don't know why. I was just trying out things from tutorials i saw.

And on my Windows 10 PC that is directly connected via 10Gb SFP+ optic cable I don't know what to set the IPv4 address to.

Thank you so much for anyone that can help.

 

[littlemissdata]

Sorry Please ignore the 192.168.0.216 Static IP for the PC, (they do NOT have the same IP) I accidentally left that in there by mistake.

 

[Patrick M. Hausen]

You need to set both the NAS and the PC manually to an address that is not part of 192.168.0.0/24.

If you want to leave your NAS at 10.0.10.2/16 then pick any address that starts with 10.0 for your PC. E.g. 10.0.10.1.
Make sure the prefix length is /16, too - or if that dialog wants a subnet mask, use 255.255.0.0.
Also don't set a gateway or a DNS server for this interface.

That's all.

 

[NugentS]

As the above
I would set the second NIC as follows:
PC: 10.0.10.2/24 (255.255.255.0)
NAS: 10.0.10.1/24 (255.255.255.0)
As Patrick says: No Gateway or DNS

Then ping from the PC the IP address of the NAS 10.0.10.1
If you get a response then the hardware is correct
If no response then reverse one side of the fibre cables and try again (this may required minor surgery on the end)

At that point the Win10 PC should be able to access the NAS on \\10.0.10.1\share_name
Then try \\NAS_Name\share_name which may or may not work. This can be fixed by editing (its just a text file) the c:\windows\system32\drivers\etc\hosts file and putting an entry in that points the NAS_Name to the 10.0.10.1 address. This is a protected file so you have to do more than open in notepad. You may or may not care about this

 

[littlemissdata]

It works I'm so happy thank you both so much. Please private message me an email I can paypal $5 bucks to, both of you. It's worth it. I needed this done so badly so I can start moving away from Drive Bender and Drive Pool. I'm getting 500-900/MB/s speeds now through that fiber cable.

 

[NugentS]

Don't worry about it - you are welcome - just glad to be able to help

 

[Patrick M. Hausen]

Same. Please donate to a charity of your choice instead.