anyone like network function in 7/vista?

If anyone know of a way to disable "IDENTIFYING NETWORK" and just defaulting all connections to private, please let me know ... otherwise read on and VOTE IN THE POLL

-----

I move from location to location several times a day and have to change my network address and settings as many as 20 times in the course of a normal work day. Often when confguring firewall, etc.

I have been using MS OS since DOS 1.2 and kinda know what i'm doing.

I use MS OS because all the lemmings use it and i need to have practical experience with it.

I was hoping MS would redeem themselves in 7 when "fixing" the problems, but i've just installed the RTM version of 7 and alas no reprieve:

Since vista, the amount of time i spend changing from network to network is RIDICULOUS!

• clicky pointy clicky pointy clicky pointy TYPE IP, MASK, GATEWAY, DNS
• wait (minutes) for @#*@(&#(*&@(*# identifying network wizard to run
• clicky pointy clicky pointy SET NETWORK AS PRIVATE
• wait for private settings to take effect
• finally i can get back to work -

unless ...

when changing networks as frequently as i do, the network identification frequently fails in a variety of ways

• set as private network, click ok, clicks accepted, but network still set at public
• set again, sometimes okay - but often a reboot is required to get network working again -GARBAGE!!!
• often i cannot set network as private, it is greyed out
• interesting to note that the virtual instance of xp (in 7) or the virtual pc copy of xp i run often continues to work even while the vista host machine does not (indicating a problem with vista)
• etc, etc

THIS IS A GIGANTIC TIME WASTER and I BILL ONLY FOR MY TIME - this is tantamount to MS PENALYZING ME for not being a novice user on a home network

MS - good work for the unskilled/uninformed users
MS - GIVE THE IT COMMUNITY the ability to turn it off so we can JUST GET TO WORK.
MS - I want an XP like experience - set ip, select OK, just get to work!!!

PLEASE TAKE A MINUTE AND VOTE IN THE POLL - the squeaky wheel gets the grease so start squeaking!

ericjmail said:

If anyone know of a way to disable "IDENTIFYING NETWORK"

Would this do?

Disable the “Set Network Location” dialog in Vista - Windows Live

(I haven't actually tested that because I'm in Windows XP at the moment)

Just an update ...

Alas, sup3rsport's suggested fix does not address the issue

The punishment continues unabated in windows 7

I never had a problem in Vista. I primarily use my home network but also have settings saved for a few other places I frequent (a starbucks, my local airport, friend's houses, etc.) I simply prioritize them and if it can't connect to Home, it tries the next one on the list and so on and so forth. Works like a charm?

in reply to "aem"'s question about "20 networks a day"

08:00 am - arrive on site with a new firewall, and 3 mesh network Access Points - all devices have a default IP that differs from the client IP

IP CHANGE 1. connect laptop to client's current network to obtain client's IP address info for firewall's internet port
IP CHANGE 2. set laptop ip address to default IP range used by new firewall
IP CHANGE 3. set laptop ip address to client's LAN address & continue firewall config
IP CHANGE 4. (rarely) config laptop ip address to IP of client's internet port for testing to verify operational status of circuit from ISP
IP CHANGE 5. set leptop ip address to default ip range used by mesh AP #1
ip change 6. set laptop IP address to client's lan to test AP association on wirless NIC
ip change 7. set laptop ip address to ap's management network address and verify operation
IP CHANGE 8. set leptop ip address to default ip range used by mesh AP #2
ip change 9. set laptop IP address to client's lan to test AP association on wirless NIC
ip change 10. set laptop ip address to ap's management network address and verify operation
IP CHANGE 11. set leptop ip address to default ip range used by mesh AP #3
ip change 12. set laptop IP address to client's lan to test AP association on wirless NIC
ip change 13. set laptop ip address to ap's management network address and verify operation
ip change 14. set laptop ip address to client's lan to do some other work
---
11:00 arrive at next site
IP change 15. set laptop ip to client's lan to do some work

12:00 arrive at coffee shop for a re-charge
IP change 16. set laptop ip to use wireless lan at coffee shop

12:45 arrive at next site
ip change 17. set laptop ip to client's wired lan & do some work
ip change 18. set laptop ip to client's private wireless lan and do some work
ip change 19. set laptop ip to client's public wirelss lan and do some work

14:30 arrive at next site
ip change 20. set laptop ip to client's lan and do some work

16:30 arrive at office
ip change 21. set laptop ip to office lan, and do some work

no kidding - this is a fair representation of an average day

between 8 am and 11 am i've had to reboot several times and have spent at least 30 minutes @*(#&(@# around with this junky junky garbage *@*@# networking junk that MS added to vista/7/server 08

best work around yet is setting policy to just trust every network, far more stable that way but still killing time for NO GOOD REASON!!!

c'mon MS FIX THE DARN THING!