Tag Info

New answers tagged

0

This seems to be more a work-around than an answer: on a stand-alone Win8.1 Enterprise workstation, an actual user account needs to be added to the share permissions, as Win8.1 seems to ignore what members are in the local Administrators group. Once the computer is joined to a domain, the user account can be swapped with the local Administrators group in ...


0

\\StandAlone\CShare is that an actual share? I would expect you to be browsing to \\StandAlone\C$ instead and then putting in StandAlone\createdadminlevellocalaccount as the username and its password. The local administrator account on a Windows 8 workstation will be disabled, so don't try to use StandAlone\administrator as the account to access the C$ ...


0

Which local admin credentials are you using? You will need to use the user account on the Domain computer, not the Standalone. Also, did you explicitly grant it the local administrator access via the permissions setting on the share itself (not NTFS perms, the share perms)? You will need to do that too. If you still cannot access, can you post a screenshot ...


-2

The same problem. It happend when a I lost my network connection to NAS. (reason was different time, Thecus vs. MS Server) Try to restart servicees in Cobian menu Menu/Tools/Options/Global/Button-ServiceAndAplicationCOntrol stop/start - shadow copy - Mains systém services.


0

The problem was the windows firewall (Server 08). For some reason he was locking door 3128 by internal NIC. I created an inbound rule and resolved.


0

Windows systems automatically shares the root of every hard drive on the machine as $ (so you get C$, D$, A$, etc). These shared are secured in such a way that only members of the local administrative group can access them. Considering your case I have 3 suggestions for you, You can temporarily unshared these administrative shares. That is, open computer ...


1

My client is asking the obvious questions and so far I have—embarrassingly—not been able to provide an answer. So you state you had to push the server to reboot manually. Quite hard in fact. And all signs point to the system running smoothly when you RDP’ed in, correct? But yet still the system choked for no apparent reason overnight. First, you ...


0

Just a few things to glance at, (probably mostly blind alleys, but hey, they're ideas!) Older windows (2003, xp et al) used an older version of the SMB protocol; you may want to check that your Windows 7 clients are setup to use the newer protocol (Windows 7 supports SMB 2, and Windows 8 supports SMB-3, which is the highest level that 2008 serves). If you ...


0

Harddisk performance also can affect the Copy process. Since the copy process mainly depends on the read and write speed of the source and destination disk kindly check performance of the disk including the bad sectors in disks.


0

Support came from one of the Samba developers. It seems like this problem was caused by my current IBM GPFS (network filesystem) configuration and not Samba. Resolving the problem The following 2 workarounds are available: A) Apply "special" settings: For GPFS 1.3.1.0 or higher -> enable GPFS setting for file rename using SMB2 access: Using SSH, ...


0

I created a new Dword: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanworkstation\Parameters\DirectoryCacheLifetime and set to 0 It worked for me after a reboot.


0

This error message will occur in case if the file path is not accessible by the System.IO namespace.Library. Try fetching the file path using the library Delimon.Win32.IO and this will overcome your issue. You can download the library from Microsoft.


0

If SEP is installed on local client, just make sure SEP firewall is not blocking any connection. Personally I have never heard about this issue. To disable SEP go to Start --> Run --> smc -stop (To stop the SEP service ) Start --> Run --> smc -start (To Start the SEP service)


2

If you are using a startup script, you need to give the Domain Computers group permission in the share and NTFS permissions. Startup scripts run in the context of the SYSTEM account. Your tests that you've run manually will run in the context of whatever the logged on user is. You can test this manually by running psexec -s cmd which will launch an ...


-1

Was this application coded for Windows XP? We experienced compatibility issues with a software we use on XP after we upgraded machines to Win 7. After a newer version everything was fine. Maybe that's what's happening with your application.


1

To remove a connection to a PC where it was made to access a folder and the User was cached (ie remains active) must be rigorously used the following procedure (step-by-step): access the folder with User / Password 2 Close all windows explorer of the machine 3 Open the command prompt 4 Execute the command Net use * /del * Should be done in ...


1

Without knowing anything about your VPN server it's difficult to make good statements about the cause. I suspect that you've got something filtering the traffic between your VPN clients and the server computers. I'd start by installing "Network Monitor" (or Wireshark, or your favorite sniffer) on one of the server computers and capturing traffic while a ...


1

You can use the command line to map a network drive and supply credentials there like so: net use drive_letter: \\HostName\ShareName /user:DomainName\UserName


0

Looks like you have a local account with same username and password on your home and web machines, and that account doesn't have have access to this share.


0

After several hours figuring out what might work, the following bit different solution worked for me: Create a new Windows User with normal user rights (no admin rights) Login with this user account and map your network drive you want to use Logout and Login in your normal user account. Now edit the apache service to run under the created user privileges ...


-1

I resolved it by right clicking on the task, then Edit task, Advanced, Run the task with another user. Then I put username, domain, and password again, my Cobian started with this error when I changed the user password, before that it was ok.


2

@Chopper3 already mentioned that VMWare Server is dead and should not be used anymore at all. My answer assumes that you use something like ESXi, KVM or Xen instead. In this case, using a VM as a PXE server is not a problem and can be done easily, there is no difference to a physical machine in that regard. It's also possible to configure a system where the ...



Top 50 recent answers are included