Mapped drives "stuck" on Windows 7 after disconnecting them..solutions?

Question

I am new to kubernetes and istio. On GKE, I have created ingress-gateway and two virtual services. The first one is frontend-gateway that routes to hipstershop and the second one is dummyservice which route to my hello world server. But when I call with

curl -v http://35.223.232.224/dummy

, it shows Cannot GET /dummy error.I'm sure my dummyservice is working since I have tested with Loadbalancer external IP.But I can call to hipstershop with http://ingress_ip. Can someone please help me?

Here is my istio config file

apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: frontend-gateway
spec:
  selector:
    istio: ingressgateway # use Istio default gateway implementation
  servers:
  - port:
      number: 80
      name: http
      protocol: HTTP
    hosts:
    - "*"
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: dummy-ingress
spec:
  hosts:
  - "*"
  gateways:
  - frontend-gateway                
  http:
  - match:
    - uri:
        exact: /dummy
    route:
    - destination:
        host: dummyservice            
        port:
          number: 80

---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: dummy-ingress2
spec:
  hosts:
  - "*"
  gateways:
  - frontend-gateway                
  http:
  - match:
    - uri:
        exact: /dummy2
    route:
    - destination:
        host: dummyservice            
        port:
          number: 80

---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: frontend-ingress
spec:
  hosts:
  - "*"
  gateways:
  - frontend-gateway
  http:
  - route:
    - destination:
        host: frontend
        port:
          number: 80

Solution 1

According to this site user Zach H's method, I went to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\ ,right-click on the drive mapping key (the "ghost" drive, if Z: is mapped to \\Server\folder then it would appear as ##Server#folder), deleted it ,and then restarted explorer.exe and the disconnected drive disappeared.

This solution still needs restarting explorer session ONCE. After that, disconnecting the share via the context menu the icon would disappear in Explorer.

Solution 2

Restart the "explorer.exe" process;

1. Right-click on the taskbar and select "Start Task Manager"
2. Go to the "processes" tab
3. find and end the "explorer.exe" task, dont close the task manager yet, your task bar should disappear
4. Click on "File" and select "New Task (Run...)"
5. Type in "explorer" without quotes and click "OK", the taskbar should return

Open "My Computer" or "Computer" again and the stuck mapped drive should now be gone.

Solution 3

Well, the drive letter is still clearly mapped and if getting rid of that is what you're trying to do, you could jump in the command prompt and go (where x: is the drive letter)

net use x: /delete

This should get rid of it. When you're disconnecting the share in the context menu, it should be unmapping it as well but I've seen this disconnect between the GUI and what Windows is actually doing. The above can be easily scripted for your users, and with a bit of VBscript you could potentially have them enter in the Drive letter they wish to have disconnected.

This is not ideal but I know I've seen some weirdness with Windows hanging onto Drive letters even though they should have been unmapped.

Comments

[ckhan]

What does net use say when the drive is disconnected but Explorer still has the ghost?

[Karu]

Nothing, it acts as though the drive is not connected.

[Karu]

No good - the NET USE list is empty after doing the context menu disconnect, the ghost drive is still there, and it won't let me remap the letter to something else.

[Will]

How do you map the drives in the first place? By script, command, group policy? Let's see if we can't track down what's going on here.

[Karu]

In this case, just by going through Explorer. Plugging in a UNC location, and then clicking "Map network drive" on the top bar.

[Johnny5]

Hmm this worked for me. Another thing I might have done is renamed the drive letters for the mapped drives. If the drive letters could conceivably be used by thumb drives, or other more transient devices, they might stick around. After mapping some drives near the end of the alphabet my stubborn "stuck" drives went away. For example my company uses the "G" drive which is close to the amount of physical devices I might have connected up at any given time. I changed it to the "M" drive and used the steps above, the problem is gone for me.

[DavidPostill]

Please quote the essential parts of the answer from the reference link(s), as the answer can become invalid if the linked page(s) change.

[Rob]

This solution just deletes the registry data as w10 mentioned above.

[Dokbua]

Yep, fixed it for me too. Imagine you still have to kill the windows explorer to fix things like this in 2020. :(