DaveRVW

Awesome! 

Your mention that, at work, that you find that "the DNS entry is my home router, not my work DNS" is interesting.  What do you mean by that?  There's not a power-cycle-to-power-cycle persistent storage of a dynamically assigned dns name.

DNS server(s) appears to be up to two IP addresses.  Took my Netduino to work, and while it was using DHCP and the IP showed up in the proper 192.168.x.x range, it kept my home DNS in the 10.x.y.z. range.   I had been switching between static and dynamic IPs, and/or lost my network settings a few times too.  But I don't remember changing to static DNS.  The "fix" to call EnableDynamicDns() was unexpected.

Now everything is working fine.

More news.

I called net.EnableDynamicDns() [font="arial, helvetica, sans-serif;"]and now DNS is working again, including requesting and receiving DNS servers during DHCP.  My Netduino was recently reset and I had to reset the MAC address.  Not sure why the default would be to not ask for DNS servers in this state.[/font]

[font="arial, helvetica, sans-serif;"]So the original complaint is not complete, but there is something not quite right here that I have to call EnableDynamicDns() from this state.  This is not expected.[/font]

Ah, the device supports both SPI and I2C.  Yeah, stick with SPI when you can get it to work.

I got confused when you called pin 5 of the Parallax module SDA.  That's for I2C.  The SPI function of that pin is SDI.

Sorry I don't have the module myself to try.  Hopefully another user can help.

Good luck!

You may have SPI and I2C confused. SDA and SCL are I2C connections, and there are dedicated (and mirrored) connections on the shield base.  You may also need 3V pull ups (e.g. 2.2k or similar) for SDA and SCL to work correctly.

And use the I2C APIs instead of the SPI APIs.