Thanks James, but no, I aready disabled IPV6 and it did not help, I have however found how to get the iTunes server working but have no idea why;
entering 'mt-daapd' into the run command produces this in the system log,
Feb 11 18:48:58 mt-daapd[1006]: Starting rendezvous daemon
Feb 11 18:48:58 mt-daapd[1008]: Starting signal handler
Feb 11 18:48:58 mt-daapd[1008]: Loading playlists
Feb 11 18:48:58 mt-daapd[1008]: Initializing database
Feb 11 18:48:58 mt-daapd[1008]: Starting mp3 scan
Feb 11 18:49:42 mt-daapd[941]: Starting web server from /rom/etc/web on port 3689
Feb 11 18:49:42 mt-daapd[941]: Registering rendezvous names
Feb 11 18:49:42 mt-daapd[941]: Scanned 8461 songs in 314 seconds
Feb 11 18:49:42 mt-daapd[934]: Starting web server from /rom/etc/web on port 3689
Feb 11 18:49:42 mt-daapd[934]: Could not open port: Address already in use
Feb 11 18:49:42 mt-daapd[934]: Error staring web server: Address already in use
Feb 11 18:49:42 mt-daapd[934]: Aborting
Feb 11 18:49:42 mt-daapd[927]: Starting web server from /rom/etc/web on port 3689
Feb 11 18:49:42 mt-daapd[927]: Could not open port: Address already in use
Feb 11 18:49:42 mt-daapd[927]: Error staring web server: Address already in use
Feb 11 18:49:42 mt-daapd[927]: Aborting
Feb 11 18:49:42 mt-daapd[926]: Rendezvous socket closed (daap server crashed?) Aborting.
Feb 11 18:49:42 mt-daapd[926]: Aborting
Feb 11 18:49:42 mt-daapd[933]: Rendezvous socket closed (daap server crashed?) Aborting.
Feb 11 18:49:42 mt-daapd[933]: Aborting
however, navigating to
http://192.168.1.1:3689/ produces a mt-daapd status page stating that the 'rendezvous' service is not configured, does the server rely on rendezvous because it doesn't appear to be auto starting.
I have no understanding of any of this, so hopefully someone more knowledgeable does!
Edit:
Seems this problem is definitely related to the Rendezvous (which appears to be the first iteration of Bonjour) service, since it is now showing as running and the server is working perfectly. Interestingly, the uptime at
http://192.168.1.1:3689/status.html is now correct but when the server wasn't functioning, the uptime was displaying 1127 Days, xx Hours, xx Days, xx Seconds.