Connecting to Win2K domain with WinXP

  • Thread starter Thread starter Aaron Todd
  • Start date Start date
A

Aaron Todd

I am trying to connect to a Windows 2000 domain. When I make the attempt it
brings up the logon screen and I login to the domain. Then it errors and
says, "Windows cannot find the network path."

No matter what way I try to join this is always the error I get.

Please let me know if anyone has seen this and knows whats wrong.

Thanks,

Aaron
 
Hi Aaron-

This sounds like a name resolution problem. May I suggest checking
DNS\WINS\DHCP config on the machine?

--
Thanks,
Richard Moreno
MCSE NT4\2000, MCSA 2000

This posting is provided "AS IS" with no warranties, and confers no
rights.
 
Richard,

Thank you for the extreemly fast reply.

Do you have something in mind that I should look for in DNS\WINS\DHCP? I
have looked at them, but everything looks fine to me. But I'm not an
expert. So let me know if there is somehting I should look espically for.

Thanks again,

Aaron
 
Hey Aaron-

If this XP client receives it's IP info from DHCP and it's the same as any
other client that is working properly then that should be good. If your info
is statically assigned, then as long as your IP info is correct for your
subnet mask and your gateway as well as your DNS addresses that should be
good. Another thing to consider is does this machine have any HOSTS or
LMHOSTS entries? Those are located in %systemroot%\winnt\drivers\etc. Also,
can you logon to the machine with a local account? If so, are you able to
ping other servers on the network?

--
Thanks,
Richard Moreno
MCSE NT4\2000, MCSA 2000

This posting is provided "AS IS" with no warranties, and confers no
rights.
 
Are all of the entries correct??? Do you use DHCP? if
not, is the IP correct, doesit conflict with anyhting else
on the network?? Is the DNS server entry correct? If the
default gateway correct? Do you use WINS on your
network? if so, is that entry correct.

Thats what he meant by checking.
 
Richard,

My XP client does recieve its IP from DHCP. My Win2K server is at
10.255.11.9. The client is at 10.255.11.1. The subnet for both machines is
255.0.0.0. The gateway for both machines is 10.255.0.0. DNS on the XP
client is set through DHCP. Both my ISP's address's are in there and also
the address(10.255.11.9) of my DNS server running on the Win2K server. I
never set up any HOSTS or LMHOSTS entries so I would say no about them. I
can logon using a local account and am able to ping other servers and
devices on the network.


Let me know if there is anything else I should check.

Thanks agian,

Aaron
 
Hi Aaron-

I wasn't aware this is a home network, is that right? Anyways, may I suggest
that you alter your gateway as an address of x.x.x.0 is invalid. Try
configuring it as x.x.x.1 for your entire LAN and then routing should work
correctly.

--
Thanks,
Richard Moreno
MCSE NT4\2000, MCSA 2000

This posting is provided "AS IS" with no warranties, and confers no
rights.
 
Richard,

More or less, it is a "home network". Actually its a small buisness which
has less than 30 computers. I am aware of the invalid gateway address, but
it was set before I took over and that is one of the things I am working on
with this Win2K server. My gateway is not a computer though. It is a
standalone SonicWall system. Will that really affect the communication
between the XP client and the Win2K Server? Do I need to somehow make the
server a gateway for the clients to connect to?

Thanks,

Aaron
 
Hey Aaron-

I'm a little baffled as to the network configuration you're now supporting
however if all the other clients can communicate with the server I'm forced
to say you should investigate changing the gateway address for your sonic
wall or an easier fix would be to add an entry to your LMHOSTS file
containing the server address\domain.

--
Thanks,
Richard Moreno
MCSE NT4\2000, MCSA 2000

This posting is provided "AS IS" with no warranties, and confers no
rights.
 
Richard,

I figured it out. I got to poking around in my servers network settings and
I saw that the Microsoft Network Client was disabled and so was file sharing
for microsoft network. I enabled both of those and now I can connect to the
domain perfectly.

Thanks for your help.

Aaron
 
Back
Top