Vista cannot connect to network share but reach internet

On Wed, 9 Jan 2008 07:28:04 -0800, Daniel30 <Daniel30@discussions.microsoft.com>
wrote:

>I have a laptop with Vista business edition connected to a domain.
>I have installed it with no problems.
>Now when my user got it she cannot reach the shares or connect to the server
>with \\servername\share
>I get the message 0x80070035
>I logged in with my domain admin user but i have the same problem.
>
>We can reach websites and ping the servers works.
>What can I do to solve the problem.
>I have bought 4 laptops but only 1 have this problem.

The "0x80070035" is the equivalent of an "error 53", which says "name not
found". Generally, this will be a misconfigured or overlooked personal
firewall, blocking network traffic that locates the computer in question. What
anti-virus product do you use?
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/0...ther-help.html

You can probably diagnose the problem, using logs from "browstat status",
"ipconfig /all", "net config server", and "net config workstation", from the
problem computer, and two other computers. Read this article, and linked
articles, and follow instructions precisely (Download browstat, and note how to
start a Vista command window!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/0...#AskingForHelp

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.

I had Symantec Endpoint Protection installed and it was that that caused the
problem :S
ffs...i will install symantec antivirus 11 instead.
thanks for all help guys

"Chuck [MVP]" wrote:

> On Wed, 9 Jan 2008 07:28:04 -0800, Daniel30 <Daniel30@discussions.microsoft.com>
> wrote:
>

> >I have a laptop with Vista business edition connected to a domain.
> >I have installed it with no problems.
> >Now when my user got it she cannot reach the shares or connect to the server
> >with \\servername\share
> >I get the message 0x80070035
> >I logged in with my domain admin user but i have the same problem.
> >
> >We can reach websites and ping the servers works.
> >What can I do to solve the problem.
> >I have bought 4 laptops but only 1 have this problem.

>
> The "0x80070035" is the equivalent of an "error 53", which says "name not
> found". Generally, this will be a misconfigured or overlooked personal
> firewall, blocking network traffic that locates the computer in question. What
> anti-virus product do you use?
> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
> http://nitecruzr.blogspot.com/2005/0...ther-help.html
>
> You can probably diagnose the problem, using logs from "browstat status",
> "ipconfig /all", "net config server", and "net config workstation", from the
> problem computer, and two other computers. Read this article, and linked
> articles, and follow instructions precisely (Download browstat, and note how to
> start a Vista command window!):
> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
> http://nitecruzr.blogspot.com/2005/0...#AskingForHelp
>
> --
> Cheers,
> Chuck, MS-MVP 2005-2007 [Windows - Networking]
> http://nitecruzr.blogspot.com/
> Paranoia is not a problem, when it's a normal response from experience.
> My email is AT DOT
> actual address pchuck mvps org.
>

On Thu, 10 Jan 2008 00:29:00 -0800, Daniel30
<Daniel30@discussions.microsoft.com> wrote:

>"Chuck [MVP]" wrote:
>

>> On Wed, 9 Jan 2008 07:28:04 -0800, Daniel30 <Daniel30@discussions.microsoft.com>
>> wrote:
>>

>> >I have a laptop with Vista business edition connected to a domain.
>> >I have installed it with no problems.
>> >Now when my user got it she cannot reach the shares or connect to the server
>> >with \\servername\share
>> >I get the message 0x80070035
>> >I logged in with my domain admin user but i have the same problem.
>> >
>> >We can reach websites and ping the servers works.
>> >What can I do to solve the problem.
>> >I have bought 4 laptops but only 1 have this problem.

>>
>> The "0x80070035" is the equivalent of an "error 53", which says "name not
>> found". Generally, this will be a misconfigured or overlooked personal
>> firewall, blocking network traffic that locates the computer in question. What
>> anti-virus product do you use?
>> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
>> http://nitecruzr.blogspot.com/2005/0...ther-help.html
>>
>> You can probably diagnose the problem, using logs from "browstat status",
>> "ipconfig /all", "net config server", and "net config workstation", from the
>> problem computer, and two other computers. Read this article, and linked
>> articles, and follow instructions precisely (Download browstat, and note how to
>> start a Vista command window!):
>> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
>> http://nitecruzr.blogspot.com/2005/0...#AskingForHelp

>I had Symantec Endpoint Protection installed and it was that that caused the
>problem :S
>ffs...i will install symantec antivirus 11 instead.
>thanks for all help guys

8-)

SEP again. Instead of another Symantec product, you might consider a free
antivirus like Avast or AVG.

Thanks for the update.

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.

I've encountered the same problem this last week with Vista 32 and 64
Business, but I finally isolated the cause as Symantec Endpoint Security
11.x. When I disabled the Network Threat option (if I have the correct
name), the problem went away. We installed on December 19th, and with
everyone being away for vacation, it didn't show up until they got back.
It took me a while, because I figured it was new Windows updates that
caused it.

XP clients had no problem. Just the Vista ones running Endpoint
Security.

Hope this fixes your problem.


--
flinthead