Solution to SD 'remote name not resolved' error

[sonofva]

Solution to: "The remote name could not be resolved:
‘webservices.prod.schedulesdirect.tmsdatadirect.com’" error line found at the following location:

http://forums.schedulesdirect.org/viewto...=240#p1455

The problem is that "prod." shouldn't be in the above name. The correct name is 'webservices.schedulesdirect.tmsdatadirect.com' and the address is 206.18.98.175

The quick fix is to go to c:\windows\system32\drivers\etc\hosts (on XP) and add the following line to the end of the file:

206.18.98.175 webservices.prod.schedulesdirect.tmsdatadirect.com

This is spelled out in detail at the above site.The fix :o worked for me.

[prouton]

Did you read Whurlston's reply to that post about the already supplied patch for GB-PVR? Sub really is quite good about supplying fixes before most people encounter them...but he can't force people to read the "1.0.16 Survival Guide" sticky at the top of the support section.

[sub]

sigh...yeah, what he said. READ THE SURVIVAL GUIDE THREAD.

The patch was required because the v1.0.16 release of GB-PVR was made before the Schedules Direct service went live, and the final production URL was not known at that stage. The patch to correct this URL has been available since the day Schedules Direct went live.