• 2221-45 Xentry Open Shell Xdos.2016.05

（2221-45） No access authorization for XENTRY Diagnostic was found on the server. You must contact the User Help Disk. How to install MB Star Xentry Openshell on Windows 10 Xentry Openshell XDOS Windows 10 installation tips and guides for newbies: – XDOS Windows 10 Startkey not valid – XDOS Windows 10 security settings – No Windows 7 VMware on Windows 10 – Windows 10 Ad-Hoc Fix.

Post supplies Mercedes-Benz Xentry.OpenShell.XDOS 2019.03 (19.3.6) free download source and reliable source.Newest Xentry V2019.03 is for Mercedes Star diagnosis, DAS XENTRY V2019.03 software is available with hdd or ssd version. 2019.03 Mercedes star diagnosis with EPC,WIS,Vediam, Dtc, Starfinder win 7 software with new mercedes starfinder online software and mercedes das xentry 2019.03.V2019.03 Xentry download:Link 1.

No VMware no win 7 image. It working on Windows 10 64bit professional. The same Ad-hoc like on Win 7. WEP is not problem.

You have to manually set new connection with name Road24h/WEP/key uncheck automatic connection or something like this /I forgot/ then use solution which posted Mr.Rocinante and allow Ad-hoc thats all. This working for me. You can see on picture in my post how is connected SDConnect. I tested it on 3 cars and no problem with Ad-hoc. I reinstall full system now because I found one larger hdd. Note down the SSID, security type, encryption type and the key of the ad-hoc network.Disconnect your connection to any wireless network and switch off/disable your wireless device.

Turn on/enable your wireless device but don’t connect to any network. (Thanks GK.)Click on the network icon in the taskbar.Click Open Network and Sharing Center Manage Wireless Networks Add.Click “Manually create a network profile”. (This may look silly but we really are going to create an infrastructure network now.)Enter the network name (SSID), security type, encryption type (if any) and the key that you noted in step 1.Uncheck both checkboxes (“Start this connection automatically” and “Connect even if the network is not broadcasting”.) Note that you cannot have the connection start automatically. If you try to have it checked, step 10 will fail. A different way to start it automatically during system boot is described below.Click Next Close. Your connection must appear in the list with the icon suggesting infrastructure (two big screens connected to a tube). Don’t worry about it.Click Start, type in “cmd” in the search box, press Enter.In the Command Prompt, type in “netsh wlan set profileparameter name=NetworkName ConnectionType=IBSS”, exactly as shown, without quotes, except you must substitute NetworkName with the SSID (network name) of your ad-hoc network.If everything went well, you’ll see that the icon has now changed to an ad-hoc icon (three small screens connected to each other) in the Manage Wireless Networks window.Turn on/enable your wireless device, and try connecting to the Ad-hoc network.

2221-45 Xentry Open Shell Xdos.2016.05

You will notice that you no longer need to enter the network key. Click Start point to All Programs right-click Startup click Open. (You may choose Open All Users instead if you prefer).Right-click an empty space and click New Shortcut.Type in “netsh wlan connect NetworkName”.

Once again, NetworkName must be substituted with the SSID of your ad-hoc network.Click Next and enter a fancy name such as “Connect to NetworkName” or something like that.Click Finish and you’re done. This shortcut will run when Windows starts up, giving you a very brief flash of the black command window, followed by your computer connecting to the ad-hoc network if it is available. Tip: You can also pin the shortcut in your taskbar or copy it to the desktop to easily connect to the network any time you want.