Solve your Desktop PC or MAC issues for free...ABSOLUTELY FREE!: October 2014

Monday, October 27, 2014

What is the difference between workgroup & domain?

What is the difference between workgroup & domain?

Computers on a network can be part of a Homegroup, workgroup or a domain. The main difference between workgroups and domains is how resources on the network are managed. Computers on home networks are usually part of a workgroup, and computers on workplace networks are usually part of a domain.

In a workgroup:

· All computers are peers; no computer has control over another computer, only the shared resources can be accessed through network.

· Each computer has a set of user accounts. To use any computer in the workgroup, you must have an account on that computer and computers must be connected to a single source of network.

· There might be 20 or 40 or more computers in a work as it depends on the size of your work environment.

· All computers must be on the same local network or subnet.

In a domain:

· One or more computers might be servers. Network administrators use servers to control the security and permissions for all computers on the domain. This makes it easy to make changes because the changes are automatically made to all computers.

· If you have a user account on the domain, you can log on to any computer on the domain without needing an account on that computer.

· There can be hundreds or thousands of computers.

· The computers can be on different local networks.

#techsupport #technology #tech #itsupport #windows #computer #computerrepair #laptop #itsolutions #itservices #microsoft #cybersecurity #apple #technews #pc #it #computers #informationtechnology #software #laptoprepair #smallbusiness #datarecovery #support #business #techsupportlife #computertech #ittech #technologynews #laptops #msp #techtips #techie #macbookpro #pcrepair #surfacebook #surfacepro #computerservice #techgadgets #network #workfromhome #techmemes #technologynerd #manageditservices #itnerd #wifi #geeky #itconsulting #technerd #lenovo #itjob #techworld #virusremoval #pro #pcsupport #computerscience #blockchain #science #innovation #platform #education #future #cloud #edge #work #news #industry #security #tech #business #companies #information #solutions #time #internet #development #team #google #software #iot #trends

OTHER PC SHUTDOWN ISSUES & HINTS...

OTHER PC SHUTDOWN ISSUES & HINTS...

BIOS UPGRADE.
UNSIGNED DEVICE DRIVERS.
PROGRAMS HANG / BECOME UNRESPONSIVE. Sometimes programs don’t close down correctly, or hang for some other reason during the Windows shutdown process. This freezes up, or at least significantly delays, Windows shutdown.
QUICK-SWITCHING USER ACCOUNTS.
USING SHUTDOWN SCRIPTS & 802.1x AUTHENTICATION PROTOCOL. This combination can cause Windows to take in excess of 10 minutes to shutdown normally.
MISMATCHED RAM.
SHUTDOWN PROBLEMS IN WINDOWS 9x.

#techsupport #technology #tech #itsupport #windows #computer #computerrepair #laptop #itsolutions #itservices #microsoft #cybersecurity #apple #technews #pc #it #computers #informationtechnology #software #laptoprepair #smallbusiness #datarecovery #support #business #techsupportlife #computertech #ittech #technologynews #laptops #msp #techtips #techie #macbookpro #pcrepair #surfacebook #surfacepro #computerservice #techgadgets #network #workfromhome #techmemes #technologynerd #manageditservices #itnerd #wifi #geeky #itconsulting #technerd #lenovo #itjob #techworld #virusremoval #pro #pcsupport #computerscience #blockchain #science #innovation #platform #education #future #cloud #edge #work #news #industry #security #tech #business #companies #information #solutions #time #internet #development #team #google #software #iot #trends

PC POWER DOWN ISSUES

POWER DOWN ISSUES

“Power down issues” is quite distinctive from “shutdown issues.” The computer may not power down correctly. This is a different problem, and I encourage people reporting these issues to make a clear distinction in their labeling.

When Windows won’t power down automatically, the APM/NT Legacy Power Node may not be enabled. To enable this, right-click on the My Computer icon, click Properties | Hardware | Device Manager | View. Check the box labeled “Show Hidden Devices.” If it’s available on your computer, there will be a red X on the APM/NT Legacy Node. Try enabling it and see if this resolves the power down problem. However, other factors can sometimes interfere with correct power down functioning. In that case, consider the following steps:

If you change the default power settings in the BIOS, it can lead to a power down problem. Restoring all BIOS power settings to default will likely fix it.
Sometimes, not all appropriate Registry settings are made when you enable all the right power management settings in Windows.
Restore Power Option Settings to its default.
Try to replace you SMPS, the Power Supply in a desktop PC.

SHUTDOWN WORKS, BUT IT’S REALLY SLOW

SHUTDOWN WORKS, BUT IT’S REALLY SLOW

If it appears that Windows is not shutting down, give it some time. Some users report a minute or longer for shutdown to visibly start. Generally, this is a consequence of software that is running when shutdown is attempted. It also may have something to do with particular hardware. If you experience this problem, be sure to close all running programs before attempting shutdown and see if this solves your problem. If so, then you can determine, by trial and error, which program(s) are involved.
Solution: Got to Control Panel | Administrative Tools | Services, stop the Nvidia Driver Helper service. (You can also get this by launching SERVICES.MSC from a Run box.)
Disable Terminal Services, Please note that Terminal Services is required in Windows for running Remote Assistance, Fast User Switching, and Remote Desktop.
The Group Policy Editor has a security option to clear the page file at system shutdown. The same setting also forces the hibernation file to be wiped at shutdown. These processes take long enough that users may think that shutdown has hung. To change the setting, click Start | Run, type GPEDIT.MSC, click OK. Drill down to Computer Configuration | Windows Settings | Security Settings | Local Policies | Security Options. In the right pane, find “Shutdown: Clear virtual memory pagefile.” NOTE: Since someone actually has to have set this policy, the problem will be pretty rare, but is worth mentioning. The personal security app Privacy Eraser automatically enables “Clear virtual memory pagefile,” and, therefore, may be the cause of a slow shutdown.
You may also disable 'Page Files' by accessing System Properties | Advance | Settings | Advance | Change and then select the radio button 'No Page Files'
Run a Disk Clean up and select the check box Clear memory dump and error checking logs. It will help you to clear system event logs.
In a domain environment, don’t forget to check any logoff scripts you are pushing. These can be a source of slow or hanging shutdown processes. A related cause of slow shutdowns is offline synchronization of data, which is increasingly common with mobile computing, but is usually much more obvious to the end-user.

“STOP” ERROR MESSAGES AT SHUTDOWN

“STOP” ERROR MESSAGES AT SHUTDOWN

Some users, when attempting either to shutdown or restart Win XP & 7, get an error message similar to the following: STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE

Stop Messages literally means that Windows has stopped. (Which isn't the same as saying it has shutdown!) STOP messages are identified by an 8-digit hexadecimal number, but also commonly written in a shorthand notation; e.g., a STOP 0x0000000A may also be written Stop 0xA.)

Stop 0x9F and Stop 0x8E are two of the most common of these at shutdown, and generally point to a bad driver. Stop 0x7B on restarting means Windows lost access to the system partition or boot volume during the startup process, due to a bad device driver, boot sector virus, resource conflict, boot volume corruption.

Stop 0xC000021A can when on restart after a system administrator has modified permissions so that the SYSTEM account no longer has adequate permissions to access system files and folders.

You may follow these steps to resolve these problems:

Restart the computer. Press F8 during the restart and select “Last Known Good Configuration.” If you catch the problem when it first occurs (meaning you likely have installed only one or two drivers or new service), this will return you to a previous working condition. System Restore provides an alternate approach, especially if you need to go back further than the last known good configuration, and Device Manager provides a tool for rolling back to an earlier driver.

MISC. HARDWARE ISSUES ISSUES THAT MIGHT CAUSE AN UNEXPECTED SHUTDOWN OR RESTART.

MISC. HARDWARE ISSUES ISSUES THAT MIGHT CAUSE AN UNEXPECTED SHUTDOWN OR RESTART.

In addition to hardware issues mentioned by users, Here’s what they have reported:

CD-ROM DRIVE:
DVD-RW DRIVE:
MODEMS:

MOTHERBOARDS:

MOUSE:
VIDEO CARDS:
USB Devices.
USB: Keyboard or Mouse + Selective Suspend.
USB: Media Combo Digital Film Reader (USB).

SHUTDOWN HANGS ON “SAVING YOUR SETTINGS”

SHUTDOWN HANGS ON “SAVING YOUR SETTINGS”

During shutdown or reboot, Windows 7 may hang (stop responding) at the “Windows is Shutting down” screen. During such a hang, there is no response to Ctrl+Alt+Del; the mouse may or may not work. The problem may be intermittent.

This is a known bug in Windows XP and 7, for which Microsoft has few supported fixes. This is caused by some unresponsive programs or services running in computer memory in background. And the windows shutdown service is unable to close or end those programs that causes a unnecessary delay in shutdown or restart. You may remove some unwanted start up programs, remove autoruns and auto program updates and scheduled tasks etc. Also you should turn off Bit torrent clients etc.

Hardware Troubleshooting for Restart, Hang, No Display issue.

Hardware Troubleshooting for Restart, Hang, No Display issue.

Shutdown problems in Windows 7 can be caused by many factors, just like earlier versions of Windows. These included: a damaged exit sound file; incorrectly configured, damaged, or incompatible hardware; conflicting programs, or an incompatible CODEC, damaged, or conflicting device driver. Windows 7 shutdown issues mostly center around a very few issues, especially legacy hardware and software compatibility issues.

Currently, the leading cause of Windows 7 shutdown problems is hardware incompatibility, including driver issues. However, it is impossible to list every possible hardware or driver issue individually. My best advice is: Check all drivers for all hardware devices to ensure that they are the current best for Windows 7.

REBOOT INSTEAD OF SHUTDOWN

Most Win XP shutdown problems reported thus far have been that it reboots when shutdown is attempted. This may be a global symptom emerging from several distinct causes, because, by default, XP executes an automatic restart in the event of a system failure. But Thid rarely happens with Window 7.

Disabling the “restart on system failure” feature may permit the exact cause to be isolated: Right-click on My Computer, click Properties, click the Advanced tab. Under “Startup & Recovery,” click Settings. Under “System Failure,” uncheck the box in front of “Automatically restart.”

You may also check the following options in a Windows 7 based PC.

Whether or not APM is enabled.
USB Connections.
“Wake on” power settings Power-management settings.
Hidden “wake on” power settings.
Logitech Internet Keyboard can also cause this problem.
Logitech MouseWare 8.6. Windows reboots when shutdown is attempted. The software caused a BSOD with KBDCLASS.SYS. Removing the software solved the BSOD the problem.
Webstar DPX USB cable modem. In the one case known to me, the problem was solved by switching the modem’s connector from the USB 2.0 port on the motherboard to the USB 3.0 PCI card.

What is POST & JIG Test for Hardware?

What is POST & JIG Test for Hardware?

Power-on self test Abbreviated POST.

A set of diagnostic programs loaded from ROM before any attempt is made to load the operating system; designed to ensure that the major system components are present and operating. If a problem is found, the POST firmware displays an error message on the screen, sometimes with a diagnostic code number indicating the type of fault. The number of preamp channels is close to 60,000 including spare parts. It is highly desirable for each one to be tested to pass a simple "go - no go" test before being installed in the detector. There are a large number of channels so the manufacturer will be testing the preamps.

The test jig will have two functions:

1) to check that the preamp can hold voltages applied to the power rails, and that the supply currents drawn are within tolerance, and

2) to provide a fast electronic pulse that is applied to the input of the preamp and compare the output waveform to an expected shape. The tester is also designed to be operated conveniently and quickly.

Five go-no go test jigs will be built to test the upgraded Calorimeter preamplifiers. Two will be configured for Calorimeter preamp testing and three for ICD testing. Two of the test jigs will stay at Fermi lab, two will be sent to the preamp manufacturing vendor, and the ICD group will use one. The manufacturing vendor will automate the tests during the production run so the test jig was modified to accommodate their automation needs.

To conduct the tests, the operator will be required to place a preamp into a zero insertion force (ZIF) socket, push a button, and either read a voltage measurement from an externally connected meter or view an oscilloscope measurement of the rise and fall time. To conduct the undershoot/ overshoot test, they will generate a comparison curve based on units that pass the current, rise, and fall time tests.

The test jig consists of three printed circuit boards; the digital control, ZIF, and LED display boards. Modifications are currently being implemented which allow the vendor to measure the preamp power supply current. Each jig is calibrated with the aid of a written test procedure to insure thoroughness. A preamp power supply current simulation circuit has been designed for use during the calibration process to insure caliber.

Thursday, October 16, 2014

Ping an IP with Time Stamp.

Make a batch file to ping an IP with 60 sec time stamp.

@ echo off
:START
date/t && time/t >> C:\Users\User\Desktop\ping.txt && ping 115.187.12.115 -n 60 >> C:\Users\User\Desktop\ping.txt
goto START

It will show you the results in a text file on your desktop like this:

01:07 PM
Pinging 115.187.12.115 with 32 bytes of data:
Reply from 115.187.12.115: bytes=32 time=64ms TTL=128
Reply from 115.187.12.115: bytes=32 time=78ms TTL=128
Reply from 115.187.12.115: bytes=32 time=17ms TTL=128
Reply from 115.187.12.115: bytes=32 time=5ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=8ms TTL=128
Reply from 115.187.12.115: bytes=32 time=4ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=5ms TTL=128
Reply from 115.187.12.115: bytes=32 time=2ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=8ms TTL=128
Reply from 115.187.12.115: bytes=32 time=3ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=3ms TTL=128
Reply from 115.187.12.115: bytes=32 time=2ms TTL=128
Reply from 115.187.12.115: bytes=32 time=103ms TTL=128
Reply from 115.187.12.115: bytes=32 time=30ms TTL=128
Reply from 115.187.12.115: bytes=32 time=48ms TTL=128
Reply from 115.187.12.115: bytes=32 time=70ms TTL=128
Reply from 115.187.12.115: bytes=32 time=4ms TTL=128
Reply from 115.187.12.115: bytes=32 time=2ms TTL=128
Reply from 115.187.12.115: bytes=32 time=42ms TTL=128
Reply from 115.187.12.115: bytes=32 time=91ms TTL=128
Reply from 115.187.12.115: bytes=32 time=87ms TTL=128
Reply from 115.187.12.115: bytes=32 time=110ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=31ms TTL=128
Reply from 115.187.12.115: bytes=32 time=42ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=2ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=58ms TTL=128
Reply from 115.187.12.115: bytes=32 time=79ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=4ms TTL=128
Reply from 115.187.12.115: bytes=32 time=2ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=99ms TTL=128
Reply from 115.187.12.115: bytes=32 time=117ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=5ms TTL=128
Reply from 115.187.12.115: bytes=32 time=84ms TTL=128
Reply from 115.187.12.115: bytes=32 time=108ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=2ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=5ms TTL=128
Reply from 115.187.12.115: bytes=32 time=2ms TTL=128
Reply from 115.187.12.115: bytes=32 time=1ms TTL=128
Reply from 115.187.12.115: bytes=32 time=2ms TTL=128

Ping statistics for 115.187.12.115:
Packets: Sent = 60, Received = 60, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 117ms, Average = 24ms
01:08 PM

And a command screen will show the date processing like this:

http://browsersucks.blogspot.in/

How to disable proxy and clean your computer.

User getting error in MS Outlook due to proxy enabled.

Disabling Proxy Settings on the Internet Explorer Using Windows 7

Hold 'Windows' key on keyboard and then hit 'R' key to open 'Run' command.

and then type INETCPL.CPL to open the Internet Options dialogue Box.

OR Follow the below process

 Click on Start, then go to All Programs & locate Internet Explorer

 Right Click on Internet Explorer and click on Run as administrator from drop down menu.

 Go to Tools menu in the Menu Bar at top of your browser & Select Internet Option which will be in the last. Click on it.

 Click on "Connections" Tab, then "LAN Settings"

 Make sure the Proxy server ', Check Box is not selected. If it is checked , kindly uncheck it.

 Click OK to come back to Internet Explorer and start accessing Internet as usual.

OR Follow the below process to disable the Proxy by changing registry values.

Hold 'Windows' key on keyboard and then hit 'R' key to open 'Run' command.

and then type the following Command:

reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v ProxyEnable /t REG_DWORD /d 0 /f

And then Click OK.

OR Follow the below process to disable the Proxy through registry editor

Hold 'Windows' key on keyboard and then hit 'R' key to open 'Run' command.

and then type Regedit to open registry editor and find the following settings should be there:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]

"MigrateProxy"=dword:00000001

"ProxyEnable"=dword:00000000

"ProxyHttp1.1"=dword:00000001

"ProxyOverride"="<local>"

OR Follow the below process to disable proxy using Group Policy editor.

Hold 'Windows' key on keyboard and then hit 'R' key to open 'Run' command.

and then type gpedit.msc, and then click OK.

In Group Policy Object Editor, double-click User Configuration\Administrative Templates\Windows Components\Internet Explorer.

Double-click Disable caching of Auto-Proxy scripts.

Click Enable, and then click OK.

Group Policy Editor

Follow the below process to disable dial-up connection proxy

Now user able must be able to connect to internet using office Local area or WiFi but still getting same proxy error while using the dial up connection or Dongle.

Follow these steps:

1. Check the Dial up connection settings

Select the Dial up connection and then Click on settings

2. Uncheck the “Use a Proxy server…..” check box and apply new settings.

And finally follow the below process to clean your computer.

.       Login as an Administrator.
2.       Remove all unwanted tool bars and third party Browser extensions and unknown programs using iObit uninstaller.
3.       Optimize and clean up computer Internet explorer using CCcleaner.
4.       Clear your browser cookies, SSL State.
5.       Reset Internet Explorer also may try registering DLL files. (for /r %i in (*.dll) do regsvr32 /s "%i")
6.       Try Autoruns , run it as administrator to remove unwanted startup and orphan registry entries.
7.       Scan computer with Anti Malware. Reboot computer and check once more if still issue persists, Go to C:\Windows\system32\drivers\etc
8.       Check Hosts file, Rename or delete the old Hosts file and create a new healthy host file.
9.       Try safe Mode with Networking
10.  Try downgrade or upgrade the browser.
11. Open command prompt as administrator and try SFC /Scannow
12.   Try a System Restore
13.   Try creating new user profile or a new user account.