robert pearman 
United Kingdom
Member since
2/23/2007
Platinum Membership
Posts: 1771
 |
| 5/03/2007 04:15 PM |
|
can you give us a bit more detail?
can you go through your manual process step by step, and tell us exactly what your doing at each step.
"access not allowed" is a little tricky to diagnose :P |
|
|
|
|
|
Stan Guinn
Texas, USA
Member since
12/29/2005
Platinum Membership
Posts: 1914
|
| 5/03/2007 04:32 PM |
|
Posted By Christian Calomme on 5/03/2007 09:13 AM
Once the config was done, I connect a brand new PC to the domain and log in with my name.
I then received my new mails from exchange, import the pst items onto exchange and import the main data from an external disk to the server.
After that, I was ready to work (and I did)
When I try to connect the old PCs (including my old one) I receive the erreor message.
Again thank you for your help.
|
|
|
|
|
|
Eriq Neale
Texas, USA
Member since
5/3/2005
Microsoft MVP
Posts: 2114
|
| 5/03/2007 10:32 PM |
|
Actually, if the machines are still thinking they're in the old domain, this is going to cause problems. You really need to join the workstations to a Workgroup manually to clear out all old domain pieces on the workstations. Then make sure you're logged in with the local machine administrator account and try to join manually. IIRC, you're not going to be able to use Connect Computer on these workstations since they had previously been in a domain. You'll have to join them manually and copy profile information over by hand. ConnectComputer is great on new workstations that have never belonged to a domain, not so much on those that have belonged to other domains.
-Eriq
|
|
Eriq Neale - Small Business Specialist, SBS MVP, Mac Guru
EON Consulting LLC www.eonconsulting.net
Lead Author of Windows Small Business Server 2008 Unleashed
In bookstores December 10, available for pre-order now
Listen to eOnCall at AIRtunZ or visit www.eoncall.com. |
|
|
|
Christian Calomme
Belgium
Member since
3/27/2005
Platinum Membership
Posts: 89
|
| 5/04/2007 02:49 PM |
|
I've rebooted on safe mode on a workgroup, deleted or renamed all the old domain stuff, then reboot again with a local user account.
After that, I first try connectcomputer, no success.
So I go to the manual process:
-change from workgroup to the new domain name
-give a user login and PW to join the domain (for example, the domain admin)
after a long time, I receive the message (freely translated from french): error during junction to domain XXX access denied
I'm sure that the login and PW are corrects because when I try with another user or with a wrong PW I receive a "Wrong username/password" message.
|
|
|
|
|
|
Stan Guinn
Texas, USA
Member since
12/29/2005
Platinum Membership
Posts: 1914
|
| 5/04/2007 03:38 PM |
|
| The ipconfig/all of the woprkstation you attached in your first post, was that from the workstation that successfully joined? If so, can you post an ipconfir/all of the workstation that won't join. |
|
|
|
|
|
Christian Calomme
Belgium
Member since
3/27/2005
Platinum Membership
Posts: 89
|
| 5/04/2007 03:58 PM |
|
No, I'm afraid... It was from one workstation that could'nt join the domain.
If that can help, I join the Ipconfig from the brand new workstation that I connect first to the domain (It's a Vista one)
|
 Attachment: 15458077829.txt
|
|
|
|
|
Eriq Neale
Texas, USA
Member since
5/3/2005
Microsoft MVP
Posts: 2114
|
| 5/05/2007 04:31 AM |
|
Christian -
Are you absolutely sure that Windows Server 2003 Service Pack 2 is NOT installed on the SBS box? The IP information for the workstations looks correct, so I don't think it's a networking configuration problem that's keeping you from joining the domain manually. The only other time I've seen something remotely like this (when SP2 isn't involved) was with a Broadcom NIC on the box. I think they've finally released driver updates that get around the particular problems people were having.
-Eriq |
|
Eriq Neale - Small Business Specialist, SBS MVP, Mac Guru
EON Consulting LLC www.eonconsulting.net
Lead Author of Windows Small Business Server 2008 Unleashed
In bookstores December 10, available for pre-order now
Listen to eOnCall at AIRtunZ or visit www.eoncall.com. |
|
|
|
Eriq Neale
Texas, USA
Member since
5/3/2005
Microsoft MVP
Posts: 2114
|
| 5/05/2007 04:34 AM |
|
| And now that I look back at your ipconfig from the server, I see that you do have a Broadcom NIC on the local connection. Definitely check to make sure that you've got the latest deivers loaded for that. |
|
Eriq Neale - Small Business Specialist, SBS MVP, Mac Guru
EON Consulting LLC www.eonconsulting.net
Lead Author of Windows Small Business Server 2008 Unleashed
In bookstores December 10, available for pre-order now
Listen to eOnCall at AIRtunZ or visit www.eoncall.com. |
|
|
|
Christian Calomme
Belgium
Member since
3/27/2005
Platinum Membership
Posts: 89
|
| 5/07/2007 05:42 PM |
|
Hello Guys,
Sorry for the long time since my last post, but I had the feeling that I running in a circle with no solution...
In the mean time, I do some modifications : uninstall the two Nics on the server, reinstall both but assign the LAN side at the Intel Nic and the WAN side to the Broadcom.
Then rerun the Connect to Internet Wizard and verify the DHCP service on the server
After that, two of four PC can be connected into the domain with connectcomputer.
But that mean's also that two cannot be connected and I don't figure why as at this time I assume that we are sure that all is fine on the server side.
You have to know that in the past, all the PC are even on english version, even on MULI english/french, the server was an english one and now the server is a french version.
What I've seen for one PC is a message saying that the previous version was in english and the new one will be in french, I accept and all was fine, the PC is on the domain.
Any idea to go ahead?
|
|
|
|
|
|
Svein Ivar Brekken
Norway
Member since
7/11/2007
Registered Users
Posts: 1
|
| 7/11/2007 06:03 PM |
|
| Try to disable Wireless, BT -nettwork... Only use the cable.. |
|
|
|
|
|
Christian Calomme
Belgium
Member since
3/27/2005
Platinum Membership
Posts: 89
|
| 7/19/2007 03:58 PM |
|
Hello Svein and welcome abroad  That was already done with no more result...
|
|
|
|
|
|
Stan Guinn
Texas, USA
Member since
12/29/2005
Platinum Membership
Posts: 1914
|
| 7/20/2007 05:14 AM |
|
->Thank you for your advice, but on the workstation it is a linksys NIC and I have the very same issue with all the 4 PC witch I try to reconnect.<-
Yes, but the Broadcom NIC is on the server. And it is Broadcom NICs that have been giving everyone trouble. And it appears to be the Internal NIC which would explain why none of your PCs can communicate with the server.
|
|
|
|
|
|