Unidentified Network: Two Computers on LAN connection

[PhoenicianWarrior]

I am using the Wiwynn SV7210, a 2 node Open Compute Project setup. The 2 node OCP was supposed to only support Linux based OS, although I managed to install Win7 Pro 64bit on the computers. The Wiwynn tech support said that they do not support windows drivers, although the ethernet driver is installed and up to date when i select update driver on the device manager. I do not know what the issue is, I tried multiple troubleshoots all to no avail. Also, i do not plan on connecting to the internet at all, I just need the two computers to communicate with each other.

I followed this site exactly but still no solution: http://www.deskdecode.com/how-to-setup-two-computers-via-lan-in-windows-7-for-sharing/

Things to note: I currently have one gpu and one monitor, so I change network settings on one computer then turn it off (tried leaving it on as well on second attempt) and swap gpu and monitor over to other computer to do the same.

 

[Ralston18]

Does the following link match your platform?

http://www.h3platform.com/download/Datasheet_SV7210.pdf

Look into setting up an "ad hoc" connection between the two computers.

That said I am wondering about the "non support" for windows drivers. Even though you managed to install the drivers does not necessarily mean that all will really work.

Plus moving the GPU back and forth could be introducing other factors that cause communications to fail. (Seems there are no built in video ports.... Can you get another GPU?)

So not able to provide a direct solution per se or even really comment on the viability at all.

However take a look at "ad hoc" - may be worth a shot.

 

[PhoenicianWarrior]

Does the following link match your platform?

http://www.h3platform.com/download/Datasheet_SV7210.pdf

Look into setting up an "ad hoc" connection between the two computers.

That said I am wondering about the "non support" for windows drivers. Even though you managed to install the drivers does not necessarily mean that all will really work.

Plus moving the GPU back and forth could be introducing other factors that cause communications to fail. (Seems there are no built in video ports.... Can you get another GPU?)

So not able to provide a direct solution per se or even really comment on the viability at all.

However take a look at "ad hoc" - may be worth a shot.

Yes that is the correct model.

Do drivers really make that much of an impact? I have also noticed that the internet speed on that computer is substantially slower than all the other computers on the network.

I will be looking into ad hoc, and for the GPU I will have one soon to do further tests.

 

[Ralston18]

Yes: drivers can make a significant impact. Especially if the problem is some subtle conflict that only occurs in certain situations such as a particular app being run directly or in the background. And any related configuration settings may likewise affect performance.

In addition, there could be some network configuration issue or problem. Everything works okay and then some threshold is hit and problems occur. The "threshold" could be on the slower computer itself or some functionality within the overall network that creates a bottleneck slowing things down.

Compare the network adapter settings between a "fast" computer and the "slow" computer.

Key is that you establish a baseline for comparison purposes and then change only one thing at a time. Watch the results carefully and remember that some changes may not immediately implement themselves. Use performance monitors and logs to see what, if anything, changes or happens.

 

[PhoenicianWarrior]

Yes: drivers can make a significant impact. Especially if the problem is some subtle conflict that only occurs in certain situations such as a particular app being run directly or in the background. And any related configuration settings may likewise affect performance.

In addition, there could be some network configuration issue or problem. Everything works okay and then some threshold is hit and problems occur. The "threshold" could be on the slower computer itself or some functionality within the overall network that creates a bottleneck slowing things down.

Compare the network adapter settings between a "fast" computer and the "slow" computer.

Key is that you establish a baseline for comparison purposes and then change only one thing at a time. Watch the results carefully and remember that some changes may not immediately implement themselves. Use performance monitors and logs to see what, if anything, changes or happens.

The computers are connected now, the issue was simply due to network configurations with the ethernet switch.