I have just received my new Ant S1's trying to connect them to my node on the local network I have setup the following 3 pools
Pool 1 192.168.1.20:9332
Pool 2 100.166.178.107:9332
pool 3 us2.eclipsemc.com:3333
but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.
I'm a relative P2Pool noob myself running an S1 and was able to get it going without too much difficulty. Had a couple of minor IP addressing issues myself, but fully operator error. I'm about 10 days ahead of you on this so will offer my "noob" experience.
You say you were mining for awhile with U1s...were those mining to the same local p2pool node at 192.168.1.20?
You mention dhcp...I'm assuming the machine you're running your node on is configured to use 192.168.1.20 as a static address rather than getting dhcp leases? That was one of my early problems...I'd assumed my machine was using a static (as I try to avoid DHCP as a rule on LANs) and I tried a bunch of other things before it occured to me that dynamic ip addressing was the issue.
Since you can ping 192.168.1.20 but the ant doesn't see the pool its a possibility that you're pinging a different machine thats not running the p2pool and your bitcoind (or qt).
Lastly, your bitcoind is running and fully synced?
In addition to a screenshot of your S! config screen a shot of your P2Pool window would be helpful as well
good luck