These are sw and version involved:
I've tried any kind of wifi connection between laptop and xdj-aero, access point or wlan client, with or without dhcp client, trusted all ip network zone range, disabled firewall or enabled with these executable as full trusted:
edb_streamd.exe
psvnfsd.exe
psvlinksysmgr.exe
rekordbox.exe
but I've obtained always the same behaviour:
I lauch rekordbox, wait for "Link" button showed up, then click on "Link" and xdj aero is showed centered in the same bar, so
I try to load a track with drag&drop a track either on deck 1 or 2 but nothing happen... xdj-aero seems to be not connected
At the same I've seen the log where the application write:
MainComponent::timerFuncMntMonitor WA mount not complete
5 to 10 times a second, since I push "Link" button and if I stop re-pushing the button the application stop to write this message.
Another message in the log PSvLinkAPILog say it:
InnerLinkAPI::dragDropPlayMusic NG mnt not complete
What these messages means?
Any ideas to solve?
Thanks.
Publicação fechada para comentários.
My recommendation would be for you to first change the settings on the AERO to disable any security and change the SSID name to something new. Connect your computer to that network and ensure that your firewall is DISABLED COMPLETELY. Try again and tell us if you still have issues.
Thank Pulse for your answer and support.
You're right... the firewall should be turned off completely, not only disabled for a while (this is an option for several software and antivirus).
The problem is solved!
...but I would like to investigate which port or protocol is blocked, more than those documented, and how to configure as well the firewall.
Plus I double checked all tests that I've done before and all connections works as access point and also as wlan client mode.
In wlan client mode there is a problem only If I choose to not use dhcp client of xdj-aero, but this is another issue, another question, another post...
Thanks again,
I'm not sure why it wouldn't work if you had allowed all the proper connections -- perhaps it wasn't using the right protocol (TCP instead of UDP)?