Upgrade from 32 to 64-bit Windows 7, now Network won't connect

normanlives8

Reputable
Jan 5, 2015
2
0
4,510
I am having trouble with the connection to a server dropping out after about 1 minute.

We run 2 computers, one is our design computer and the other is our office computer. These are not connected in any way but are connected to separate networks.

Here’s some background about the network between the design computers. We run a very simple little network. It’s basically 4 computers plugged into a 100mbps switch which is plugged into an old desktop PC to act as our server. I am aware this isn’t the best or most secure setup but it’s cheap and it works. This does not have internet connection either.

We also have a second network that connects the rest of the office computers through the business. This is connected through a gigabit switch and does have internet connection.
I have upgraded one of the design computers from a 32 bit version of windows 7 to a 64 bit version. The system page did state the processor was 64-bit compatible. This was in preparation for some new software we are having installed. After installing the new version of windows 7, I plugged it into the network which has an internet connection and installed windows updates available. However when disconnected it from that network and connected it to the design network it could not find the design server. It does find other computers on the network (some intermittently disappear then re-appear) but won’t find the computer we have set up as our server. In the network sharing option I have made sure discoverability is turned on and file sharing is enabled. I have tried typing the server name when mapping the network drive and searching for it on the network but it cannot connect.

I swapped the Ethernet cable from the computer at the next desk (which does connect to the network) but there was no change. This lead me to believe it is not a problem with the network, but a setting is wrong on the computer. I have also manually changed the network adapter driver to the 64-bit version but this didn’t help either. This computer was attached to the same network before it was updated to a 64-bit version and there were no problems at all.

To complicate the issue further, I have found a way to get the computer to find the server. If I plug it into the network that has an internet connection for a few minutes, then swap back to the design network, the design server shows straight away in the network connections and allows you to map it as a network drive. However after less than 1 minute this connection drops out and you can no longer connect. Disabling/re-enabling the network adapter doesn’t work, it has to be switched from the network with internet connection to the one without, and even then it lasts less than 1 minute.

Any ideas are welcome!
 
Solution
In your server (non-Internet) network, is there a router which is handing out IP addresses and handling DNS/WINS? Or is the server doing it? Or do you have everything configured as static addresses?

Without more info on how that network is set up, it sounds like the computers on it are set up with static IP addresses. When you reinstalled Windows on the computer, it defaulted to looking for a dynamic IP address. Your server network is not handing out dynamic IP addresses, so the computer is unable to talk to anything on the network.

When you connect to the regular network (with Internet), the computer is getting a dynamic IP address. When you quickly switch it to the server network, it is briefly retaining that IP address which...

normanlives8

Reputable
Jan 5, 2015
2
0
4,510


Yes, sorry I wasn't very clear.
I did a complete re-install (to Win 7 64 bit) and am now trying to connect to the Network the computer was originally connected to.
 
In your server (non-Internet) network, is there a router which is handing out IP addresses and handling DNS/WINS? Or is the server doing it? Or do you have everything configured as static addresses?

Without more info on how that network is set up, it sounds like the computers on it are set up with static IP addresses. When you reinstalled Windows on the computer, it defaulted to looking for a dynamic IP address. Your server network is not handing out dynamic IP addresses, so the computer is unable to talk to anything on the network.

When you connect to the regular network (with Internet), the computer is getting a dynamic IP address. When you quickly switch it to the server network, it is briefly retaining that IP address which apparently allows it to talk with other computers on that network. But a minute later it realizes it can't contact the DHCP server, revokes the IP address, and it can't talk to anything on the network again.

Go to one of the (working) computers on the server network and check to see if it's using a static IP address.

Control Panel -> View Network Status and Tasks
Click on the network next to Connections:
Click Details button
See what it says next to DHCP enabled

"No" indicates the computer is set up with a static IP address. If it says "no", you have to set up the new computer with a static IP address. On the new computer, do the same as above, but click on Properties instead of Details.

Scroll down to Internet Protocol Version 4 (TCP/IPv4) and highlight it.
Click Properties.
Change the radio button to "Use the following IP address".

The IP address must be unique - it has to be different from the ones used by the other computers on the network (so you'll have to do the Details thing on all the other computers). The IP address will be of the form x.x.x.x (e.g. 192.168.0.1), and it's usually set up so only the last number varies on a network. Find a free last number and assign it to the new computer.

Subnet mask should be the same as on the other computers. Usually it's 255.255.255.0

Default gateway should be the same as on the other computers.

DNS (if you're using it) should be the same as on the other computers.

Generally WINS isn't needed if your computers are auto-negotiating amongst themselves via netbios, but you should check on the working computers to see if it's been set (from the TCP/IP v4 properties page, Advanced -> WINS).
 
Solution

aidll 1974A

Reputable
Jan 14, 2016
4
0
4,510