When the connection is lost, I can browse all of the files on the XP
workstation from the notebook by typing at a Run line "\\ipaddress\c$.
However, if I type "\\computername\c$ it fails to connect. Both of these
computers are set up properly in AD, can ping each other by name and IP, and
an nslookup of the workstation from the notebook returns all the correct
information. It appears that I can access the workstation normally by name
from other computers on the lan, even at the time it is refusing connections
by name from the laptop. It doesn't appear to be a permission issue since
everything works fine by IP.
Sometimes rebooting the laptop will restore the connection, but not always.
It appears that the problem is with the workstation, not the laptop, so that
makes sense. However, the workstation has no network issues at all, other
than this. These are both relatively new computers, with all the
appropriate patches, current service packs, etc.
This might relate to a problem that several posters in this group have
reported, where laptops connected to SBS networks start working offline for
no apparent reason. Anyone have any idea what this could be?
You very well may be right about SP1, although this seems to have worsened
lately, and we've had SP1 installed for a while now.
"Susan Bradley, CPA aka "Ebitz" SBS Rocks [MVP]" <sbra...@pacbell.net>
wrote in message news:3DD06B47...@pacbell.net...
We are kinda like psychiatrists and bartenders out here....
Dave Nickason wrote:
> With more troubleshooting, I discovered that in addition to being able to
> connect by IP but not by name, I can connect by \\computername.domain.local,
> but not just \\computername. The laptop can connect to every other
> workstation on the network, other than the user's own workstation. And,
> every workstation can connect to the user's workstation, even while the
> laptop can't.
>
> What I did was to run the "Repair" option on the workstation LAN settings,
> and do the same thing on the laptop. This clears all of the cached network
> information. This seems to be working now. I got the procedure for the
> win2k laptop from "Q289256 A Description of the Repair Option on a Local
> Area Network or High-Speed Internet Connection."
>
> Susan, thank you for your help!
>
> "Susan Bradley, CPA aka "Ebitz" SBS Rocks [MVP]" <sbra...@pacbell.net>
> wrote in message news:3DD08A86...@pacbell.net...
What I did was to run the "Repair" option on the workstation LAN settings,
and do the same thing on the laptop. This clears all of the cached network
information. This seems to be working now. I got the procedure for the
win2k laptop from "Q289256 A Description of the Repair Option on a Local
Area Network or High-Speed Internet Connection."
Susan, thank you for your help!
"Susan Bradley, CPA aka "Ebitz" SBS Rocks [MVP]" <sbra...@pacbell.net>
wrote in message news:3DD08A86...@pacbell.net...