Forums › Forums › Avantis Forums › Avantis troubleshooting › Avantis + Dante V3 + DVS: Card not visible in DHCP mode
- This topic has 4 replies, 4 voices, and was last updated 1 month, 1 week ago by Klaus Haulrich.
-
AuthorPosts
-
2024/09/29 at 3:18 pm #126027Klaus HaulrichParticipant
I need help with Avantis + Dante V3 + Dante Virtual Soundcard.
Actually, I have two problems with this setup, but to keep things separated, I’ll make one post per problem.This problem is about using the A&H Dante V3 card in a proper network with DHCP assigned addresses.
I have reduced my setup to the simplest possible:
– A windows PC with Reaper, Dante Virtual Soundcard and Dante Controller
– Avantis (“duo”) with a 64×64 Dante V3 card in slot 2
– The PC is connected directly to the primary port on the Dante card. No switch in between and therefore no DHCP server on the “network”.
In this setup the Dante Controller finds the A&H Dante card as it should.
On the Avantis the card is listed as “Dante 64×64 V3 Version 2”.However, I would like the Dante card and my PC to sit on a proper network with DHCP assigned IP addresses and in the future with more Dante devices.
If the A&H Dante card is connected to a switch on my network, it becomes invisible to Dante Controller. My PC is connected to the same switch and it gets a proper IP address from my DHPC server.
I can see in the DHCP server status that the Dante card requests an IP and it gets a proper one that fits in the network.
On the Avantis the card is listed as “Dante 64×64 V3 Version Unknown”. See screenshot #1.Do you know what’s going on here?
As mentioned in my other post, I am struggling a lot with this Dante setup.
My Dante card was previously on firmware 1.0.1 and back then it was actually visible in Dante Controller with a DHCP assigned IP address next to my Dante Virtual Soundcard with the DHCP assigned address from my Windows PC.
Because I am struggling to solve the issue on my other post, I chose to upgrade the firmware. It went smoothless but now I have this issue.There is no firmware 1.0.1 on the Allen & Heath website, so I can’t downgrade to that again.
Do you have any ideas how to fix this?
Attachments:
You must be logged in to view attached files.2024/09/29 at 4:27 pm #126030jyradelixParticipantDiscovery uses mDNS, so if your network is blocking multicast, that could cause it. Thought, that could block PTP/clock as well as it uses multicast too … Are you sure your card is getting an IP address from the DHCP server? Maybe check to set if the DHCP server shows a reservation.
I use DHCP on my network for my cards and machines, though I do tend to use DHCP reservations, just so I know what’s what.
2024/09/29 at 5:10 pm #126033ericdannewitzParticipantDoes everything have the same subnet? 255.255.255.0?
Windows PC not have a software Firewall enabled?
2024/09/30 at 1:18 pm #126049BrianParticipantThe Dante network and the built in network ports on the console are NOT on the same network unless you go into the Dante card settings and select the “Bridge Network Connection” option (I’m writing this off memory, so the exact name of the setting might be different). Alternatively, you can connect one of the Dante card network ports into one of the built in network ports on the console, but this is a “manual” way of doing the exact same thing that the Dante card “bridge” setting will do.
Personally I would work hard to keep the two networks separate. Usually by having two network ports on the computer you are using DVS on – one for Dante and one for the regular network. Keeping the Dante network separate from the regular network will create a more reliable Dante network.
2024/10/05 at 3:32 pm #126211Klaus HaulrichParticipantThanks for your suggestions.
I could see in the DHCP server, that an IP address was assigned to the Dante card, but still it wasn’t visible in Dante Controller.
I tried assigning a static IP address within the same subnet as the Windows PC and the DHCP server.
Then the Dante card becomes visible in Dante Controller.My takeaway is, that I’m affected by the known issue in Dante V3 firmware version 1.0.2.
“ID29 In certain circumstances with specific third-party hardware, card will crash when attempting to acquire a DHCP address requiring a reboot.”
I will proceed with a static IP address for now.
-
AuthorPosts
- You must be logged in to reply to this topic.