My iPad with the iOS remote app cannot consistently connect to the server. They both ate on the same network. Does the server pc has to be wirelessly connected for it work with ipad. As for now the pc has a wired connection to our netgear R7000 router as well as the ipad.

There's no static up whatsoever. Both iPads and easyworship PC are on the same network and all are DHCP

So you turn EW on, press the Remote button. At the bottom of that where it says "Easyworship Remote (PC Name)", make sure it says ON and not OFF. If it says Off, click the word and it will turn it On.
Then launch the app. Press the three lines top left, then the gear icon. Under Server should show your EW PC.

Are you able to get that far?

I did all that. I had connected once only for 1 minute. I am pretty sure it is not a networking issue. Take a look at both setup one is static ip and the other DHCP. let me know whether you see something out of ordinary. The ipads are the only devices that cant make a connection. I tried an iphone and there was conection

Microsoft Windows [Version 10.0.16299.309]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\rony>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : easyworship
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : bbc.church

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : bbc.church
Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-26-18-59-33-E7
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . : bbc.church
Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-26-18-59-39-09
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2dc4:cf48:667:cdcc%12(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.151(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, March 28, 2018 8:54:09 AM
Lease Expires . . . . . . . . . . : Thursday, April 5, 2018 8:54:09 AM
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.143
DHCPv6 IAID . . . . . . . . . . . : 318776856
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-86-03-1B-00-26-18-59-33-E7
DNS Servers . . . . . . . . . . . : 10.0.0.143
Primary WINS Server . . . . . . . : 10.0.0.143
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Users\rony>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : easyworship
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : bbc.church
Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-26-18-59-33-E7
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-26-18-59-39-09
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2dc4:cf48:667:cdcc%12(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.254(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 318776856
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-86-03-1B-00-26-18-59-33-E7
DNS Servers . . . . . . . . . . . : 10.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:18b2:174d:9bd9:7cfa(Preferred)
Link-local IPv6 Address . . . . . : fe80::18b2:174d:9bd9:7cfa%11(Preferred)
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : 184549376
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-86-03-1B-00-26-18-59-33-E7
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\rony>

the second one is with the static ip which has the same gateway as the ipads. There should've been a connection with the static ip.

DNS is the big thing for computers making connections to each other. I noticed they are different depending on DHCP or not. The first shows DNS Server 10.0.0.143. The second shows 10.0.0.1. Normally, they would stay the same no matter what.

If the phones are connecting without issue, then I would suspect something wrong with the iPad. I have connected an older iPad 4 with no problems.

the first DNS was with DHCP on then I pot the second one DNS 10.0.01.1 when on static ip. DNS 10.0.0.1 is the one I use with the ipads. I posted both DNS to show that it makes no difference with set up I used there is still no connection

The only time it worked, which was for a very time it was on static ip

the first DNS was with DHCP on then I pot the second one DNS 10.0.01.1 when on static ip. DNS 10.0.0.1 is the one I use with the ipads. I posted both DNS to show that it makes no difference with set up I used there is still no connection

Typically, DNS server would be the same no matter what. DHCP or static.

If iPhones connect without issue, something is clearly going bad with the iPads. Would be interesting to see their network settings.

IPv4 Address. . . . . . . . . . . : 10.0.0.249
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1

IPv4 Address. . . . . . . . . . . : 10.0.0.145
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1

This does sound like a dns issue on the ipads. If there is a way to clear the dns cache on an ipad you might try that. Or there is an issue with connecting to the Bonjour service running on the PC.
Please submit a ticket and reference this Forum thread so one of our techs can help you out with this issue.
https://support.easyworship.com/support/tickets/new

I solved it by creating a separate network just for the iPad and the easyworship computer. Thanks for all the help

Sorry guys the solution did not last 24 hrs. I turned both PC and iPad last thinking that problem was solved. Tonight for good Friday concert we couldn't make connections at all. Even the iPhone was unable to connect. The network setting was the same as before. I can conclude that the iOS app is the issue

Sorry guys the solution did not last 24 hrs. I turned both PC and iPad last thinking that problem was solved. Tonight for good Friday concert we couldn't make connections at all. Even the iPhone was unable to connect. The network setting was the same as before. I can conclude that the iOS app is the issue

While I have had some refresh issues with the app, I have never had a problem connecting, even back when it was in beta. And since this does not seem to be a problem that others are having, there must be some issue with your particular setup. Not to say anything you are doing is wrong, but from looking at the forums, this is an isolated problem. I recommend opening a ticket with support.