OK, thanks. Here's the latest:
- double checked the local IP and it did seem to be different to what was in my router settings (and I could have sworn it was showing earlier today). Anyway, have updated router accordingly

- subsonic previously seemed to be set up on 3180 in the systray app (although this port previously forwarded in the router had been disabled), so guess was working before via auto configure option..
- Network settings in Subsonic intermittently seem to show port forwarded ok + domain registered but can't connect
- I previously tried turning off auto configure in subsonic, but again nothing stuck (once minute ok, next not.. but mostly not)
- If I now put the domain into my browser (on the same network) it does resolve to the correct IP and so allows me to run subsonic locally (as does localhost address of course)
- despite the above, my phone app simply shows 'not found' when I test the connection or try to gain access
Questions:
- portforward website says you should set up subsonic ports on both 80 and 4040; also shows them set as "both" (I previously had them as TCP only). Are these instructions all correct?
Aside from the general frustration, most of all it's the fact that this seems to happen again and again, and often for very little obvious reason. As the other person now in this thread just said, could it be anything to do with a subsonic update - does anything revert to default setting that needs to be tweaked back etc..?
Otherwise, just wish there was an easier way to make sure the thing connected (often recommend this to others, but have to admit not sure how they'd cope when this keeps happening, for whatever reason).
Again, answers/advice much appreciated!!
