We are setting up our first Windows 7 Professional computer on our SCADA network. We use STATIC IP addresses and There is NO DHCP server or Domain server. We are having 2 Problems Problem #1 We are unable to change the network from Public to Work. The Public word that is normally blue is black and we can not click on it to select the type of network. Problem #2 We are unable to change the network name When we go to the screen to change the name, we can hilight the name but it will not allow us to change or delete the name. The curser will go there but no changes are allowed. Thanks -Me

For Windows 7 network types, the secret lies in the GATEWAY entry. Any network you connect on that doesn't have a DEFAULT GATEWAY provided with, becomes PUBLIC and you cannot change it's type. The solution is simple, specify the DEFAULT GATEWAY IP in the network properties . http://www.tomshardware.com/forum/215-63-change-network-type

Hi Brano, Thank you for your reply. We don't have a gateway, this network does not reach the internet, it is a private SCADA network, so I don't have a gateway to specify. I tried putting the computers own IP address in the gateway location and it simply didn't accept it. When I reopened the network properties, it would dissappear.Me

try using loopback address 127.0.0.1 If that doesn't work try switching the computer ip address to APIPA range 169.254.1.1

The name and the network location is obtained by NLA service from the gateway. Since you do not have a default gateway, the issue you described are all normal. It will not affect your works. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Brano, We use static IPs on all of the equipment on our network. Our address range is will out of the 127 range we use a 204.xxx.xxx.xxx range. Will that 127 loopback address work for our application (what is a loopback anyway?) We tried one of the answers on another thread (cant' remember which one) and we set it up so that if it doesn't have a gateway that it becomes a Home network. I don't think that it we will have any trouble with it because it will NEVER go anywhere else. Of cource that is not my first choice. What a Pain, I had NO trouble with XP now win 7 comes along and causes me Hours of trouble but trying to make things better! Thanks Microsoft for making things more difficult AGAIN! I can't imagine how many hours are lost due to upgrades all over the country!Me

Hi Arthur, Thanks for you reply. It does effect our works. Under these conditions (public network) we can not see the other computers on the network nor can we communicate with them. We can ping them but no other communication is allowed by the "security".Me

127.0.0.1 is telling computer to use it's own NIC as a default gateway. Even though the other computers are in different range i think it still could work. You may want to enforce the network location via is Group Policy http://www.sevenforums.com/tutorials/71785-network-location-enable-disable-change.html

Hi Brano, We use static IPs on all of the equipment on our network. Our address range is will out of the 127 range we use a 204.xxx.xxx.xxx range. Will that 127 loopback address work for our application (what is a loopback anyway?) . . . Thanks Microsoft for making things more difficult AGAIN! I can't imagine how many hours are lost due to upgrades all over the country! LTPInst, I don't mean no harm, but if you don't known what a loopback address is, then I don't think you are in a position to honestly say that MSFT is at fault for making things more difficult. Windows 7--and Vista before that--have been out for several years now. The issue you are experiencing is an easily fixed issue by those that are familiar and comfortable with Windows releases post XP. Because you decided to hold off of using the new Windows architecture that was introduced with Vista and chose to stick to XP is not a fault of MSFT. In either case, just set your gateway to your loopback (127.0.0.1) or to an arbitrary address such as 204.0.0.1. The gateway points to a router that routes traffic to a network that is not yours. For example, since you are using 204.xxx.xxx.xxx, the gateway would only come into affect if you were trying to connect to a 145.xxx.xxx.xxx network. Since you are isolated, you have no need; however, providing the gateway will allow you to change your network type. MSFT is not making things more difficult. Education is the key. While you are at it, why don't you give the Windows 8 Developer Preview (and soon to be released Consumer Preview (beta)) a try. That way, you can be up-to-speed when the actual Windows 8 client/server drops. Head on over to http://msdn.microsoft.com/en-us/windows/apps/br229516 to obtain a copy. Also, keep on on the latest advances by following the Building Windows 8 Blog: http://blogs.msdn.com/b/b8/.

Thank you Brano, I will give it a try as soon as I get a chance and will let you know the outcome.Me

Darien, First of all let me thank you for your description of a loopback address. When we can finally move over to a new platform, we do our best to work with what we are given. Yes sometimes we do get frustrated with Microsoft. It seems to be such a simple thing, Set the address and subnet mask and it should work. Well, we could ping the computer but weren't able to see the other computers on the network or communicate with the Historian. After reading up on the problem we decided that we had the wrong type of network showing, well we couldn't change it, no explanation no indication of why it would not change nothing. And yes it is frustrating, it seems that it is the simple things that can be the most frustrating. Like telling a computer to look at an NTP time server and set its time. Seems simple doesn't it? Well not on a network like ours Microsoft doesn't make these seemingly simple tasks simple. As a USER, my expectation of these simple tasks is that they are simple, I shouldn't have to go into the system regestery and change a bunch of stuff around just to make the simple stuff work. The reason that it has been so slow to change to Win 7 is that the manufacturers of the software that we use along with around 1/2 of all factories in America has just caught up rewriting their software to work with Windows 7. They have to do a lot of testing because of the reporting that is legally required by departments such as ours. I can't even fathom the hours upon hours all over the globe that are spent trying to keep up with Microsoft. It is unimagionable. My opinion is that the latest operating system should completely support the older programs. In an industrial environment this can be critical. Hours and hours are spent do develop specific operations and systems and then modified to work well. Then guess what? A new operating system comes out and Kapow! Things that have cost Thousands of dollars to develop no longer work. They cant even support older hardware. The cost to world industries is staggering. I understand the need to move ahead, but does that necessairly have to mean not supporting older programs and hardware? The same goes with consumers, "Guess what, I just upgraded to the latest operating system, but now my favorite games no longer work, I have to buy a new printer oh yeah and monitor too becuase it is not supported by the latest Operating system". We skipped right over Vista because the manufacture was not able to complete the testing before Windows 7 came out. And since Vista didn't last too long we just kept the same system until we knew there was a stable platform and the software that controls our facility was certified to be compatible. We can't just jump to the next platform just because it is out. You say windows 8? Forget about it, we haven't finished getting over to 7 it doesn't support the special cards that we use to communicate with our PLC's. Also we have 15 special work stations that cost around $6000.00 each. Windows 7 means that we have to replace all of those too. In our present economy it is simply not in the budget. Governments aren't making ends meet and these are the types of things that suffer. The Software manufacutrer's are just catching thier breath too and we have to wait for them. Yes clearly I do get frustrated with Microsoft. I don't know if you will read this and try to put yourself in my position or not. At least I tried. Me