I recently upgraded my modem and router to take advantage of new internet speeds being offered. I'm trying to get my panel app up and running again but I'm running into some issues. First of all, my xp3 is not showing up in the list of devices on my router. Is this normal? I set up a DNS server on my router and was preparing to set up port forwarding when I realized that I have no idea what the IP address of the processor is? Is this info readily available/standard. I guess if I can't get this figured out I'll need to have the installer come out. I was trying to avoid this and the hefty fee that comes with it if at all possible.

Thanks

download Angry IP Scanner. Scan your network. If the RTI is connected, it will show it and it's IP address

Your new router is probably on another subnet. I would send a test file consisting of only a control processor set to DHCP in the settings. Once the processor is assigned a DHCP address you can then either reserve it by MAC address or at least change your current system file under processor properties to the right subnet.

Thanks for the help. I have everything up and running again!

Glad to hear it!

Hi Vincent,

I'm hoping you can help me too.

I have an Rti system I am having problems with after my most recent renter "played with" the rack leaving none of my whole house 8 zones playing music.

Fortunately, I was able to straighten out a bunch of wires and patch them back correctly and as a result got the 4 zones attached to the main rack working properly.

The four rooms connected to the living room ad-4x in our main rack with the Sonos module, all are working properly in Rti panel and music can be heard an adjusted as intended. I can also see the Living room xp3 and ad-4x on my network and access them via they're ip addresses via a browser.

The for rooms attached to the Bedroom ad-4x and xp3 do not get any music. When any of of these rooms volume controls are slid up, a second later goes back to the off (-75) position. In addition If I try to select sonos or airplay, the icon flashes but the input is remains as "unknown" and a red 0 (zero) is above the channel slider (the channels that work on the living ad-4x have a green "on" in this position.
I cannot see the ad-4x and xp3 on my network. There is one ip address I can't access that I'm trying to determine if it is possibly the xp3 or ad-4x.


It seems like a communication problem and our installer has been "putting us on the schedule" for over a month and now has gone dark after I asked him to email me our configuration files.

Any suggestions or help would be appreciated.

SO THANK YOU in advance.

Equipment:

Living room (main rack)
Denon receiver
Rti ad-4x
Rti xp-3
Rti T2i remote
Sonos
AppleTv

Bedroom
Rti ad-4x
Rtis xp-3
Rti T2i remote

ptgerald,

Of course, it would be best if you could consult with the original installer.

Your symptoms indicate that the Bedroom is not communicating. When you drag a slider, it will move, then wait for a response. If there is no response, the slider will return to the original position.

Duplicate IP addresses can cause transient, vexing issues.

You somehow figured out the IP addresses of the RTI units in the main rack. Likely, the RTI units are using fixed IP addresses. If the router has been replaced, it is probably using its default DHCP range and it is very possible that the DHCP range could overlap the fixed RTI addresses. In my systems, I’ll usually start the DHCP range at .40 and place my fixed IP addresses below 40. Assuming, that the installer has a similar strategy and that the RTI devices reside in a close cluster of addresses, start with the IP addresses of RTI devices that are working and carve out a block of addresses in that range.

It would not be wrong to reboot everything on the network after you change the DHCP range.

After the reboot, “Reserve” IP addresses for every known device, making sure that the RTI addresses are unique. Some installers will simply reserve RTI addresses and allow them to be within the DHCP range. This is not my style.

When in diagnostic mode, never assume that the problem must be [...] or cannot be [ ... ]. Be sure to consider bad cables and bad hardware.