Peer to Peer 10Gbe Windows to FreeNAS 11.1 U5

Status
Not open for further replies.

ryanakata

Explorer
Joined
Jul 26, 2015
Messages
63
Hi,

I've read the 10gbe networking primer and didn't see my issue in that thread.

What I have is a Windows 10 PC currently working with a 192.168.1.1/24 network.

I purchased 2 Mellanox cards and a DAC cable that was used here. https://blog.sherwinm.com/2018/02/06/10gb-network-between-windows-10-and-freenas/

I slotted both cards and they come up in both systems.

In Windows I assigned 192.168.1.100 and in FreeNAS I've assigned 192.168.100.2. FreeNAS configuration is below.

Code:
mlxen0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
		options=ed07bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWFILTER,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
		ether 00:02:c9:51:15:22
		hwaddr 00:02:c9:51:15:22
		inet 192.168.100.2 netmask 0xffffff00 broadcast 192.168.100.255
		nd6 options=9<PERFORMNUD,IFDISABLED>
		media: Ethernet autoselect (10Gbase-SR <full-duplex,rxpause,txpause>)
		status: active


FreeNAS Network Summary Tab:
Code:
Name IPv4 Address IPv6 Address
igb0 192.168.1.250/24
mlxen0 192.168.100.2/24
Nameserver
8.8.8.8
8.8.4.4
Default route
192.168.1.1


FreeNAS can not ping my Windows machine and my Windows machine can not ping the FreeNAS box on that subnet. I've restarted both with no luck and I'm not sure what to try next.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
You won't get far if the machines are on different subnets. The 10GbE network needs to be a separate subnet and both devices must have IPs in that subnet, on the correct interfaces, in addition to the regular network.
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
In Windows I assigned 192.168.1.100 and in FreeNAS I've assigned 192.168.100.2. .
You did that wrong. You need to check out the directions again.
Still don't get it, post back.


Sent from my SAMSUNG-SGH-I537 using Tapatalk
 

kdragon75

Wizard
Joined
Aug 7, 2016
Messages
2,457
This may help if your more visual. Justy made it for another user doing the same thing for two PCs. Just ignore on of the PCs.
simple.JPG

If you don't see an IP labeled, just leave it the way it was before you changed it ;). to access FreeNAS on the 10gbe use the corponding 10gb interface IP.
 

ryanakata

Explorer
Joined
Jul 26, 2015
Messages
63
You did that wrong. You need to check out the directions again.
Still don't get it, post back.


Sent from my SAMSUNG-SGH-I537 using Tapatalk

I see my typo and I do apologize! Quite embarrassing for a Senior ISP engineer.

The Windows machine is 192.168.100.100
 

ryanakata

Explorer
Joined
Jul 26, 2015
Messages
63
Update: SOLVED by checking bind to both interfaces in SMB settings.
 

kdragon75

Wizard
Joined
Aug 7, 2016
Messages
2,457
I see my typo and I do apologize! Quite embarrassing for a Senior ISP engineer.

The Windows machine is 192.168.100.100
It happens. Thanks for the update!
 

pjr_atl

Dabbler
Joined
Jan 4, 2013
Messages
24
I am experiencing the same issue. just added a peer to peer 10GE connectionon a seperate subnet (192.168.111.1 and 192.168.111.2 I tried the fix suggested above binding SMB to IPs - no joy.

Windows reports the following -

Windows can't communicate with the device or resource (192.168.111.1)
It is available but is not responding to connection attempts. A firewall or network security policy on the remote computer might be blocking the connection on port "file and print sharing resource".
Make sure that the device or resource (192.168.111.1) allows incoming connections for File and Printer Sharing

it also reports ending and receiving packets on the link


I am running 11.2 Beta 2
 

kdragon75

Wizard
Joined
Aug 7, 2016
Messages
2,457
I am experiencing the same issue. just added a peer to peer 10GE connectionon a separate subnet (192.168.111.1 and 192.168.111.2 I tried the fix suggested above binding SMB to IPs - no joy.

Windows reports the following -

Windows can't communicate with the device or resource (192.168.111.1)
It is available but is not responding to connection attempts. A firewall or network security policy on the remote computer might be blocking the connection on port "file and print sharing resource".
Make sure that the device or resource (192.168.111.1) allows incoming connections for File and Printer Sharing

it also reports ending and receiving packets on the link


I am running 11.2 Beta 2
Please start a new thread with all of the required information and we will assist you there.
 
Status
Not open for further replies.
Top