(no subject)
Jul. 27th, 2012 10:24 am
Jul. 27th, 2012
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif){kind=small}
Borderlands 2 is on pre-release. I'm buying a 4-pack on principle but all four spots aren't taken yet - who wants in for $40?
Borderlands 1 is 75% off, currently at $7.50 for the game and all DLC. Oh, and it's free to play all weekend - so you have no excuse.
Borderlands 1 is 75% off, currently at $7.50 for the game and all DLC. Oh, and it's free to play all weekend - so you have no excuse.
Geek pop quiz.
Jul. 27th, 2012 06:05 pmA server is, for unknown reasons, trying to connect to ip A for updates to an application. It SHOULD be connecting to ip B. The application configuration is correct. A complete reinstall, down to digging it out of the registry and deleting all the folders, has not solved the problem.
A brute-force solution presents itself: forcibly redirect all connection to A to B instead. Difficulty: they are on the same subnet, and you cannot change anything about the switches, routers, or, in fact, anything except Windows itself on this one machine.
And it's an IP, NOT a dns name. Hosts file won't do it unless you can provide syntax for ip redirection via hosts.
Is there a way to do that in windows server 2008, via "route" or something?
Posted via the phone of doom
A brute-force solution presents itself: forcibly redirect all connection to A to B instead. Difficulty: they are on the same subnet, and you cannot change anything about the switches, routers, or, in fact, anything except Windows itself on this one machine.
And it's an IP, NOT a dns name. Hosts file won't do it unless you can provide syntax for ip redirection via hosts.
Is there a way to do that in windows server 2008, via "route" or something?
Posted via the phone of doom