Windows 7 RC - I can't change my network from public to work

Question

After a lot of job, I connected my W7 beta PC with my XP PC, but when I upgrade to W7 RC, I am unable to do this.
I have two net adapters: one linked to the internet cable modem and it is OK (public network). The other linked with a switch but W7 assigned this as unknown public network and I can't change it to home or work network. In W7 beta I assign a work network and it worked.
Thanks.

Answer 1

SOLUTION :
WINDOWS 7 WILL AUTOMATICALLY TAG THE CONNECTION AS UNDEFINED NETWORK WHEN IT IS UNABLE TO DETERMINE THE TYPE OF THE CONNECTION AND YOU ARE NOT ALLOWED TO CHANGE THE NAME AND TYPE OF THE NETWORK
The possible reasons are :
a. You are connecting to a network with TCP/IP configuration to automatic but the network doesn't have a DHCP server;
b. You configured the TCP/IP manually with static values but didn't specify a Default Gateway;
The possibles solutions are :
a. you are using dynamic IP, so you have to set up a software DHCP server on the 2nd subnet
b. you are using static IP, so set up a default gateway on the 2nd subnet NIC
( Source : http://windows7forums.com/windows-7-networking/4416-how-change-network-type-2.html  )
Hope this helps ^^
This solution works -- but unfortunately it requires the other network adapter to be on DHCP. If you want two adapters with fixed IP, you get messages that having two default gateways "does not work properly".  I tried it anyway -- this resulted in an unreachable internet via router. This all is in Win 7 RC, I will try it on a RTM (Ultimate) in a few moments, but I'm not expecting an improvement.
There is one thing you can do to ignore the problem without most of the negative aspects: turn off the firewall for your "private" network adapter. I don't see much danger here as that's roughly what would happen anyway if you could set it to private.
Having one line set to DHCP (to the router) and the other to use fixed IP will also not be without side effects. Suppose the DHCP line is only 100 Mb, while the internal net uses 1Gb. This will result in all network trafic using a computer name to pass via the 100 Mb line, which is probably not what you wanted. Maybe you could remedy that with a route command; but I have not succeeded in a non-temporary solution to this as the routes are not kept across reboots -- any help welcome.
Getting a DHCP server into this business will also not solve the problem, because then this computer needs to be online all the time, which is not what I would want. If your router (like mine) provides DHCP, you also get problems, because having two DHCPs will usually get you into trouble (this I read from other posts, never did it myself.)
Whoever is responsible for this mess at Microsoft should either provide a very good explanation or preferably fix it as fast as possible.
Maybe I don't understand you, but, if I have a router I don't need to use two adapters, I simply use the router as server and connect all of my computers to it.