Community


All times are UTC - 5 hours




Post new topic Reply to topic  [ 13 posts ]  Go to page Previous  1, 2
Author Message
 Post subject: Re: Changing IP to met server program requirements on NR free li
PostPosted: Thu May 16, 2019 12:47 am 
Offline

Joined: Thu May 16, 2019 12:43 am
Posts: 1
MaxBlitzer wrote:
maestro7676 wrote:

There are another 4 LAN cards on th PC server, connected to other devices using the same ip range (the server software on PC Servr manages that devices via LAN).

The problem is that then all the other devices attached on server LAN cards having the IP 192.168.200.xxx are not reachable by the server program (that now has 10.0.0.3 IP)


This sounds like incorrect network setup. You probably are mistaken about this, or this needs to be fixed as its just wrong.

When you have multiple network cards, you need to have each network card on a different subnet, so when the OS needs to send a packet, it knows WHICH card to use. If they are all on the same subnet, could be random, could think there is a loop, its *dunno, this is bad and shouldn't be done* etc.

So on each of your neorouter clients, your network interfaces should have one for your internet connection subnet, AS WELL as a neorouter interface ON A DIFFERENT SUBNET. You MUST have the neorouter IP PLUS an additional IP (the path to your internet connection) for any of this VPN stuff to work.

Put Neorouter DHCP range back to 10.0.0.x and the local LAN back to 192.168.200.x.

For the local clients that are physically connected to the PC server, they will talk to the PC server using the 192.168.200.x IP. Any/all neorouter computers can talk to the PC server using the neorouter assigned 10.x.x.x IP. For any computer that is both on the same 192.168.200.x and neorouter 10.x.x.x lan SHOULD be able to ping each other over either interface. If not, your computers are the issue, not neorouter. You'll need to provide all the IP's and interfaces (including routes) to figure this out.

Here's my setup:

Windows 10 PC (connected to switch):
local network connected to my router/internet connection: 192.168.2.20 (physical card)
local network connected to my 10G network: 192.168.222.20 (physical card)
neorouter virtual interface: 192.168.236.20

Windows XP PC (connected to switch):
local network connected to my router/internet connection: 192.168.2.30 (physical card)
neorouter virtual interface: 192.168.236.30

Work PC (in a different location):
local network connected to its router/internet connection: 192.168.0.40 (physical card)
neorouter virtual interface: 192.168.236.40

From either PC, they can ping each other. 192.168.2.20 pings 192.168.2.30 and vice versa, and 192.168.236.20 pings 192.168.236.30 and vice versa. Either the win10 or XP can ping my work PC at 192.168.236.40, but not 192.168.0.40. That will be 'destination unreachable'.

You cannot ping 192.168.200.x IP from a 10.x.x.x IP and vice versa (remember, both computers should have at least two different IP subnets, they don't replace each other).

When they ping each other over the physical 192.168.2.x interface, the pings are ALWAYS 1ms. When I ping them over the 192.168.236.x interface, the first 8-10 pings are kinda high (depending on server location and internet speed), but then as the p2p figures out they are on same lan, then pings go to 1ms.

Pinging 192.168.236.2 with 32 bytes of data:
Reply from 192.168.236.2: bytes=32 time=141ms TTL=128
Reply from 192.168.236.2: bytes=32 time=30ms TTL=128
Reply from 192.168.236.2: bytes=32 time=31ms TTL=128
Reply from 192.168.236.2: bytes=32 time=29ms TTL=128
Reply from 192.168.236.2: bytes=32 time=67ms TTL=128
Reply from 192.168.236.2: bytes=32 time=176ms TTL=128
Reply from 192.168.236.2: bytes=32 time<1ms TTL=128
Reply from 192.168.236.2: bytes=32 time<1ms TTL=128
Reply from 192.168.236.2: bytes=32 time<1ms TTL=128

But it might all just sort itself when you fix the 4 network cards on the same subnet. That's red alarm bells wrong. Neorouter likely isn't the issue, here, your network design is. Packets are getting dropped on the PC server for having messed up routing.

So to recap:
1) fix the 4 network cards on same subnet, that's wrong. Or its described incorrectly (ie, they are actually on different subnets).
2) Set neorouter DHCP range back to 10.x.x.x
3) Local, physical computers NOT using neorouter uses the 192.168.200.x IP for the PC server
4) the non-local, neorouter clients uses the 10.0.0.x IP for the PC server

The application on the PC server shouldn't need to change (unless you have to specify an IP to bind to, in which you have a showstopper problem right there and will need a different solution). You just need to change the new neorouter clients to use the 10.0.0.x IP.

If none of this makes sense to you, to further help you, you need to run "ipconfig /all" and "route print" on both your windows PCs. It sounds like your neorouter server is linux, but I don't think we need that info. (The linux box would be "ifconfig" and "route -n", and would be helpful but probably not needed).

You may also need to expand on the limitations of setting an IP in the PC servers application and in the PC clients application.


Thank you so much for taking time and explaining all steps, even absolute nub like me can figure it out now =D

_________________
Gaming with troubletank2.com & troubletank.org.uk


Top
 Profile  
 
 Post subject: Re: Changing IP to met server program requirements on NR free li
PostPosted: Fri May 24, 2019 3:50 am 
Offline

Joined: Thu May 23, 2019 2:05 am
Posts: 6
VPN is the best option here.


Top
 Profile  
 
 Post subject: Re: Changing IP to met server program requirements on NR free li
PostPosted: Tue May 28, 2019 4:51 am 
Offline

Joined: Tue May 28, 2019 4:42 am
Posts: 1
Location: New York
You can use VPN or change IP contacting your internet provider.

_________________
Play full version of World of Solitaire game.
Free version of Earn to Die Unblocked game.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 13 posts ]  Go to page Previous  1, 2

All times are UTC - 5 hours


Who is online

Users browsing this forum: No registered users and 4 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron