Thanks for this discussion forum!

We ran a D-Link DIR-655 for about 5 years on our home network of 7 desktop computers (LAN) and two laptops (wireless) with essentially no problems. However following a power outage last week the router stopped communicating with the cable modem (WAN port failure?).
From the web site we determined that the DIR-825 is a fancier version of the DIR-655 (extra 5 GHz transmitter) so we upgraded to a new 825 three days ago.
I did not use the wizard on the CD to set up the new router -- rather did it manually because I thought I'd configure the new router exactly the same as the old one -- this was probably not a good idea in retrospect. (FYI our new DIR-825 is a ver. B1 unit with ver. 2.02NA firmware.
After setting the router up -- it lit up like a Christmas tree and I could see all 7 desk top computers (3 are WIN7 & 4 are WINXP) in the LAN and all would go on-line with no issues. (FYI 3 desk tops are directly attached to the DIR-825 and four attached via a switch).
However, when I tried to map the network I find that only 5 of the desk tops we assigned to our named home network -- 2 or them could not be mapped as they were assigned to a "public" network. So while they all still communicate with each other two are no longer in our home network. I do not think this was anything that I did -- knowingly at least.
I logged back on the the router home page but I see nothing that clues me in as to what I did wrong.
So I'm wondering how the DIR-825 made these "assignments" and what I can do to redirect the router to bring the other two computers into our home network. (BTW one of the two "miss-assigned" computers is WIN7 and one is WINXP so its not a window version issue).
Thanks for any assistance! Smiley