Free word 10 for mac. To remove the update installer, first drag the Microsoft Office 2011 14.5.5 Update volume to the Trash, and then drag the file that you downloaded to the Trash.

1. Wan Miniport Network Adapter Drivers For Mac Windows 10
2. Wan Miniport Network Adapter Drivers For Mac
3. Wan Miniport Ip Driver

NDISSTATUS MiniportWanSend( IN NDISHANDLE MiniportAdapterContext, IN NDISHANDLE NdisLinkHandle, IN PNDISWANPACKET WanPacket ); Parameters MiniportAdapterContext Specifies the handle, originally input to, identifying the miniport and WAN network adapter it controls. NdisLinkHandle Specifies the handle to a miniport-allocated context area for this link. The driver previously returned this handle in an NDISMACLINEUP indication when the link was established.

WanPacket Points to an NDISWANPACKET structure, specifying the data to be transmitted. This structure specifies the virtual range for a buffer with guaranteed padding at the beginning and end. The driver can manipulate the data in this buffer in any way. Return Values MiniportWanSend can return one of the following: NDISSTATUSSUCCESS The driver (or its network adapter) has accepted the packet data for transmission, so MiniportWanSend is returning the packet.

NDISSTATUSPENDING The driver will complete the packet asynchronously with a call to. NDISSTATUSFAILURE or NDISSTATUSXXX The given packet was invalid or unacceptable to the network adapter. Comments When MiniportWanSend is called, ownership of both the packet descriptor and the packet data is transferred to the driver until it completes the given packet, either synchronously or asynchronously. If MiniportWanSend returns a status other than NDISSTATUSPENDING, the request is considered complete and ownership of the packet immediately reverts to the initiator of the send request. If MiniportWanSend returns NDISSTATUSPENDING, the miniport subsequently must call NdisMWanSendComplete with the packet to indicate completion of the transmit request. MiniportWanSend can use both the MacReservedx and WanPacketQueue areas within the NDISWANPACKET structure.

However, the miniport cannot access the ProtocolReservedx members. Any NDIS intermediate driver that binds itself to an underlying WAN miniport is responsible for providing a fresh NDISWANPACKET structure to the underlying driver's MiniportWanSend function. Before such an intermediate driver calls, it must repackage the send packet given to its MiniportWanSend function so the underlying driver will have MacReservedx and WanPacketQueue areas of its own to use. The available header padding within a given packet can be calculated as ( CurrentBuffer - StartBuffer), the available tail padding as ( EndBuffer - ( CurrentBuffer + CurrentLength)). The header and tail padding is guaranteed to be at least the length that the miniport requested in response to a preceding OIDWANGETINFO query. The header and/or tail padding for any packet given to MiniportWanSend can be more than the length that was requested. MiniportWanSend can neither return NDISSTATUSRESOURCES for an input packet nor call.

Instead, the miniport must queue incoming send packets internally for subsequent transmission. The miniport controls how many packets NDIS will submit to MiniportWanSend when the network adapter driver sets the SendWindow value in the driver's NDISMACLINEUP indication to establish the given link. NDISWAN uses this value as an upper bound on uncompleted sends submitted to MiniportWanSend, so the miniport's internal queue cannot be overrun, and the miniport can adjust the SendWindow dynamically with subsequent line-up indications for established links. If the miniport set the SendWindow to zero when it called with a particular line-up indication, NDISWAN uses the MaxTransmit value that the driver originally set in response to the OIDWANGETINFO query as its limit on submitted but uncompleted send packets. Each packet passed to MiniportWanSend is set up according to one of the flags that the miniport set in the FramingBits member in response to the OIDWANGETINFO query.

It will contain simple HDLC PPP framing if the driver claimed to support PPP. For SLIP or RAS framing, such a packet contains only the data portion with no framing whatsoever. A WAN driver cannot manage software loopback or promiscuous mode loopback internally. NDISWAN supplies this loopback support for WAN drivers. MiniportWanSend can be pre-empted by an interrupt.

Windows network stack uses “miniports” to handle different layers of the network. These can sometimes “break” and cause VPN and possibly other network level services to not work properly. Usually you can tell a miniport is not working when it has an exclamation sign icon next to it in the device manager. (The miniports are typically hidden too, so if they aren’t broken, they won’t show up at all.) To me, this problem manifested when I was creating a VPN, and despite choosing connection over network, the connection would try to dial the modem.

All it takes to fix them is uninstalling and re-installing the non-working miniport, but unfortunately there is no easy way to do it. Miniports can’t be deleted/uninstalled, and their drivers are hidden from the user, so even re-installing them isn’t easy. Trying to avoid OS reinstall, I hunted around for a while and could not find a decent guide to fixing the problem. There are a lot of outdated posts that no longer work in Windows 7 (and probably Vista), and some that are just plain wrong. Having read number of forum posts, some KBs, and a bit of intuition and guessing, I’ve pieced together the following guide to uninstall and re-install the network miniports: Uninstall the non-working miniports To do this, DO NOT edit the registries. There are number of other registry keys that depend on the miniports being present, and it is super easy to completely break the network stack, to a point where the base network card driver won’t work. (If you did this already, let’s hope your system has restore points – you can restore to previous snapshot and try doing it the non-registry way outlined there.) When doing this, take a note of the miniports that you are removing, you’ll need to know this later when reinstalling.

Wan Miniport Network Adapter Drivers For Mac Windows 10

So, to remove each non-working miniport, do the following:. Right click on the non-working miniport, choose “Update Driver”.

Wan Miniport Network Adapter Drivers For Mac

Choose “Browse my computer”. In the next window, choose “Let me pick driver from a list”. Uncheck “Show compatible hardware”. From the “Manufacturer” list, choose “Microsoft”, and from the “Network Adapter” list, choose “MAC Bridge Miniport”.

(It can be any device the user is allowed to uninstall.). Back in the device manager, delete the device that just turned into the “MAC Bridge Miniport” device. Once done removing the bad miniports, reboot.

Wan Miniport Ip Driver

Don’t skip this, it’s important. Otherwise there is a change things will go bad again. Reinstall the miniports This is the fun part. You’ll need to do a few extra steps, as the miniport drivers aren’t meant to be installed by users and are not visible. To avoid editing.inf files (which in lot of cases are protected and not easily editable), we’ll do it the long way. Get ahold of current devcon.exe.

32-bit version won’t work on 64-bit systems. It runs, but won’t do what it needs to. Old (XP/2000) versions don’t work well wither. The easiest way to do this is to follow the steps outlined in “” on Microsoft’s TechNet wiki.

(It involved getting an ISO image of a developer CD and extracting the devcon.exe file out of there.). Go to command prompt, go to the directory where you extracted devcon.exe. For each miniport that you have previously uninstalled, execute the command outlined below. DO NOT run all of them or run the command twice, as that will create second version of the existing miniport, which can cause problems again. If running the command reports “driver install” failure, don’t pay much attention to it, it usually does. The only problem is when it complains about the inf file missing, or a missing class (in which case you most likely made a typo in the last part of the command). IKEv2: devcon.exe install c: Windows inf netavpna.inf MSAgileVpnMiniport.

IP: devcon.exe install c: Windows inf netrasa.inf MSNdisWanIp. IPv6: devcon.exe install c: Windows inf netrasa.inf MSNdisWanIpv6.

Network Monitor: devcon.exe install c: Windows inf netrasa.inf MSNdisWanBh. L2TP: devcon.exe install c: Windows inf netrasa.inf MSL2tpMiniport. PPPoE: devcon.exe install c: Windows inf netrasa.inf MSPppoeMiniport. PPTP: devcon.exe install c: Windows inf netrasa.inf MSPptpMiniport. SSTP: devcon.exe install c: Windows inf netsstpa.inf MSSstpMiniport Once done, reboot.

Again, this is necessary. You can go to device manager and scan for new devices and some of the miniports will show up, but some will have wrong names and won’t work properly without a reboot. That’s it, you should have working miniports again. If you had a VPN connection created while the miniports were still bad, you will most likely need to delete it, and re-create it. Otherwise, things should be back to normal. Tags Feedback is always welcome.

Feel free to, or edit on GitHub and submit a push request.