WinXP won't stay connected

[Brian Lynn]

I have a peer-peer network consisting of a Win2K Server
box and 2 WinXP Home edition boxes. I am using a linksys
router as a DHCP server. So far it has been simple to
setup. I am MS-MCP and have a little expereince so its
not that hard. The network goes together no problem.
Files are shared, internet is no problem, and the printer
is networked and shared across the network. That was all
easy. Now the issue: and hour after I have it all
connected it all DISconnects. No settings change anI can
still ping across the network from any box to any box and
get a response. But WinXP for some reason will not stay
connected on any of the network shares. I have never had
this issue before. Am I missing something? Or does WinXP
just suck?

 

[Mike Clay]

You are using your router for dhcp assignment - if you go to a command
prompt, try to access one of your mapped drives (type in j: or whatever),
after a pause you will likely see AN ATTEMPT HAS BEEN MADE TO COMPROMISE
SECURITY. CANT CONTACT THE SERVER THAT AUTHENTICATE YOU...blah blah like
that....

For xp on win 2k, what i've found, is to use the DHCP on the win2k box, and
make sure that your DNS points to the win2k box ONLY. The win2k box can
have a 'forwarder' on its DNS server setup to an outside dns source, but if
you have any outside dns on your clients, you will get the error after 1-3
hours...

also make sure the dns 'suffix' is matching on all of the workstations,
which matches the win2k server.

 

[Brian Lynn]

Well this is a really complicated solution to what seems
to be a really simple issue. I have a mixed Xp 2k network
at home and i've not had to do any of this monkying
around to get it to work... but I can try what you
suggest. Do I leave the default gateway set to the router
IP? By doing what you're suggesting wouldn't it be easier
for the Win2K to act as router, DHCP, and just get rid of
the linksys box?


And abou this first paragraph:
******************************

-----Original Message-----
You are using your router for dhcp assignment - if you go to a command
prompt, try to access one of your mapped drives (type in j: or whatever),
after a pause you will likely see AN ATTEMPT HAS BEEN MADE TO COMPROMISE
SECURITY. CANT CONTACT THE SERVER THAT AUTHENTICATE YOU...blah blah like
that....

********************************

I have no mapped network drives. The win2k box isn't
really acting as a server. it holds some shared docs in a
shared network folder. Thats about it. The rest is just
for the OS to run the box... they do quickbooks on it
usually... So I have never seen the error message you are
talking about.. basically the computers just all drop out
of My Network Places as even being available to talk to.
This is a super low-key network.

But you're sayin that cause I am using an external DNS
server I will continue to loose contact? What if I
eliminate the need for DHCP? I only have 3 computers... I
can set them up with static IP no problem... will solve
the issue?

 

[Graham]

Bryan, From another NG (win2000 networking) ref. these problems, it suggests
checking articles (I assume in MS-KBase)
810907 329170 812397 811492 321169 296264
all relate to Win2K server with XP client issues.

HTH.