AFTER REBOOT “Set Network Location” required.
Background:
1. Restaurant environment.
2. Two desktop “terminals” Microsoft Windows 7 Embedded, 64-bit Service Pack 1 (build 7601)
3. Cox business Router Switch is the “Technicolor-cga4131” both Terminals directly wired to the Router Switch.
4. Bitdefender MAV.
5. All Patches current.
6. Terminal 1 – (for my purposes) static IP set on the local adapter.
6.a. Terminal 1 hosts the POS software DB.
7. Terminal 2 – Dynamic IP, needs to connect the POS DB on Terminal 1.
8. Both Terminals local adapters DNS set to 8.8.8.8 and 8.8.4.4
9. IPV6 disabled on both terminals
10. On each Terminal there are 2 administrative profiles, 1 password required, which then automatically launches the point of sale software. The other profile no-password required, and no access to the point of sale software.
FYI - I did pick up some batteries as a just-in-case “it’s the CMOS batteries.” Yet to be installed. I'll be dropping those in today within the next hour or two.
Problem:
After a each reboot the “Set Network Location” widow pops up. EACH TIME!
This causes a break on Terminal 2 being able to automatically connect to Terminal 1's DB, as the Network setup has to be performed. Afterwhich Terminal 2 requires the use of Microsoft SQL Server Manager to properly connect to Terminal 1 where the Point of Sale software's hosted DB is located.
Guru’s watcha got for me?
Respectfully,
Vincent Mills.
1. Restaurant environment.
2. Two desktop “terminals” Microsoft Windows 7 Embedded, 64-bit Service Pack 1 (build 7601)
3. Cox business Router Switch is the “Technicolor-cga4131” both Terminals directly wired to the Router Switch.
4. Bitdefender MAV.
5. All Patches current.
6. Terminal 1 – (for my purposes) static IP set on the local adapter.
6.a. Terminal 1 hosts the POS software DB.
7. Terminal 2 – Dynamic IP, needs to connect the POS DB on Terminal 1.
8. Both Terminals local adapters DNS set to 8.8.8.8 and 8.8.4.4
9. IPV6 disabled on both terminals
10. On each Terminal there are 2 administrative profiles, 1 password required, which then automatically launches the point of sale software. The other profile no-password required, and no access to the point of sale software.
FYI - I did pick up some batteries as a just-in-case “it’s the CMOS batteries.” Yet to be installed. I'll be dropping those in today within the next hour or two.
Problem:
After a each reboot the “Set Network Location” widow pops up. EACH TIME!
This causes a break on Terminal 2 being able to automatically connect to Terminal 1's DB, as the Network setup has to be performed. Afterwhich Terminal 2 requires the use of Microsoft SQL Server Manager to properly connect to Terminal 1 where the Point of Sale software's hosted DB is located.
Guru’s watcha got for me?
Respectfully,
Vincent Mills.
Try setting the service "Network Location Awareness" to delayed start and test. HTH
Many of the newer routers really hate it when you set a static ip on a workstation. Instead, they want you to login to the router's web interface and reserve the address you want using the mac address of the PC's nic.
Are the network card drivers up to date?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have you tried to set network location to work and then rebooted and still you get issues?
Ensure in windows firewall if network discovery is on for all profiles