back to drawing board

  • Thread starter Thread starter bill s via WinServerKB.com
  • Start date Start date
B

bill s via WinServerKB.com

I was having trouble joining a PC to a DC until I removed Norton completely
fom the computer. It then joined Okay. I put the PC back in a workgroup just
to see if I could re-join the new domain and it would not!! The message after
the account sign-in is 'network name cannot be found".
I can ping the DC by IP Okay
I can ping the DC by name Okay
Client DNS pointing to DC IP
I flushed DNS
The DC is a new domain with no other PC's on. It's a lab network.
This is really strange..........
Anyone have anymore suggestions?

Thanks
Bill
 
How about pinging by FQDN (for example, DCname.yournetwork.local or
whatever)?

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
 
Richard said:
How about pinging by FQDN (for example, DCname.yournetwork.local or
whatever)?
I was having trouble joining a PC to a DC until I removed Norton completely
fom the computer. It then joined Okay. I put the PC back in a workgroup
[quoted text clipped - 12 lines]
Thanks
Bill

Richard
I can ping by IP
I can ping by domain name
I can ping by FQDN...all with success

ipconfig /fix =
Computer name: server1
DNS host name: Server1.bgcmeriden.org
DNS test: passed
Pass: all the DNS entires for DC are registered with DNS server
Everything else seemed to pass also
Any ideas form here??

Thanks
Bill
 
Not unless you've got another firewall program on there - from what I can
see it should be working.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


bill s via WinServerKB.com said:
Richard said:
How about pinging by FQDN (for example, DCname.yournetwork.local or
whatever)?
I was having trouble joining a PC to a DC until I removed Norton
completely
fom the computer. It then joined Okay. I put the PC back in a workgroup
[quoted text clipped - 12 lines]
Thanks
Bill

Richard
I can ping by IP
I can ping by domain name
I can ping by FQDN...all with success

ipconfig /fix =
Computer name: server1
DNS host name: Server1.bgcmeriden.org
DNS test: passed
Pass: all the DNS entires for DC are registered with DNS server
Everything else seemed to pass also
Any ideas form here??

Thanks
Bill
 
Richard said:
Not unless you've got another firewall program on there - from what I can
see it should be working.
[quoted text clipped - 21 lines]
Thanks
Bill
Richard.....that's not good news. :>)
Is it possible something could be in the registry as a resultant of a program
like Norton that used to be installed??
I am using an old copy of Windows2K and have XP pro with SP2. I thought that
might have something to do with it but the first time I tried this it worked
fine. Actually, it worked fine for the first 20 computers. With 2 to go I
started to get that error message. BUT...that was also a few installation
tries ago and I cannot fathom something still hanging around.
Anyway.....any more advice you can come with will be greatly appreciated.
I'll keep ya posted

Regards
Bill
 
hi

You could try running the removal tools for whatever norto product uyou had installed, personnaly I would touch any of their products with a barge pole, well any of the @iternet security@ s/w apart you maybe the corporate server but the rest .......

I have had the misfortune of settig it up/configurig it/torubleshooting it as part of work and its no fun. Dont know which Norton you had ionstalled but ther is a different removal tool for pre 2003 and 2004 onwards for Norton Anntivrus and norton internet security kinda products

pre is called RnisUPG.exe and rNAV2003.exe

post 2004 is symNRT.exe

Norton can certainly cause the seemingly "unexplained behaviuor " like above

Hope you fix it

Si
 
Back
Top