LaurenG
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 03:37 PM
Original message |
| Help computer network problem |
|
Win2k new addition will not join domain, insists on setting up a workgroup with only itself.
When attempting to join I get this error messege; "your computer could not be joined to the domain because the following error has occured, the network was not found". The problem with this is that the computer shows up under workgroup on the network and connects to the internet (for all those windows updates) through the lan. What does it want? Does anyone know? The bosses son used to take care of this but he went to college so now it's only me.:cry: :shrug:
|
TrogL
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 03:39 PM
Response to Original message |
|
Put the ip address and name of the BDC in the lmhosts file, make sure WINS is pointing to a valid WINS server. If it still hates it, manually put an entry for the PC in the domain on the BDC and try joining again.
|
LaurenG
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 03:42 PM
Response to Reply #1 |
|
Can do, I will make that sucker join, now that I'm armed with IP address info. Thanks :hi:
|
seemunkee
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 03:46 PM
Response to Original message |
| 3. Is this a new machine? Was it previously on another network |
|
There is a bug in W2000 that will sometimes prevent you from switching domains and/or workgroups. You may need to remove the TCP/IP protocol from the network card, reboot and add it back in.
|
LaurenG
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 04:55 PM
Response to Reply #3 |
| 5. Actually it was an old machine |
|
that was really whacked out so I re-installed win2-k and deleted the C: Fat 32 and D: NTFS and started all over again reloading drivers etc. The network card has had it's drivers reinstalled as well. It's all fresh now and finds the network, but refuses to join the domain. I hope it doesn't still have a virus after that. Thank you for the info though at least I can be on the look out for that as we have 15 that screw with me from time to time. Thank you for the information.
|
Crazy Guggenheim
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 04:58 PM
Response to Reply #5 |
| 6. Update the NIC drivers too. Are you saying a "Domain" or |
LaurenG
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 05:05 PM
Response to Reply #6 |
| 8. I'm saying all the computers are on a domain except |
|
the stupid one that insist on staying in a workgroup by itself. It WILL NOT join the domain. So under my network I have a domain with 14 computers and a workgroup with one.
|
Crazy Guggenheim
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 04:15 PM
Response to Original message |
| 4. Yeah yeah yeah. First, make sure the "Workgroup" names are the |
|
Edited on Fri Nov-04-05 04:17 PM by Crazy Guggenheim
same for the W2K and the other systems. Then go into Network Connections, Right click on the connections and choose Properties. Make sure you have all the Protocols installed except DLC and I think there is something for Mac - umless you need it. Reboot the system and see what happens.
|
LaurenG
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 05:03 PM
Response to Reply #4 |
| 7. I did and they are all win 2k |
|
I think the network address gets jacked up because we have a high speed internet connection and the isp takes control of the ip address. I'm not certain but I am sure it has something to do with the IP address.
Sheesh I frustrate myself because I have so little knowledge of 2-k professional and 2-k server. I left work determined to find the problem on Monday. I am book marking this so I can go through it when I go back. Thank you computer whiz. It's tough when you have a job you don't have the experience for.:shrug: Thanks.
|
Crazy Guggenheim
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 05:09 PM
Response to Reply #7 |
| 10. Ok. Are you connected to a *Proxy Server*? Also, I have a W2K Pro |
|
system here and I'll take a look.
|
LaurenG
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 05:10 PM
Response to Reply #10 |
DS1
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 05:08 PM
Response to Original message |
| 9. Put the IP of the PDC in the DNS server settings |
|
Even if it isn't running DNS
|
Crazy Guggenheim
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 05:11 PM
Response to Reply #9 |
| 12. I think you're on to something. |
LaurenG
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 05:20 PM
Response to Reply #9 |
| 13. Ok IP in the DNS setting of the "workgroup" computer |
|
Edited on Fri Nov-04-05 05:37 PM by OhioBlues
I'll try it. I wish I'd stayed at work I bet I could have fixed this. Muchas gracias senor.
|
CatholicEdHead
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 07:26 PM
Response to Original message |
|
It may be that simple as a bad Network Card.
|
LaurenG
(1000+ posts)
Send PM |
Profile |
Ignore
|
Fri Nov-04-05 07:32 PM
Response to Reply #14 |
| 15. Yes I believe it is working |
|
I'm going to learn exactly whats wrong with it on Monday, unless of course none of the things suggested here work. Then I'll ask my boss to hire a PROFESSIONAL instead of making me do it. Thank you for the suggestion.
|
DU
AdBot (1000+ posts) |
Sun Mar 29th 2026, 10:10 PM
Response to Original message |