I have a notebook runing WinXP. My old employer required me to log into the network/server, so the machine was set up to log in to a domain. I no longer work there but still have the machine, and when I boot the machine the domain log in screen comes up and asks for the network password. Is there a way to eliminate this log-in screen and change the machine to a normal (no passowrd) WinXP boot without doing an OS re-install?
An expert who has achieved level 2 by getting 100 points
An expert that got 5 achievements.
An expert whose answer got voted for 20 times.
An expert who has answered 20 questions.
Re: Windows XP Log In screen removal
Try removing the machine from the domain first. Right click on my computer, go to Properties, go to the Computer Name tab, and where it says " To rename thic computer or join domain, click Change", click on the Change button.
In the following screen, select Workgroup, give it any name and click OK.
Before you do this, make sure you have an account with admin privileges on the local machine (make sure you know username and password for this account).
A 6ya expert can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
The service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones). click here to download the app (for users in the US for now) and get all the help you need. Good luck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Either your print-driver settings don't match the ribbon installed, or you have a bad ribbon sensor. Check your driver settings via the Windows printer center screen (Win7: Start Button => Devices and Printers; WinXP: Start Button => Printers and Faxes); locate your Zebra printer, then right-click on it and select "Printing Preferences". Locate the tab for the ribbon setting, and ensure the setting here matches the ribbon you have loaded. NOTE - you must have Windows administrator rights for your Windows log-in ID to make any changes to the driver settings. Contact your network administrator if you do not have these elevated privileges, and they can log in and make any required change for you.
Check to make sure that your main harddrive is working. Sounds as if it is unable to find a bootable drive to configure. It would be better to get the Professional version of XP but since MS is dropping support for XP in 2013 you might have issues. I had an old Windows NT server CD that stopped working after they dropped suport on it. Not sure how that worked since it did not require internet connection to run the setup. They must of put a time code algorthym in the source code to deactivate the CD after a certain date.
Did you press a button (or move a slider-switch) on the WIN7 laptop, to "disable" the wireless adapter?
Can you login to the web-server "inside" the wireless router, and look at the "log-files" that the router keeps of "recent" events (such as connection-attempts from wireless devices), to see if there is any useful information in those logs?
Does the WIN7 laptop connect to _any_ wireless network (Starbucks, university, shopping mall), or does it fail ONLY when connecting to your wireless router?
Have you tried a "factory-reset" on your router, just in case that it might be the problem?
When you go to the Connect to Server dialog, you may browse the names of computers that are on your local subnet.
can connect to a server via its IP address or DNS name. If it is
required or more convenient in your environment, you may also use other
valid URL formats, such as: smb://ServerName/ShareName smb://DOMAIN;User@ServerName/ShareName
The name of the "share" (the shared disk, volume, or directory) must be specified. You will not be prompted for it.
You cannot type spaces as part of the share name when connecting. In place of any space in the share name, type: %20 .
troubleshooting a connection issue, you can ping the IP address of the
Windows PC using the Mac OS X Network Utility application (in the
Utilities folder). A successful ping verifies a TCP/IP connection
between the two computers. This is an important first troubleshooting
step when there's no response or a timeout for a connection attempt,
since SMB connections involving a Mac require TCP/IP. However, a
successful ping does not mean the SMB service is also working or
troubleshooting an SMB connection issue, use Console, which is located
in the Utilities folder. These Console logs may help advanced users
identify an issue: private/var/log/samba, private/var/log/kernel.log,
system.log . Note that some log files only appear when logged into Mac
OS X with an administrator acccount.
If you are connecting
to Windows XP, make sure that the Internet Connection Firewall settings
are not interfering with your connection. SMB uses ports 137, 138,
139, and 445. These ports should be open on the Windows XP computer.
This may require "Advanced" configuration of the XP firewall.
you are connecting to a Windows SMB resource, check to see if the
firewall is blocking TCP ports 137, 138, 139 and 445. After trying the
above steps, you may perform advanced troubleshooting by inspecting log
entries in the Event Log of the Windows SMB resource (if you have access
to it), and/or the Mac OS X computer's relevant logs in the Console
application. If those steps do not help identify the issue, or you do
not want to perform advanced troubleshooting, than you should contact
your network administrator. It may be necessary to contact your network
administrator in some situations in order to grant access to your Mac
from the SMB resource, or its host network configuration.
Mac OS X uses SMB only over the TCP/IP protocol, not the NetBEUI protocol.
You've put a networking problem in as a WinXP issue without describing the network topology. Perhaps the WinXP systems are set up to use the original connection, and the new router eventually tires of that behavior and cuts those systems off; you can look in the router's logs around the time the WinXP systems drop off for clues. Look things up, read the manuals, and you will have a better network for your understanding of its operation.
I solved this by changing the Outgoing Mail Server settings. Open Mail client, select Tools>Account>Properties then select the Server tab. Check Server Requires Authentication and under settings click Log on using and enter your user name and password in the boxes provided, the boxes were already filled out but you may have to enter your information.
Yes, you can upgrade from Win98 to WinXP. The minimum hard drive requirements for WinXP is 1.5GB and the minimum RAM requirement is 64MB. You will also need a CD ROM for the install. Now those are the minimum requirements so don't expect it to go very fast. If possible I would recommend you upgrade to Win2000. WinXP and Win2000 are almost identical. The minimum hard drive for Win2000 is 650MB and for RAM it is 64MB. So you could still use your 4GB hard drive and have plenty of room. You will need a CD ROM for the Win2000 also. Good luck if you have anymore questons let me know,
Don't forget to rate this solution before you log off.
You need to go into administrative tools and look for group policy.
In the local computer policy
Windows Settings > security settings > Local policies > user rights assignment. In the right hand pane find the policy for "Allow log on locally" Set the user accounts for those users which are allowed to log on interactively on the server. Be careful you dont lock the administrator account out.
Use in conjunction with the "Deny logon locally policy" if you need to.
Hope this helps
I don?t have the equipment to test your setup; however, I suspect your problem is in redirecting the device to the terminal server session. Check the terminal server system event log file to see if you are generating any messages when you connect. When my users have issues, typically with printers, they will be listed in the log as *Errors* and the source will be *TermServDevices*.
If you?re using the latest Remote Desktop Client there is a tab in options called Local Resources which is used to deal with configuring your workstation sounds, keyboard, printer, and other local resources to redirect to the terminal server. Click on the More button at the bottom and you will be taken to the more generic section of resource redirection that deals with other items. Your device is probably USB so if it is going to work is would fall under the scope of the section labeled *Supported Plug and Play devices*. You would start by placing a check in that box, reconnect and see if you keypad works now or if anything shows up in the event log.
Let us know how this turns out and if you have any other questions. As always please don?t forget to rate this post.