01:00.0 Ethernet controller: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless
Wifi will randomly disconnect as it seems the network manager will restart or crash. Internet is usable, however this interrupt makes it hard to complete larger projects. I updated to Fedora 27, but then the wifi refused to connect at all (on my stable Fedora 25 kernel it connects on startup without fail, only to break later, normally I restart to fix the connectivity issue, but this has been getting old.) Maybe there's a Marvell Linux Kernel Driver I'm missing? Or maybe something to do with akmod wl, etc.
Appreciate any suggestions.
Maybe this could help?
https://ask.fedoraproject.org/t/howto-fix-surface-pro-3-wifi-issues/2273
It says to add this rule in the following location:
/etc/udev/rules.d/81-surfacepro3_wifi.rules
SUBSYSTEM=="net", KERNEL=="wlp1s0", RUN+="/usr/sbin/iw dev $name set power_save off"
Related
USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
The problem was described here - https://communities.vmware.com/thread/612551
but anyone has no answer for it.
Generally, the problem is like so:
launch vm
connect usb stick or usb phone cable
vm freezes
it is not possible to terminate vmware-vmx.exe process (even as a SYSTEM user with highest privs).
The issue occurs on vmware workstation 14 & 15 on Windows 10 Pro Build 1903
Also tried disabling windows defender (maybe some strange scan policy) but no results.
Tried also to change almost every setting in workstation but no results...
please help
I was facing exactly the same issue and I have finally found the solution.
Update to VMWare Workstation version 15.5. Update the VM Tools in the Guest operating System, and it works!! Tried with Android Devices, in USB Tethering Mode also.
I had this problem previously (but didn't know the cause) and had to reformat my machine to eliminate the problem. Now I a pretty sure I know the cause:
I have both a wired and wireless internet connection. If I unplug my wired connection I cannot use SSMS to connect (forcibly closed by the remote host) to my Azure database (even though the wireless connection to the internet is fine). I can still connect using sqlcmd over the wireless connection.
By simply plugging/unplugging the Ethernet cable I have confirmed that this is the problem. I have checked my firewall rule for 1433 and it is supposed to be interface independent.
I've tried turning Firewall off completely and forcing TCP in the SQL connection properties.
Has anyone else found this to be a problem and found a solution? Is there a way to specifically tell SSMS to communicate over a specific network interface? Otherwise, I will have to reformat my machine again (and never use a wired Ethernet cable, since it worked fine before I ever plugged in an Ethernet cable) to eliminate this problem.
My guess is that you may be fighting (unbeknownst to you) network protocols.
https://www.connectionstrings.com/define-sql-server-network-protocol/
in the above URL, find the section labeled "Network protocol codes"
"Network Library=dbmssocn"
The above network-library is the 'tcp' one..and is the most common (in 2019) version. (I started sql-server when named-pipes was the biggest player and learned the hard-way about network-protocols ! )
That is how you "force" a certain network protocol in a connection string.
You can also set this value in Sql Server Management Studio.
See here:
https://kb.intermedia.net/article/1893
Find the sentence
"2. If it does not work with default settings, go to Options > Connection Properties tab. And choose TCP/IP in the drop down menu for Network Protocol."
Try experimenting with that.
APPEND:
Your first two screen shots are really hard to read. You have alot of blue space. I'd suggest making your ssms window smaller, then taking the screen shot.
Are you using these credentials naming style?
myazuresqlservername.database.windows.net,1433
MyUserName#myazuresqlservername
Could it be this??
Impossible to connect to Azure SQL database with ipv6 address due to recent forced update from v11 to v12
Turns out this doesn't seem to be a problem with SSMS at all. Although Windows responded that I had the latest Network Driver, I discovered that the manufacturer had a new driver and that seems to have solved the problem.
http://support.killernetworking.com/knowledge-base/clean-install-killer-control-center/
Product Type Killer(R) Wireless-AC 1550 Wireless Network Adapter (9260NGW) 160MHz
Product Type Killer E2500 Gigabit Ethernet Controller
My Hardware:
Operating System: Windows 10 Pro 64-bit (10.0, Build 17763) (17763.rs5_release.180914-1434)
Language: English (Regional Setting: English)
System Manufacturer: Alienware
BIOS: 1.6.5 (type: UEFI)
So I am connecting to my work computer from home and the Remote Desktop Connection app is annoyingly slow.
I pinged my work pc from my computer and it returned at a reasonable time of 50ms~ with 0 loss. I then attempted to ping my home IP from the RDP session and it timed out every time. Not sure if this might help anyone come to a conclusion but hopefully it does. Note I am also using it in conjunction with Cisco AnyConnect Secure Mobility Client if that helps at all. Work is Windows 7 and Home is Windows 8
I attempted switching off my home pc's firewall but that did nothing.
Any assistance would be great, surely a setting in the RDP file might make it run a little smoother.
I'll edit this post with further attempts at fixes below
Did three things and now RDP is running screaming fast:
Change RDP settings:
Run the RDP session and connect to the remote machine
Find mstcsc.exe in the Task Manager and and set priority to Realtime
I installed Ubuntu server XRDP. Went through Windows and terribly slowed down. I solved this problem. In the /etc/xrdp/xrdp.ini file, change crypt_level=high to crypt_level=None
Our remote chain is Citrix then RDP, target machine is Win 10.
I solved this issue by changing the mouse pointer scheme to None and disabling the pointer shadow.
In Windows 10. Go to Display Settings >> Scale and Layout >> Set the custom scale to 120 [you may need to experiment, try 110 - 150]
After that log in to your Remote Desktop, it should adjust the resolution and scaling factors.
It gave me a faster experience. If you need more then follow the answer of Mr. B
First of all, there's a similar thread on OpenQNX posted years ago but the solutions don't really apply for me.
Having said that, I want to create an OS image of QNX 6.6.0 to put on a Compact Flash card. This card is plugged in an USB adapter which is connected to my host pc. I'm running Neutrino in a VM (VMware/VirtualBox) for which I enabled USB support. Generally, the adapter works fine under Win (current host) and Linux.
The (apparently out-dated) tutorial I was following stated to search for devices named umass* or hd* after connecting the USB adapter. But there aren't any (except for hd0).
See also "ls /dev" screenshot.
The processes devb-umass and io-usb are running. So I expect that the adapter is detected automatically.
Any suggestions what went wrong?
OK, it seems that I had to restart the usb driver 'devb-umass' (several times). When the card reader is already plugged-in during the booting the driver will not detect it autoamtically. Thus one has to unplug and plug it in again after the devb-umass was getting re-started. It also might have been that the Host Controller Driver (HCD) was set to 'ohci' instead of 'ehci'.
Everything is working now as expected.
(Thanks Tim from the OpenQNX forum! ;) )
I have installed VMware-workstation-full-10.0.3-1895310 on windows 8.1. Although VMware brige protocol is enabled in my LAN adapter but still I am unable to add and switch VMNET0 to bridged mode.
It says "Cannot change network to bridged: There are no unbridged host network adapters"
So far I have tried the following things:
I have reinstalled it many times
I have restore default settings of virtual network editor
Have also checked that Vmware bridge protocol is enabled
Have checked that whether vmnetbridge service is running or not
have done almost everything present on forums
I had this same problem also. I also run Kaspersky AV, and tried bigapple99's suggestion and unticked Kaspersky Antivirus NDIS 6 filter. This made the NIC show up in the editor, but didn't fix the problem. I noticed I was running the editor as Administrator when it was showing up, so I tried running VMWare Workstation as Administrator too. It worked! I tried reticking the Kaspersky filter, and reopening VMWare Workstation as Administrator, and it still works :) Best of both works, I'll just Run as Administartor now.
I had the same problem after upgrading windows 10. "Repair" VMware workstation version fixed the problem. I'm using VMware Workstation 11.1.3.
It's wired in network editor the "Bridged To" showing nothing in the drop down list (at least it should show "Automatic"). Can you try to untick the Kaspersky Antivirus NDIS 6 filter in LAN property to see whether your NIC will show up in the editor?
I had the same problem today and I thought I'd come back to you since no one answered your post yet.
My problem was coming from Kaspersky AV.
Remove VMWare
Remove Kaspersky AV
Re-Install VMWare
Re-Install Kaspersky
Hope it'll be of some help.
Best,
Alex