If your Auction Flex primary computer and workstation computers won't connect, can't see each other on the network, or you're seeing a credential prompt or error message when mapping the network drive, work through this article. Start with the basic checklist — it resolves most connection issues — then jump to the section that matches your specific error.
Before You Start: Basic Network Checklist
Run through these checks before troubleshooting a specific error message. Most connection issues trace back to one of the items below.
Note: Both your primary computer and every workstation computer must be connected to the same local network for any of these steps to work.
1. Check Network & Sharing Settings
On both computers, open Network and Sharing Center. Confirm both are connected to the same network.
Click Advanced Sharing Settings, then expand all three sections: Private, Public, and All Networks. Make sure the following are set:
Network Discovery — On
File and Printer Sharing — On
Public Folder Sharing — On
Password Protected Sharing — Off
2. Confirm the AuctionFlex Folder Has Read/Write Access
Find the AuctionFlex folder on your C: drive.
Right-click the folder, choose Show more options, then select Give access to > Specific people.
Confirm the AuctionFlex folder is shared with Everyone, and that Everyone has both Read and Write permissions.
3. Set Both Computers' Network Type to Private
Both your primary computer and your workstation(s) need to use a Private network profile — not Public.
On Windows 11:
Open the Start Menu and click Settings (the gear icon).
Click Network & internet.
Select Wi-Fi or Ethernet, depending on how you connect.
Click your active connection, or its Properties.
Find Network profile type and select Private.
On Windows 10:
Open Settings from the Start menu.
Select Network & Internet.
Choose Ethernet or Wi-Fi from the left pane, then click your connected network's name.
Find Network profile and switch it from Public to Private.
4. Check Your Antivirus Software
Third-party antivirus software can block your Auction Flex computers from communicating with each other. If you use one of the programs below, add an exception for Auction Flex:
Bitdefender
Norton 360
Malwarebytes
McAfee
Avast
Auction Flex and HiBid aren't responsible for issues caused by antivirus software, but adding an exception usually resolves the connection problem.
5. Confirm Your AuctionFlex Version
If you're running AuctionFlex version 9.19 or older, you'll also need to confirm SMB2 is enabled in the Windows Registry on your primary computer. See Update Registry Settings for SMB2 and Security Signing further down in this article for the steps.
6. Run a Quick Connectivity Test
On the workstation, open File Explorer and go to:
\\NameOfYourPrimaryComputer\auctionflex\. If you're prompted for credentials, try admin / admin, admin / nopassword, or leave the password blank.Open Command Prompt and run
ping NameOfYourPrimaryComputer. If that doesn't work, try the IP address instead — for example,ping 192.168.1.15.
Note: Complete this checklist fully before moving on to a specific error below. Network Discovery must be on, and both computers must be set to Private.
Primary Computer Not Visible on the Network
If your primary computer doesn't show up when you browse to Network in File Explorer on the workstation, follow these steps.
Find Your Network Adapter's IP Address
Click Start, type
CMD, and open Command Prompt.Type
ipconfigand press Enter. This lists every network adapter on your computer, even ones you aren't currently using.Find your Ethernet adapter and note its IPv4 Address.
If you only connect over Wi-Fi: Auction Flex isn't supported over a wireless connection. Note your Wireless LAN adapter's IPv4 address for now, but plan to switch to a wired Ethernet connection.
Run a Ping Test
On the workstation, open Command Prompt and run
ping NameOfYourPrimaryComputer. If the name doesn't work, try the IP address instead.Also try it in reverse: from the primary computer, ping the workstation.
If either ping fails, confirm both computers are set to a Private network type, then try again.
Note: If every ping fails — both by name and by IP address, in both directions — the issue is most likely with your physical network hardware (cables, router, switch, or Ethernet ports), not your computer's settings.
Credential Prompt or "Network Error 1208"
If Password Protected Sharing is off but you're still prompted for credentials, try the steps below.
If you sign in with a Microsoft account: a Windows Hello policy may be blocking the connection. Go to Settings > Accounts > Sign-in options > Additional settings and turn off "only allow Windows Hello sign-in for Microsoft accounts on this device."
Credentials to try at the prompt: admin/admin, admin/nopassword, admin/blank. If none work, clear the username field and enter ComputerName\username instead (e.g. Laptop_Primary\admin).
"A Specified Logon Session Does Not Exist"
Clear the username field completely, enter ComputerName\username (e.g. Laptop_Primary\admin), and try admin, nopassword, or blank for the password. Once in, confirm the Everyone group has Read and Write access on the share.
Guest Access Blocked by Security Policy
Common on Windows 11. On the workstation: press Win + R, type regedit, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters, add a new DWORD named AllowInsecureGuestAuth set to 1, then restart.
"The Specified Network Name Is No Longer Available"
Fix 1: Control Panel > Programs > Turn Windows features on or off > check SMB 1.0/CIFS File Sharing Support > restart.
Fix 2: Open services.msc and confirm Server and Workstation services are Running/Automatic on the workstation (and the primary, if the error continues).
"An Extended Error Has Occurred"
Fix 1 (try first): Temporarily disable firewall/antivirus to test; confirm network type is Private.
Fix 2 — Update Registry Settings for SMB2 and Security Signing (both computers, primary first):
On the primary:
regedit>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters> set/create DWORDSMB2=1.On the workstation: same path under
LanmanWorkstation\Parameters> setEnableSecuritySignature=1, then create a new DWORDRequireSecuritySignature=0.
"OLE IDispatch Exception Code 0"
Fix 1 (try first): Restart, or sign out and back in.
Fix 2: Map using the IP address instead of the computer name — e.g. \\192.168.1.15\auctionflex, or net use Z: \\192.168.1.15\auctionflex from an elevated Command Prompt.
Fix 3: Temporarily disable firewall/antivirus to test; confirm network type is Private.