As the former owner of the site in question, the increase in membership because of Atlas closing wasn't that big of a deal. We always figured that most would end up here on TB anyways. It takes a lot of work to keep these forums going. Just ask Charlie and the staff here. You get what you get, nothing more, nothing less.
Exactly, and all problems force forum managers into a reactionary position and recovering from a problem is not easy. Remember, we were down for almost 72 hours two months ago and it was costly to turn it all back on. When people are critical, they usually have no idea what it's like to be on the other side. It takes time, and money. Charlie
Charlie...John.... Please dont take my comments as critical. The where constructive in nature. I DO know what its like to be on the other side. As some background...in the late 90' early 00's I owned 2 seperate websites. I sold both at enough profit to put 3 kids through college. I DO have knowledge of how hard it all is. Although NOT forum in nature I still had to be vigilant and try to anticipate any problems. It was a 24 hour a day job. I always tried to be proactive as oppossed to reactive. I would say on a forum based website members get more upset when things get fubar as oppossed to a merchandise based website. I dont think, nor indicated, that you guys have it easy by any stretch of the imagination. Agreed...some problems cant be forseen....thats a given. I just feel that with Atlas folding other train forums should have known it would affect them one way or the other. One of the original replies in this thread indicated that increased activity basically crashed the railwire website. I based my replies on that. I appologize if my comments where misread or seemed to be arguementative in nature...thnxs. George I would NEVER try to tell anyone how to run their website.
For those of us who are affected, the issue still exists, despite clearing cookies, trying different browsers (Chrome & IE for me) and also logging through from entirely different access points (home is att.net and work is what it is --- ). I happen to live in Texas, so maybe remoteness from the core of the railwire.net provider's service ( presumably East Coast?) has a bit to do with this?
I am on the West Coast and I am having no problems. Once your ISP gets its DNS entry updated you'll be able to login again.
I am in Texas, and it is hit or miss. I'm not sure it's 100% solely a DNS propagation issue, but that's at least part of it. I have hit (or not) the site from three different clients (WinXP using 3 diff browsers via 3G Hotspot, an iPad via Uverse, and Win7 using Chrome and IE via T1 at work) and it works fine one minute and the next it's a goner. But I'm not logging into the site--just hitting the page as a visitor--so that might make a difference. One thing you can try is to clear your DNS cache on your operating system. (Run: Cmd.exe --> ipconfig /flushdns on Windows)
Well this is weird as I just tried for the heck of it and I could get in even though I was banned from there. Go figure!
A word of caution. I have tried to go on Railwire 3 times in the past 2 days and all 3 attempts resulted in my Antivirus program flashing a Malware Detected meesage, It prevented the malware from getting into my system.
On of the gang over there gave me a work around - I went into my hosts file and added the url and ip address for the Railwire and saved it - after that I get in no problem... I guess my provider as a DNS propigation issue...and I haven't got a clue what all that I just typed means, except i get to log in on RW now...yaaaaahhh !
I can get in today without issue but those still having problem there is nearly nothing on your end that you can do until your path into the internet is updated with the new IP for the site; just give it a few more days. As for the previously mention of Malware / Tracking Cookies concern, I am not detecting any on Railwire while I do here at TB; normally Google +1, Facebook, and Twitter tracking due to those features being enabled here. Nothing malicious just simple tracking of non-personal data which is common for any site using those features. Using AVG Anti-Virus Free Edition 2012 I can detect and block those simple enough...
on windows start 'cmd', then enter 'ipconfig /flushdns' might clear your local dns cache. i don't think dns propagation is an issue here. i run my webservers using dynamic dns. propagation usually is done within 60 seconds.
