Re: \\pc name not accessible but \\pc name.Domain is accessible Server 2003
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 25 Jan 2007 09:34:32 -0500
In news:1169690252.090949.114020@xxxxxxxxxxxxxxxxxxxxxxxxxxx,
ace.wilhelm@xxxxxxxxxxxxxxxxx <ace.wilhelm@xxxxxxxxxxxxxxxxx> typed:
HI All,
Here is my problem.
I have recently upgrade from NT4 to server 2003.
The upgrade went well except, i am unable to access any of the share
by accessing the pc using \\pc name.
All the shares are available to me when i use the following
\\pc-name.domain
ie: \\home-pc -> throws \\pc-name not accessible
\\home.pc.homenetwork --> able to connect.
Does anyone have any idea why this may occur.
Thanks
Browsing requires NetBios over TCP/IP - and if you want to use that, you
should also use WINS (hybrid node / 0x8). In fact, if you were using NT
before, I have to imagine you were using WINS then or you'd have had a whole
host of problems. I'd also disable the computer browser service on all the
workstations.
.
- Follow-Ups:
- Re: \\pc name not accessible but \\pc name.Domain is accessible Server 2003
- From: ace . wilhelm
- Re: \\pc name not accessible but \\pc name.Domain is accessible Server 2003
- References:
- \\pc name not accessible but \\pc name.Domain is accessible Server 2003
- From: ace . wilhelm
- \\pc name not accessible but \\pc name.Domain is accessible Server 2003
- Prev by Date: Re: \\pc name not accessible but \\pc name.Domain is accessible Server 2003
- Next by Date: Terminal Services?
- Previous by thread: Re: \\pc name not accessible but \\pc name.Domain is accessible Server 2003
- Next by thread: Re: \\pc name not accessible but \\pc name.Domain is accessible Server 2003
- Index(es):
Relevant Pages
|
