Stop making this public, immediately. This is for your own good, trust me.

Says the guy who has been banned before.

LINK OR GTFO!!

No boo, but you were banned temporarily a while back.

1. DNS Problem: Solution 1
Ok people, starting with this How to stuff. Lets define the problem,
PS2 attempts to validate via the DNAS check, then attempts to connect to first capcom server.
The DNAS Server is still up and working, so thats not a problem as such, we just need access to the internet for that. Problem is Capcom server is down and the DNS doesnt respond/times out. As the domain name for this capcom server is hardcoded into the disc we can't easily change that (without modifying the disc)

Requirements:
1.PS2 Still connects to internet for DNAS
2.PS2 Recieves different and valid DNS Record for the downed Capcom server.
3. PS2 Connects to stable state.

Solution:
DNS Servers work in a request based way, where a client will send a request saying "Hey whats the IP Address for yadda yadda yadda.capcom.com" and the DNS Server will look up to see what that IP address is (like a telephone book). If it does not have a record, it will bounce the request to its secondary DNS Servers to see if they have got a record, till eventually all servers shrug their shoulders and say "Nope, we dont know where that is".
This logic holds the key, where by the client who asks for this request can specify who the first DNS Server to ask before it bounces off. So what is stopping me setting up my own private DNS Server to respond to these requests, nothing! From what I gather, this is not illegal as its my private Domain (correct me if im wrong) and ive not hacked the disc in any way.
So what I could have is this,
PS2 requests DNS Record from PrivateDNSServer#1,
PrivateDNSServer#1 sees if it has a record and responds if so,
If no record exists, bounce the request to a public DNS Server (one provided by my ISP).

So if I have my PrivateDNSServer#1 only have records on the downed servers (so just yadda yadda yadda.capcom.com) and bounce any other requests (DNAS Server)to the publicDNSServer.
Simples.

One catch, this is not global because any other players would require access to my DNS Server by IP Address. If you came along to my house to play, this wouldnt be a problem, but still you folks across the waters should be able to play. There are ways to circumvent this (I think). One way would be for me to open up my DNS server to you guys, providing my IP Address so you can connect (The problem with this though it requires me to have a Static IP address otherwise you will be changing your configs each time my ISP provides me a new IP Address, so once every few weeks). Another solution would be to utilize VPN's but Im not 100% sure how well that will turn out.

When I first attempted this, I used my copy of Windows Server 2003 (In a virtual machine) to quickly set up the DNS Server (You can do this just as well in Linux, but my shell work is terrible). Details to setup DNS server in Windows and Linux are easily available online.
Essentially what you require to do is:
Setup required DNS Lookup records
Setup Secondary DNS/DNS Forwarding.

As for Playstation 2 requirements/setup:
1. Change the Network config.
2. Dont use DHCP option unless you have messed around with your DHCP server to take account your new DNS Server else you could cause all sorts of problems with family/housemates/drunk version of yourself.
3. Use static IP Address, enter in a valid IP, subnet and gateway address for your network (Make sure there is a range for non DHCP assigned ip addresses available). For example mine would be:
IP: 192.168.1.5
Subnet: 255.255.255.0
Gateway 192.168.1.1
You will need to work out your values for your network, for Windows load command prompt and enter ipconfig (ifconfig/iwconfig if your a mighty Linux user, and for Mac, f**k Mac). Here you can grab your gateway IP and your subnet. Why am I even stating this, if youve managed to rig up DNS Server then this stuff is fundamental
4. Hit next,For the DNS Server, just enter the address of your private dns server and Boom done.

Hope this has helped you as much it will me when I go to setup my private DNS Server
Posted by Fulci666 at 09:30 0 comments

Monday, 27 February 2012
Domain names
app01.reo.capcom.sf.yav4.com
http://stage6.sega.com/mhweb/index.jsp?DNAS=
snap01.capcom.client.sf.yav4.com

Pulled from outbreak file 2 UK disc. These domain names fit with my idea, App01 is the Capcom Custom code server which deals with the login and registration stuff.
Stage6 sounds like its related to the DNAS (Duh')
Snap01 will be the sega/nokia snap server. So essentially app01 is the transition between problem 1 and problem 2.
Posted by Fulci666 at 11:06 8 comments

By now the only method not used out of desperation is hiring a sky writer.