QUOTE(carmico @ 10-12-06, 6:10pm)

I have a pap2 vonage blocked with fw. 3.1.12 . Never connected to the internet.
I don't know if anybody else in this thread succeeded in unlocking such a PAP2; however, in theory it SHOULD work no differently than 3.1.9.
QUOTE(carmico @ 10-12-06, 6:10pm)

I'm following the dingler's method with a laptop. Using the exact method of the dingler's example.
Ok.. but that's "Diggler," not "dingler."

QUOTE(carmico @ 10-12-06, 6:10pm)

I have everything,the encrypted xml file downloaded from vonage tftp server, TFTP server solar winds, winxp http information server, dhcp & dns server trough winxp ICS. Modified hosts file like the example.
Everything is equal to the dingler's example unblock.
Ok, everything above looks good, except once again it's "Diggler," not "dingler."

QUOTE(carmico @ 10-12-06, 6:10pm)

The unblock process stopped me at the firmware downloading part.
Ok, this is where your details start to get a little fuzzy.
QUOTE(carmico @ 10-12-06, 6:10pm)

The tftp sent the encrypted xml to the pap2. then the pap2 request the other xml but failed, after that the pap2 has to process the firmware, but here is the problem, doesn't process the firmware, doesn't reboot. Stop it there.
Does the PAP2 make an HTTP request to the IIS HTTP server? You can look in the IIS logs for this (C:\WINDOWS\system32\Logfiles\W3SVC1). Also, have you tried packet sniffing the connection? Since you're using ICS and a crossover cable, it's easy to sniff the connection to 192.168.0.1 (which is the IP Address the PC running ICS). The packet sniff will show whether the PAP2 has made any HTTP requests.
QUOTE(carmico @ 10-12-06, 6:10pm)

excuse me for my english, i'm italian.
Your english, I promise, is much better than my italian!

Diggler