Pinging local computers by name results in a WAN address resolution instead of local 192....

I have a windows workgroup network consisting of 4 windows XP Pro computers (and 1 Vista business).  The network is used for basic file sharing, printer sharing and one application that runs off a SQL database on a single workstation.

The network was fully operational until we swapped out a router (we upgraded from an old 802.11b dlink to a new dlink DIR-655).  At the time of the router switch we lost access to both the printer and the SQL database.  We can successfully ping ALL computers and devices by IP address, we can browse the network computers from each workstation, we can copy files back and forth, internet access is fully functional, etc... However when pinging a local computer or device name, I get an internet address (208.69....).  Running a traceroute on the local computer/device name confirms that we are routing out over the internet.

As a result, when we try to access the SQL database from another workstation, it is not able to resolve it properly.  The same thing is happening with the network printers.  There is a wireless brother printer that properly responds to the brother diagnostics software when run from a workstation, but all attempts to print to it fail.

I tried swapping the old router back, and the problem remains.

Currently the Config is as follows:
1) Actiontec M1000 DSL (192.168.0.)
2) Dlink DIR-655 router/firewall (192.168.1.)
3) All computers are pulling DHCP from the dlink, and I have a lease reservation for the computer containing the SQL database
4) Windows firewall is DISABLED on all computers as is the antivirus currently
5) 3 computers are wired, the other 2 are wireless
6) DHCP is enabled on the actiontec (192.168.0.), and the dlink gets its WAN IP address from that
7) DHCP is configured on the dlink (192.168.1.100-192.168.1.130), and we are using openDNS for the DHCP provided dns servers.

This is a workgroup, so there is no internal DNS or WINS server.  I've tried adding lmhosts entries to force proper resolution, and that works when I ping a device - however it still does not allow me to access the printer or the SQL server service.

I've enabled dynamic routing on the actiontec DSL box thinking I had a problem between that and the dlink, but that had no bearing.