Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Krazykanuck]

I have recently switched over to MC13 and ran into a little problem when searching for library servers.
For some reason it will not find the local server I have running on my home network.
It took me awhile to figure out what was happening because it would find a server but then not connect.
After looking through the log it appears to be trying to connect to a server at 192.168.56.1:6080, 6080 is the port I run the server on.
It appears that it is finding my server because it has the right port but my internal network is 192.168.2 not .56.
If I specify the server everything is fine.

[Matt]

I'm not able to reproduce this on our LAN.  The search finds the server and connects.

Are there multiple servers on the network so that it will want to show a dialog to let you choose?

[Krazykanuck]

I only have one server running.

My internal network is 192.168.2.xx
My server is running on 192.168.2.75:6080
When I try to search in the log I see it attempting to connect to 192.168.56.1:6080

The fact that is trying to connect to port 6080 seems to indicate that it found my server since it is using the correct port.
In the client I see the attempting to find and then the connecting to messages so I think it is finding the server and then it fails
I just don't understand where 192.168.56.1 is coming from. It is not a valid on my network.

As I was writing this I had an idea so I changed the port to 7080 on the server.
When I tried to search it tried to connect to 192.168.56.1:7080 so I think it is finding the server.

If I start up the version 12 server and attempt to search with a version 12 client everything works fine.

I can specify 192.168.2.75:6080 and everything connect and works fine.

[RhinoBanga]

More than one NIC (physical/virtual) on your server?

What does "ipconfig/all" show on the server?

What does "nslookup <server name>" show on both the client and server machines?   What does "nslookup <server ip address>" show on both machines?

[Krazykanuck]

I have virtualbox installed on the same box for some testing.
ipconfig shows that that is where the 192.168.56.1 address is coming from.

I am confused as to why if my server was found at the right address that when it tried to connect it switched to this address.
Also why does V12 not act the same way.

Thanks

[RhinoBanga]

I have virtualbox installed on the same box for some testing.

To clarify are you saying your server box has two NIC's or the client?


If it's the server then maybe MC is sending the response via the 2nd (virtual) NIC instead of the one it's actually listening on?   Or maybe the reply packet sent to the client just contains the address of the fist NIC on your server, which in this case is the virtualbox one.

Either way it should be something simple for JR to fix.

[Krazykanuck]

My server box has one physical NIC and the virtual NIC that vitualbox installed.

From the client it is finding the server on the physical link but trying to connect to the virtual link which of course it can't.
The only way the client can know about the virtual NIC is if the server provides the address.

Thanks

[foraye]

Have you considered checking the NIC priority settings?

Control Panel> Network Settings>Advanced>Advanced Settings

Make sure that your Local Lan has priority over the Virtual Box NIC etc.

Good Luck!

[Krazykanuck]

foraye

I checked and the virtual NIC was top priority.
I moved it down and now it works fine.
Thanks for the tip.

I admit I'm no networking guru but why does this matter?
Should the correct address not be part of the response packet?

Thanks again.

[foraye]

Happy to hear that it worked. I had a similar dual nic problem with a piece of equipment a few months back. I think some apps automatically grabs channel 1 and won't share it. You may have to re-check your settings upon re-booting.