Url: http://www.abinaapparel.com I can log into the account no problem, the code that works for everyone else and that has been working for me (for months) hasn't been altered in any fashion and appears to be fine, and I can bring up ads.digitalpoint.com from the server, but I cannot retrieve ads from DigitalPoint. Have I been banned? Just trying to eliminate possibilities in figuring out how to get things working again.
Ok, after further testing here's what I've found (disregard anything said in the prior post ): At this point I cannot bring up http://ads.digitalpoint.com from a browser on either server, nor can I access this URL via ASP Microsoft.XMLHTTP object or .NET's HttpWebRequest/WebResponse objects. I can't "access" it even by direct IP address (216.9.35.50) from either machine. I can access other URL's via these methods from these servers, thus it's not a connection problem on these servers. I CAN access the aforementioned DP URL via 2 other servers on the same IP block (216.168.129.*), as well as from machines on 3 other different IP blocks that I have access to, thus ruling out a DNS issue on my end (since they're all using our DNS servers). I'm running the co-op on about 20 or so different sites (yes, I do love the coop ) on different IP addresses all within the same Class C. I'm at a loss here and a lonely sailor without my coop . I'm trying to think of what could it be on the 2 machines that would suddenly deny itself access to ads.digitalpoint.com. Hopefully I've not exceded my limits on requests (doubtful though since I'm using the Shawn-approved component from http://forums.digitalpoint.com/showthread.php?t=17092). Also worth mentioning is that this has all been set up and working fine for months on all my sites, until the last day or two (not sure the specific date since wasn't online much during the US holiday weekend). Thanks again for the help! Amazing that you manage to continue to grow your network and get things done while playing Tech Support all day.
It looks like 216.168.129.14 was blocked automatically by the system because it was not caching ads. Is that your servers IP?
Yes, that is me. Not sure what I did wrong; I just use the aforementioned .NET component that has always worked without problems for months until now?? Like I said, there's quite a few sites running the co-op network on this server, as well as on 216.168.133.13. What can I do to un-ban them and make certain my sites start caching the ads again?
It also appears that I may not be alone in this phenomenon: http://forums.digitalpoint.com/showthread.php?t=17092&page=3
At the moment, no. I've deleted the file a couple of times in trying to get it to work, and after deleting it, it is re-created by the component and contains: <?xml version="1.0" encoding="utf-8" ?> - <Settings xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <LogStats>false</LogStats> <SupportedAgents /> <MaxAdCount>0</MaxAdCount> <QuickRewnewTime>0</QuickRewnewTime> <RenewTime>0</RenewTime> <Ads /> <LastFetch>2005-11-29T14:23:32.0625000-05:00</LastFetch> </Settings> Code (markup): Thus, the file is in fact writeable. There wouldn't be any ads in it anyway, as the server's IP address is being blocked so there is nothing to retrieve and write to it. I just updated my site to use the new coop component that Slightly uploaded just a short while ago, which will not fetch ads in the event the file is un-writeable. Hopefully in the event my IP is un-blocked this will prevent any type of excessive request on your system I'm sorry if my server hit yours too much