Problem with connecting to DOMAIN

  • Thread starter Thread starter Ryan
  • Start date Start date
R

Ryan

I am having a issue with my windows 2000 professional, I
get 'network path not found'. I have already did the
online walkthrough from microsoft support, but still get
the same error message. It is Knowledge Base Article
285182. One thing however, I could not find my WINS server
IP address. when I do a IPCONFIG /ALL it has wins proxy
enabled as no. I did however try putting in our main
server IP address, still came back with the same problem.
If anyone can assist please contact me, I need to be able
to connect to my domain to install our companys new
Blackberry Exchange Server. THANKS
 
Ryan said:
I am having a issue with my windows 2000 professional, I
get 'network path not found'. I have already did the
online walkthrough from microsoft support, but still get
the same error message. It is Knowledge Base Article
285182. One thing however, I could not find my WINS server
IP address. when I do a IPCONFIG /ALL it has wins proxy
enabled as no.

What is the server OS version? Do you need WINS for some reason?
Is WINS installed on your server, and DHCP set up to hand out the IP address
and 0x8 for node type to clients?

More importantly, is DNS set up so that all clients & servers use only the
internal DNS server IP, with forwarders to your ISP's SMTP servers set up on
the internal DNS server?



I did however try putting in our main
 
Have you checked that the PRIMARY domain server is entered into
the LMHOSTS file ?

"Lanwench [MVP - Exchange]"
 
Why would someone use an LMHOSTS file in this case?

its said:
Have you checked that the PRIMARY domain server is entered into
the LMHOSTS file ?

"Lanwench [MVP - Exchange]"
What is the server OS version? Do you need WINS for some reason?
Is WINS installed on your server, and DHCP set up to hand out the IP
address
and 0x8 for node type to clients?

More importantly, is DNS set up so that all clients & servers use
only the internal DNS server IP, with forwarders to your ISP's SMTP
servers set up on
the internal DNS server?



I did however try putting in our main
 
Admittedly we've never needed it until recently.
The company I work for has a MS network, and a secondary domain
controller, and there are 50 or so similar companies around the uk with
the same setup.
Our users can logon to the domain from various OS versions: 98,NT,XP,2000
and very rarely have problems, but very occasionally one PC cannot be logged
on
with any account other than a 'local' one.
The error mentions the user account cannot be found, and the 'this computer'
option of the logon screen shows a different computer name: the ip address
followed by 'C', instead of what the computer name actually is.
What we were advised to do was add an entry to the LMHOSTS file
with the PRIMARY domain controller - we have not had any re-occurences
since.

"Lanwench [MVP - Exchange]"
Why would someone use an LMHOSTS file in this case?

its said:
Have you checked that the PRIMARY domain server is entered into
the LMHOSTS file ?

"Lanwench [MVP - Exchange]"
Ryan wrote:
I am having a issue with my windows 2000 professional, I
get 'network path not found'. I have already did the
online walkthrough from microsoft support, but still get
the same error message. It is Knowledge Base Article
285182. One thing however, I could not find my WINS server
IP address. when I do a IPCONFIG /ALL it has wins proxy
enabled as no.

What is the server OS version? Do you need WINS for some reason?
Is WINS installed on your server, and DHCP set up to hand out the IP
address
and 0x8 for node type to clients?

More importantly, is DNS set up so that all clients & servers use
only the internal DNS server IP, with forwarders to your ISP's SMTP
servers set up on
the internal DNS server?



I did however try putting in our main
server IP address, still came back with the same problem.
If anyone can assist please contact me, I need to be able
to connect to my domain to install our companys new
Blackberry Exchange Server. THANKS
 
its said:
Admittedly we've never needed it until recently.
The company I work for has a MS network, and a secondary domain
controller, and there are 50 or so similar companies around the uk
with
the same setup.
Our users can logon to the domain from various OS versions:
98,NT,XP,2000 and very rarely have problems, but very occasionally
one PC cannot be logged on
with any account other than a 'local' one.
The error mentions the user account cannot be found, and the 'this
computer' option of the logon screen shows a different computer name:
the ip address followed by 'C', instead of what the computer name
actually is.
What we were advised to do was add an entry to the LMHOSTS file
with the PRIMARY domain controller - we have not had any re-occurences
since.

LMHOSTS can indeed work just fine, but it seems better to me to resolve the
underlying DNS issues that this points to -if you change DCs, etc., you
don't want to have to update a bunch of local files.
"Lanwench [MVP - Exchange]"
Why would someone use an LMHOSTS file in this case?

its said:
Have you checked that the PRIMARY domain server is entered into
the LMHOSTS file ?

"Lanwench [MVP - Exchange]"
message Ryan wrote:
I am having a issue with my windows 2000 professional, I
get 'network path not found'. I have already did the
online walkthrough from microsoft support, but still get
the same error message. It is Knowledge Base Article
285182. One thing however, I could not find my WINS server
IP address. when I do a IPCONFIG /ALL it has wins proxy
enabled as no.

What is the server OS version? Do you need WINS for some reason?
Is WINS installed on your server, and DHCP set up to hand out the
IP address
and 0x8 for node type to clients?

More importantly, is DNS set up so that all clients & servers use
only the internal DNS server IP, with forwarders to your ISP's SMTP
servers set up on
the internal DNS server?



I did however try putting in our main
server IP address, still came back with the same problem.
If anyone can assist please contact me, I need to be able
to connect to my domain to install our companys new
Blackberry Exchange Server. THANKS
 
Back
Top