Over 1 million tech questions and answers.

Hp 250 notebooks not able to connect to a network domain.

Q: Hp 250 notebooks not able to connect to a network domain.

All of a sudden, the HP250 laptops we have are not able to connect to our network.I have taken them out the domain to try and join them back, and now I keep getting this error message: The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "nsnet.net":The error was: "DNS name does not exist."(error code 0x0000232B RCODE_NAME_ERROR)The query was for the SRV record for _ldap._tcp.dc._msdcs.nsnet.netCommon causes of this error include the following:- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:10.177.76.10- One or more of the following zones do not include delegation to its child zone:nsnet.netnet. (the root zone) I have googled this and done everything and they still will not connect. All other HP notebooks/laptops have no connection issue.

RELEVANCY SCORE 200
Preferred Solution: Hp 250 notebooks not able to connect to a network domain.

I recommend downloading and running Reimage. It's a computer repair tool that has been proven to identify and fix many Windows problems with a high level of success.

I've used it in the past to identify and fix everything from blue screens (BSOD's), ActiveX errors, corrupt files and processes, dll/exe/sys errors, recover lost memory, Windows update problems, defragging, malware removal etc.

You can download it direct from this link http://downloadreimage.com/download.php. (This link will automatically start a download of Reimage that you can save to your computer.)

A: Hp 250 notebooks not able to connect to a network domain.

Which version of Windows 7 is installed? If it is Home Premium, then it is a limitation by design which will not allow it to connect to a Windows domain. That limitation does not apply to Windows Professional ad Ultimate versions.

Read other 1 answers
RELEVANCY SCORE 64.4

PCs are Win 7 Ultimate, All are joined to the Domain
Domain Controller, DNS, DHCP Server (on same instance) is Server 2012 standard
The network topology is like this: Router as Internet Gateway>Switch>Wired to Server and PC's, SIP phones, and Wireless Access Point all on same subnet. DNS and DHCP have been offloaded to Server Roles and switched off on the router.
All of the PCs have network cards that have joined the domain network at least some of the time since I set them up.
Some of them have always picked up the domain network and continue to this day.
Some of them intermittently pick up the domain network and other times join whatever other unmanaged network is available.
Some of them have stopped picking up the domain network altogether and will, no matter how many times their NICs are restarted, always join a non-domain (unmanaged) network.
When the NICs are not joining the domain, they are unable to ping hostnames of any devices on the network but nslookup of the hostnames usually works. The DC, DNS, DHCP server's IP can be pinged without issue, ipv4 or ipv6.
I am recording DNS Client Errors (ID 1014) on all of the PCs during the intervals when their NICs are identifying which network to join.

-On the PCs that are catching the domain network I am only getting a single error about the root domain, eg the domain is ad.domain.com and I am only getting errors about how the configured DNS servers cannot resolve domain.com (nothing with fully qualified
do... Read more

Read other answers
RELEVANCY SCORE 60

At my work, we are upgrading all computers from Windows 7 to Windows 10 (roughly about 12 computers total). So far 6 of them have been upgraded successfully with not network issues. There is a company domain in place. After upgrading the 7th computer, a Dell Latitude E6410, to windows 10, I cannot access the shared drive on the network. I can connect to the network, see shared printers and any shared workstations, and can even access the internet, but cannot connect to the shared drive. When attempting to do so, the message about missing network protocols come up. I have tried a few suggested fixes but cannot fix the issue.

Any ideas?

Read other answers
RELEVANCY SCORE 60

I'm trying to setup an FTP server to upload photos and videos to, and tried to setup a program to automatically change the ip on the domain every time it changes, but have been having trouble with it.
 

Read other answers
RELEVANCY SCORE 59.6

I am having an issue with some client computers running xp, they are unable to connect to the domain or map network drives. I have ghosted these computer for a temporary solution but it has been happening to multiple computers now.

The error message that comes up when I try to map a drive or connect to the domain is "network location cannot be reached"

Any Ideas on how to resolve this problem without having to ghost these computers?

Read other answers
RELEVANCY SCORE 58

Hello,
I have 3 interfaces running Win7 on a company network with 3 network share drives on the server.
These interfaces are part of WORKGROUP.  Mapped drives work while on WORKGROUP settings.
When changing to company domain, drives are no longer mapped with an error 1909.
Tried disabled Windows firewall but this did not help.  Also disconnected drives and tried remapping them to the interface.
Still getting error 1909.  When I return settings to WORKGROUP network status, share drives are accessible.
There are 3 other interfaces running Win7 on the network that I switched to the domain and were able to connect to drives.
Please advise with any new options.
Thank you,
Troy

Read other answers
RELEVANCY SCORE 54

OK, I am trying to connect to a domain, which other people have successfully connected to.

i type in the admin username and password after typing in the AD directory, and then I get this
"network path not found"

This message is driving me nuts!

I have checked the DNS, enabled all networking features in XP, and I cant think of anything else...

the domain is active-directory.****-****.eu (im keeping this hidden for now)

Help please...

Read other answers
RELEVANCY SCORE 53.6

Hello everyone. I really hope that you can help me. You are my last hope.

I maintain about 30 domain computers. Recently when users try to log in on most of them the following error appears frequently:

"Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. if the message continues to appear, contact your system administrator for assistance."

I have seen that this error appears only in the computers with Windows XP and not in the computers with Windows Vista or 7. We have 2 domain controllers.

Please let me tell you about the ways I tried to resolve this problem and their results:

- on some computers, after several restarts the users are able to log in, but if they restart or shutdown after that the error appears again; this worked for some computers, but I do not know if the error will appear again in the future.
- on some computers, when i disabled the windows firewall or allowed all kind of ICMPs it was resolved, but this did not work for all the computers and I do not know if the error will appear again in the future.
- I unjoined and then rejoined some computers from the domain and it was resolved but after restarting the error appears again.
- If I unplug the network cable the users can log in but after restart the error appears again.
- I have tried to reset the user password and computer on the Active Directory for some users and... Read more

A:windows cannot connect to the domain, either because the domain controller is down...

Read other 16 answers
RELEVANCY SCORE 53.2

I'm running into a problem with connecting to network drives over a VPN. The common difference is whether or not the computer is part of the domain by default.

1) Computers connecting to VPN using local account on computer: Prompted for a domain login when attempting to use the network drives. Can get in.

2) Computers connecting to VPN using a domain account (but on another network): Unable to connect. Specific error changed based on below info.
A) Computer logged on and connected to an outside network. Never connected to domain network: Can't find folder error.
B) Connects to domain network at some point before connecting to an outside network and using VPN: Might be in use error, attached.

A:VPN Network Shared Drive Error Domain/Non-Domain Differences

Sounds more like the network the VPN connection puts you in has trouble making kerberos connections to domain controllers, but NTLM connections work fine (kerb might be blocked). The errors are likely bogus if you can get #1 to work - if the computer is connected to a domain it's going to want to use Kerb before NTLM, and if the machine still has (what it thinks is) a viable kerb ticket, it's going to try and validate that with a DC (to achieve auth), and if this fails, so does the connection.

This may not actually be the case, of course, but it sure has the symptoms of it.

Read other 1 answers
RELEVANCY SCORE 52.4

Can I access a network share on the domain with a non-domain computer? I would connect the computer directly to the corporate network. 
For what reasons could this be blocked (firewall? policy? settings on server-side?) and what configuration is needed to make sure it is possible to access a network share with a non-domain computer?
Thanks already for your help!

Read other answers
RELEVANCY SCORE 52.4

I've got a†machine running Windows 7 logged on the network domain†but when I try to map a share to a machine on the network, but not registered on the domain I cannot connect (even though I have a local account on the networked machine).When attempting to connect Windows 7 prompts me for my connection credentials and it automatically fills in the domain name.† How can I connect to this network share using credentials that are local to that network share?

A:Logging in to Non-Domain Network Share from computer on Domain

When you say local credentials I assume you mean local on the "TestServer", not local on the Windows 7 box. Then you should be able to just type in TestServer\LocalAccount and the password (the domain you see should automatically switch to "TestServer")Also; have you tried mapping the drive using the IP address (i.e. \\xx.xx.xx.xx\TestShare)?

Read other 14 answers
RELEVANCY SCORE 49.6

Hi.
I have a non-domain computer (win 10 basic).
Can it connect to a Aerohive wireless domain network?
Any links to a tutorial on the net?

Thanks...

Read other answers
RELEVANCY SCORE 47.2

Hi,
One domain user recently can't see network drives and use printer. When you join a domain it automatically maps those drives and ads that printer, and it did, but now it is all gone. You can't even see disconnected drives in My computer. I am able to ping
those drives, but that's it. And this occurs only on one computer on one user. If log in to different user on that computer everything is fine and if I log in with that user on different computer it also works. Tried looking for disabled services, but couldn't
any that would be turned off from the most important (Workstation, Network location awareness, Network list service). Any suggestions?

Read other answers
RELEVANCY SCORE 46.8

HI,

I have installed server 2003 on a small network and created a domain that is the same as the public domain name (ie the companies website).

This is now causing a problem because when i type in the public address (for example www.company.com) it is trying to resolve it locally - because the local domain name is also company.com.

Does anyone know if there is a way to get round this problem?

Many thanks in advance

Dave
 

A:problem with the local network having the same domain name as the public network

add 'local.' to the internal domain or change it altogether.

Your public domain should not have any connection into your private infrastructure,
but you may have references from private->public; not very common.
 

Read other 6 answers
RELEVANCY SCORE 46

hello,

i have 8 laptops all running windows 7 ultimate and 1 pc with windows server 2008 r2. i created a domain and sorted the dns server and went to connect my laptops to them. when i typed the domain name in it asked for a username and password so i typed my username and password of the administrator account (admin account was activated) and it said ' cannot connect to domain'

can anybody help me i can't think of what is wrong. (images would really help.)

Thanks

A:Cannot connect to my domain

  
Quote: Originally Posted by liamacalvert


hello,

i have 8 laptops all running windows 7 ultimate and 1 pc with windows server 2008 r2. i created a domain and sorted the dns server and went to connect my laptops to them. when i typed the domain name in it asked for a username and password so i typed my username and password of the administrator account (admin account was activated) and it said ' cannot connect to domain'

can anybody help me i can't think of what is wrong. (images would really help.)

Thanks


I believe the easy way would be to first install Active Directory to the server if it's not already installed.

The link shows you how to do this from the client PC but I believe Active Directory needs to be installed for this to work. The video makes it look easy so hopefully it will work for you.
http://www.youtube.com/watch?v=jUUjAkjzV9U

Read other 8 answers
RELEVANCY SCORE 46

I am working on personal home project to learn windows server 2012. I am using a virtual box to setup the server for testing. I have setup the DNS and Active Directory. I ping the Server (Machine Name), but not the DNS Domain Server (Svr1.Local), however I can not join the domain. I have added an account to the AD with all computer rights. Do I have add the computer that I am trying to join to the domain ? The IP is as Follows:

IP: 192.168.200.50
SubMask: 255.255.250.0
Default Gateway: 192.168.200.1
Dns: 192.168.200.50

Also I have setup the adapter in vitual box as bridge.
I can view the files if use the IP address from the windows explorer and I can even remote to the server, but I can join the domain to use AD. The computer that that I am trying to join has windows 7 Professional.

Any suggests or I ideas would be appreciated.
 

Read other answers
RELEVANCY SCORE 46

guys,

i have no idea when this happen or why or by who, but please any advice will be very much appreciated.

here's the case:
i'm have 4 DCs that replicted each other, when i opened my AD and right click an OU. click the properties, and then the "group policy" tab, there is an error that said "ACCESS IS DENIED".

i'd tried to open the domain security policy and the domain controller security policy from the administrative tools, there is also an error that said "ACCESS is denied". i tried to use the snap in and the error is "Domain does not exist or could not be contacted".

please help, i'm so desperate, because we're being audited by TUV, and i must print scr my GPO.
 

A:GPO - cannot connect to a domain

Read other 10 answers
RELEVANCY SCORE 46

Hi,
 
I'm trying to setup a computer to connect to a domain set by the server. However, I'm getting the error "an active directory domain controller ad dc for the domain could not be contacted". Trying to follow this tutorial on Youtube, however, in the properties of IPV4, I need to connect to the a domain with numbers. How can I find out that number in the server?
 
Alternatively, anyone got any other suggestions to connect?
 

 

Read other answers
RELEVANCY SCORE 46

Hi everyone,

I work as an IT consultant for a real estate company. I keep having this same problem with the same model computer. I am trying to connect to our domain. When I go to add the computer I get the error message:

The Domain controller for the domain XXXXX.local could not be contacted.

I know everything is fine with the server as I have changed other PCs on the domain with no problem. This same type of PC keeps giving me the same problem at various locations and different local domains. I can't figure this out at all.

The type of PC is link here.

Has anyone had this same problem before? Any help would be greatly appreciated!

Thanks!!
 

Read other answers
RELEVANCY SCORE 46

I have win xp pro and log on to the domain.The domain name is right and have set to obtain IP address automatically.The computer name is also right.What could be the problem.Any solotions will be appreciated.
 

A:cant connect to domain

Read other 6 answers
RELEVANCY SCORE 46

Alright, so I've started a new job and it's time to put out some fires. Here's the deal. Our network domain is E-HAMPTON, it's a winnt 4.0 network. We have a windows 2003 webserver that you can link to at http://e-hps.net That webserver is on the domain e-hps.net What I want to know is if I put that webserver on the E-HAMPTON domain, am I going to lose web connectivity to http://e-hps.net or is that an entirely different issue? If I put the webserver in our network domain is it going to try to take over all domain authentication? Also if anyone see's any other potential pitfalls please pass them along.
 

A:A web domain and a network domain

Ok, so E-Hampton is the Primary Domain Controller (PDC). Correct?

Is the Windows 2003 webserver running XP Pro with PWS? Windows 2003 Server w/ IIS? Enterprise Server w/ISS? Apache?

Is it configured as a Domain Controller on the e-hps.net network?

There was a pretty big jump from NT 4 to the Windows 2000/Windows 2003 architecture as far as domains go. With 2003 you're into the world of Active Directory, Trees, and Forests.

As for whether or not you'll lose connectivity, it depends on how the network is set up, whether it is assigned a static IP address or on a DHCP controller with a reserved address, whether or not it is in a DMZ, etc., etc., etc. Is it a dual NIC machine (one NIC to the network, the other to the Internet)?

There is an awful lot going on there. We'd almost need to see a diagram to make a call on this one.

In short, this isn't as simple a question as it sounds.
 

Read other 3 answers
RELEVANCY SCORE 45.6

I need to connect to my work domain for various things, but at home I have a workgroup with shared printers etc. There is another workgroup with shared I need at another office.

How can I configure my XPSP2 laptop to connect to domains and workgroups without continually reinputting the settings and rebooting?
 

A:Connect to Domain & Workgroup?

you might try to create a LAN connection for each one you need then just right click and connect or right click and disconnect as you need to.
good luck.
P.S. for the domain you have to go to sys properties and change from a domain connection to a workgroup connection
 

Read other 2 answers
RELEVANCY SCORE 45.6

Working on a pc thatwas set up as a "Workgroup" and trying to connect work station to "domain" but can not. Receive an error "Network location cannot be reached". I can ping the domain controller.
 

A:Unable to connect PC to domain.

Read other 9 answers
RELEVANCY SCORE 45.6

I keep getting this error message, but I get the Domain login screen.
"An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain. For information about network troubleshooting, see Windows Help." I have gotten this message, but do get a Domain login screen. Help!

Thanks in advance!
 

Read other answers
RELEVANCY SCORE 45.6

I'm trying to print on a printer which is on other domain.

Let's say I'm on Vancouver domain trying to print on Toronto domain printer.
I want to add it as a network printer on my Vancouver domain computer.
How is it possible? 
what are firewall ports should be allowed?
Can this be done? 

Shekar

Read other answers
RELEVANCY SCORE 45.6

When I try to connect to our domain I get the error message:

Changing the Primary Domain DNS name of this computer to "" failed. The name will remain "(name of our domain)" The specified domain either does not exist or could not be contacted.

The procedure is the same I've used since Hector was a pup and never had a problem. I don't know what is different with Windows 7. I can't add users to the domain and can't log on directly to the domain.

Would be greatly appreciative if someone could help.

Thanks.
 

A:Solved: Connect Win 7 to Domain

I hate to even put this out here, as in hindsight, it was so stupid as to be laughable.

Windows 7 doesn't automatically prompt for an administrator password when installing, only a user with admin privileges. Well, to make and keep changes for all users, you have to do them via the administrator and I did them with the user privileges. After I initiated the administrator account and reapplied all the changes and added the computer to the domain, surprise, surprise ....... every worked as it should.

Stupid mistake and not one that I'll make again any time soon.
 

Read other 1 answers
RELEVANCY SCORE 45.6

Hi,

At my office we have a domain based network with about 15 connected computers, all of them with Windows XP installed. Now we have installed a new computer with Windows 7 Professional, and connected it to the network. There is no problem to access shared files and printers from the Win7 machine, but no other computer on the network can access shared files on the Win7 machine. On any XP machine, I can see the Win7 machine among the other computers on the network, but when I try to access it an alert shows up, telling me that the computer isn't available (which it is).

On the Win 7 machine, in Control Panel > Network and Sharing Center > Advanced sharing settings, I have turned Network discovery, File and printer sharing and Public folder sharing on. (A weird thing is that I can't see an alternative to password protect shared files, but that's probably not the problem anyway since I'm not asked to type in a password when I try to access from a XP machine). And of course I'm not connected to any workgroup, but the domain we use on the network.

I hope I can get some help here. Thanks in advance!

A:Connect XP to Win7 over domain

  
Quote: Originally Posted by andechspam


Hi,

At my office we have a domain based network with about 15 connected computers, all of them with Windows XP installed. Now we have installed a new computer with Windows 7 Professional, and connected it to the network. There is no problem to access shared files and printers from the Win7 machine, but no other computer on the network can access shared files on the Win7 machine. On any XP machine, I can see the Win7 machine among the other computers on the network, but when I try to access it an alert shows up, telling me that the computer isn't available (which it is).

On the Win 7 machine, in Control Panel > Network and Sharing Center > Advanced sharing settings, I have turned Network discovery, File and printer sharing and Public folder sharing on. (A weird thing is that I can't see an alternative to password protect shared files, but that's probably not the problem anyway since I'm not asked to type in a password when I try to access from a XP machine). And of course I'm not connected to any workgroup, but the domain we use on the network.

I hope I can get some help here. Thanks in advance!


Just curious. Are you using "homegroup" for networking? Homegroup uses IPv6 and is primarily designed for win 7 only networks. You can see if this is the problem by creating a new network connection using the workgroup model.

Let us know if you need help

Ken

Read other 9 answers
RELEVANCY SCORE 45.6

Hi there,

I have been using Windows 7 with domain "domain1" and connected to Windows Server 2003. The owners decided to change the domain of the network from "domain1" to "domain2". Someone was hired to do the job for the company. Since I was on work tour my PC was left without any change. Now the gentleman is gone and I can not connect the domain on Windows 2003 Server. I was told to remove previous domain and switch to WORKGROUP and then switch back to "domain2".

I followed the steps till I get to username and password window. I enter my username and password and after few minutes I get the following error:

"An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the terget domain"

Please help.

A:Windows 7 won't connect to domain

hello and welcome
when you change the domain name with "domain2"
make sure that's the DNS on the windows server 2003 already configuration. because before Windows server 2003 is read the first domain ( domain1), that's why you can't to login.
Edit : Joining domain
you can try this..i think that's same issue..

Cheers ~

Read other 9 answers
RELEVANCY SCORE 45.6

Hello Everyone,

I had an Internet source before where it had a modem with 4 internal switches, so me and my bro got connected to it directly. Now, i m established with a new Internet source and it has only one switche. Now, my system has the Internet but not my bro's. I was told to make a network between me and my bro's system and make my pc as a domain for Internet and networking.

I even have the small hub, but I wasnt successful trying that, cos the new setup has the internal settings and my bro's system does take that

Can anyone pls guide me on how to network with my bro's pc and get Internet in his pc through mine.
 

A:How to connect through LAN and make my pc domain

Can I assume that here is no router involved here?

Routers are cheap and a pretty easy way to set up a home network.We have some pretty good guides here if you choose that option.
 

Read other 1 answers
RELEVANCY SCORE 45.6

Hello everyone!
Can you please state categorically, step by step how you were able to add the Windows 7 pc to the Windows 200 AD Domain.

I am unable to have it joined and am receiving the following error:
"An attempt to resolve the DNS name of a domain controller in the domain being joined has failed.
Please verify that the client is configured to reach a DNS server that can resolve DNS names in the target domain."

Many thanks,
Taz.

A:Unable to connect to domain

To reach those win 2k domains you will usually need to find out which DNS your domain server is using then add that DNS address or addresses to your IPv4 properties as a static DNS.

Read other 1 answers
RELEVANCY SCORE 45.6

- Windows 2000 Network. PDC has Win2k Server.
- All Win2k computers can connect to the domain w/o problem
- NT 4.0 (SP6a) machine used to connect fine but can't recently.
- Only recent change to the PDC was the installation of SP4.
- I can ping the PDC by IP address but not by name

Stuff I have tried:
- I tried switching it to a workgroup, rebooting, then switching
them back to the domain but now they give "Unable to connect to
the domain controller for this domain. Have your administrator
check your computer account on the domain." The computer account is on the PDC and a member of "Domain Computers"
and "Pre-Windows 2000 Compatible Access"
- I tried unchecking the "Enable LMHOSTS Lookup" check box in
Network\Protocols -> TCP/IP Protocol -> Properties -> WINS Address, as recommended by MSKB Article 271925 but that did not help.
- I tried changing the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
\LanManServer\Parameters values for EnableSecuritySignature and RequireSecuritySignature, then restarting Net Logon as recommended by
http://content.techweb.com/winmag/library/1999/0501/sol00074.htm, but that did nothing.
- Lastly I tried what was recommended in MSKB Article 293127 which was:
Change the HKEY_LOCAL_MACHINE\System\CurretnControlSet\COntrol\Lsa
\restrictanonymous DWORD value to 0, but I haven't rebooted yet since I don't want to boot everyone else who is currently on the domain... I am not holding ... Read more

A:NT 4.0 can't connect to domain controller

Read other 8 answers
RELEVANCY SCORE 45.6

Hi,

I am working on getting Windows XP to connect to a domain on my Windows Server 2008.
I was able to get it just about connected till I get the message "Logon failure"
I made sure the username and pass were correct, and they are.

Here are the screen shots:

A:Problem getting XP Pro to connect to domain

hi
please check the permission given to the user you have made on the server side as well as in XP Machine.

Regards

Read other 4 answers
RELEVANCY SCORE 45.6

Ok, so here's my problem.

I WAS part of an ad domain. But I needed to connect to some local computers so I change my computer do a workgroup.

Problem is... I don't appear to have a logon on the computer. So when I restarted after changing to the workgroup, I can't log into the computer. So I can only login to the domain it seems.

So is it possible to change my computer back to the domain? (Noting that I can't login to the computer right now because I don't have an account to the work group?)

Futhermore, how does my computer connect to the domain when I don't have internet access? Shouldn't there be an account on the computer somewhere that is [email protected]?

I hope I explained my problem well enough, thanks!
 

A:how to connect to domain (from login)

Oh... furthermore, I don't have the "Domain:" option when I click "Option>>"

Version is Windows XP Pro.
 

Read other 1 answers
RELEVANCY SCORE 45.6

Hi,

We have a small network of 7 computers and all are connected to a workgroup named MSHOME.
Today new client came to our company and he bring his laptop.
He wants to use our existing network and internet too.

So I have changed his computer properties from domain to workgroup MSHOME.

So now his laptop is no more connected to any domain and is in workgroup.
No the client wants to connect to his company via VPN and wants his old login screen where in login dialog there was
username
password
domain

When i tried to agian change laptop's property to domain and tried to given old domain name it shows the following error message:

A Domain Controller for the domain could not be connected.

Ensure that the domain is typed correctly.

If the name is correct, Click Details for the troubleshooting information

Well this will obviously come as there is no domain exists in our network.

Is there any other way that i can re-configure that laptop in domain and user can get the old login screen with domain name?
form local profile or anyother way?

Regards,
Little Boy
 

A:How to connect to domain back

Read other 12 answers
RELEVANCY SCORE 45.2

One of my computers has recently decided it will not connect to my domain...sometimes. I had reformatted this computer about a week ago and it was working great till yesterday. One of my employees tried to log on and it gave her an error;
"Windows cannot connect to the domain. Either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear contact your system administrator for assistance."
I then logged on as an admin ONCE and it worked, then i logged in as another employee and it worked ONCE. Then i tried to log in as an admin again and it gave me that error, crazy right!
So i logged in with Safe mode with networking and it does the same thing. I replaced the Ethernet card and the slot of the bus, that didn't fix it, then i changed the cable, and that didn't do anything, i replaced every cable and plug i could and nothing changed.
I can log in to admin locally every time, and when i do manage to log on to the domain the once it works fine.
Help would be appreciated cause in stumped.
 

A:Solved: Domain wont connect....sometimes.

Remove that computer from the domain, restart the computer, then re-add it. Also, check your domain controler while it's restarting and make sure that computer shows up in your Active Directory list.
 

Read other 3 answers
RELEVANCY SCORE 45.2

If I connect vista to a domain cntroller, is their any way that I can display the regular screen?
Not the CTRL ALT Delete login.
I want visual login.

Anything?

A:Connect to Domain Controller questions

Ctrl-Alt-Del (SAS) logon has security benefits over the "pretty" (FUS) non-domain logon UI. That's why the act of joining a domain kicks the machine over to SAS logon... it's considered a corporate machine and that (presumably) means the need to emphasise security.

Read other 2 answers
RELEVANCY SCORE 45.2

I'm using Windows 2000 Server (as a PDC and the only domain controller) on my network. I have Windows NT, Windows 2000 and Windows XP Pro clients.

When I log on to the domain with a XP client all the network shares (and printers) work OK for a certain amount of time (I don't know exactly how long 2min-5min) but after that they stop working. If I try to connect to a network share I get this error message:

The system detected a possible compromise in security. Please ensure that you can contact the server that authenticated you.

If I log out and then log in again, everything works again. I don't have any problems with NT and 2000 clients and the domain server itself is available all the time.

Any ideas? Thx in advance,

Amer
 

A:Can't connect windows xp profesional to domain

when that happens can you ping the server?
 

Read other 6 answers
RELEVANCY SCORE 45.2

Hi,
I am unable to ping/remote desktop/access shared drives to a XP machine after it joins the domain. I removed it from the domain, everything is fine. I disabled anti-virus program, no luck. Firewall setting is from the GPO. Other computers in this domain
are fine.
DNS, DHCP match the computer IP. When I ping it, I got 4 "Request timed out" reply.
Please advise!
Thanks in advance!

Grace

Read other answers
RELEVANCY SCORE 45.2

Hello Friends

I have 6 PCs which I got off a friend who wound up his business. The machines are set up to logon to the old now none existent domain.

When I switch on the machines the typical set up is this

CS-PC08
password:

I have no passwords

Switch user, none available, I do have an option to log on to another domain.

To Logon to another domain enter domain\user

To Logon locally it says, enter CS-PC08\local user name

I have no password or user names.

I cannot boot in safe mode or in safe mode with command prompt without encountering a logon screen.

I have downloaded Password Unlocker and whilst this allows me to change passwords and add users I still get the same logon screen and none of my new user names or changed passwords help.

I have no disks so cant do a reinstall.

Any and all ideas welcome.

Thanks

A:Second hand PCs what to connect to non existent old domain

Looks like you will have to get into the bios and stop the computer from booting from LAN.
Can you not talk to your friend to get the passwords.

Read other 9 answers
RELEVANCY SCORE 45.2

Hello folks!
here is the network admin at GESS,
I have this strange problem!
I have this computer which has been working fine for more than one year!
but one fine morning it just doesn't connect to DNS server!
It doesn't even ping any more!
it would ping other computers on the network but not DNS-ip address!
please help !!
Ali Syed

A:DNS does not connect to one single computer in the domain!

Try a winsock reset if you are running WXPSP2/Vista you can do this command in a command prompt and then restart the PC.

netsh winsock reset

Reboot and see if that helps.

Read other 2 answers
RELEVANCY SCORE 45.2

I have installed WIN Server 2012 on my laptop using a new volume and dualBoot.
I would like to set it up on our domain but I'm not very technical. I have run NSLookup but I don't really know what I'm looking for. I haven't yet setup the DNS on the server.

Thank you in advance for any assistance you make be able to offer.
 

Read other answers
RELEVANCY SCORE 45.2

We have a couple of hundred client machines running XP (some SP2, others SP3), on a single domain. Recently we have noticed that some machines are inaccessible. You cannot remote into them, you can't browse them on the network and you can't even ping them. On the client side though, everything appears normal - they can see and access all network resources. We only notice the problem when we need to access the machine, so we don't know "when" this problem is occurring.

We found a workaround - if we remove the client machine from the domain and add it back, everything goes back to normal as far as remote access is concerned. But this takes time and requires IT hands on the machine. Not a preferred situation.

Any clue as to what is going on?

It's not a permissions thing, we have full domain admin access.
We also know that when the client machines were originally setup, anywhere from a month ago to a couple of years ago, remote access was not a problem.

 

A:Cannot connect to client until rejoin domain

Read other 7 answers
RELEVANCY SCORE 44.4

Hello,
I have one computer on our domain that can't connect to a shared drive. All other computers can, and it affects everyone who logs into the machine. When you try to map to it, or even use the unc path in windows explorer, you get an access denied error. If
you try from any other machine it works just fine. The machine can connect to other shares on the server just fine. 
Does anyone have any ideas? 

Thanks

Read other answers
RELEVANCY SCORE 44.4

Here are the details;
Server is a Dell PowerEdge sc420 running SBS 2003
There are 5 boxes running winXP pro SP3 linked via Active directory all with static IP's and Default gateway and DNS pointing to server. Internet is coming in as DSL, goes to a linksys router, then to a hub - which everything connects to. (server, XP boxes, and printers) The linksys is currently controlling DHCP. DNS from the server.

Four of the boxes have no problem connecting, grabbing data from the server or using either of the laser printers installed on the network.

The exception is the one that cant connect. Up until this morning it never had a problem, but then it was rebooted and upon entering username/pass at the ctrl+alt+del prompt, I receive an error "Windows cannot connect to the domain because controller is down or otherwise unavailable or because your computer account was not found. "

I cannot connect using administrator's account either, I get the same error.

The computers settings have not changed in Active Directory locations (domain users, domain power user, & domain computers), DNS locations, or in Security Policies. So I have no idea whats going on.

I had the same issue awhile back on a different computer and had to logon to the computers account as admin to change domain association to WORKGROUP, reboot and re-establish the domain association. Using the same name as before - which I didnít really understand but thatís another story.

My issue here is th... Read more

Read other answers
RELEVANCY SCORE 44.4

Pretty much sums it up. Have ran ms secess and still have problems with connecting to the domain and slow system speeds.
Have run combofix and seems to hang after completed stage_4. Problem occurred on clients system last night or this morning. System is not receiving any AD data and mapped drives aren't connecting.

A:Infected with 64:sirefef/ad and unable to connect to domain

Hello midiean and welcome to BleepingComputer forums. Backdoor trojan warning:ZeroAccess / SirefefThis system has some serious backdoor trojans. ZeroAccess / SirefefThis is a point where you need to decide about  whether to make a clean start.According to the information provided in logs, one or more of the identified infections is a backdoor trojan. This allows hackers to remotely control your computer, steal critical system information, and download and execute files.You are strongly advised to do the following immediately.1. Contact your banks, credit card companies, financial institutions and inform them that you may be a victim of identity theft and ask them to put a watch on your accounts or change all your account numbers.2. From a clean computer, change ALL your online passwords -- for email, for banks, financial accounts, PayPal, eBay, online companies, any online forums or groups.3. Do NOT change passwords or do any transactions while using the infected computer because the attacker will get the new passwords and transaction information.These trojans leave a backdoor open on the system that can allow a hacker total and complete access to your computer. (Remote access trojan) Hackers can operate your computer just as if they were sitting in front of it. Hackers can watch everything you are doing on the computer, play tricks, do screenshots, log passwords, start and stop programs.See this article on creating strong passwords   http://www.microsoft.... Read more

Read other 3 answers
RELEVANCY SCORE 44.4

win2k3 sbs one client refuses to connect to domain
Hey everybody,

I stepped into a situation with a company whose computers were quite screwed up. I've fixed and setup work arounds for all the problems but one.

The windows 2003 server runs ok. There are three client computers (the bosses, the secretary's, and this one I'm working on now). Two of the client computers work just fine, they connect to the domain no problems.

The computer I'm currently stuck on (that I reloaded with WinXp Pro & SP2) refuses to log on to the domain. I setup the client with the domain, which refused to work for a while but finally took. I got alot of "The RPC server is unavailable" messages while trying to get the domain to take. It finally did take.

The reloaded computer has no firewalls running, and all the network settings are default/automatic and I've verified they match the other two client computers exactly. I get this message when trying to logon to the domain from the client computer:

"Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable...."

There is a 4 port router which I've checked the settings on. It's setup with the static IP address and DHCP/etc disabled, and controlled by the server, as it should be. No IP's are blocked, nothing seems amiss there.

The reloaded machine has no firewalls running, not even windows firewall.

The server can ping the client by name ... Read more

A:win2k3 sbs one client refuses to connect to domain

The Red Flag I see is that the client cannot ping the server by IP address.

IP Stack may be corrupted.

Try This:

Start, Run, CMD to open a command prompt:

Reset TCP/IP stack to installation defaults. Type: netsh int ip reset reset.log

Reset WINSOCK entries to installation defaults: Type : netsh winsock reset catalog
Have you tried plugging the broken client into a port on the router that a WORKING client currently is using?
 

Read other 1 answers