I am about to pull my hair out and need some help!

For 3 months now, I've had Verizon FIOS internet service and love it.
However, I'm having a problem with accessing shared folders.

My main PC is XP Pro SP2. I also have a work laptop that is the same
build. The home PC is named "paulpc" and is part of workgroup
"@home". On my work laptop, I login to the local admin account. I
had this exact same setup with my previous ISP and had NO problems
accessing shared folders. But I can't get jack working here.

PAULPC pulls an internal IP of 192.168.1.2. The laptop pulls an IP of
192.168.1.3. From the laptop, I can ping 192.168.1.2 just fine. I
can also just ping PAULPC, and get a reply...so DNS is definitely
working. When I go into My Network Places, I don't see PAULPC. In
fact, the only network that shows up is my work domain (AMER) in
Microsoft Windows Network. I am NOT connecting to this domain
however. I have to run VPN to do that and am not doing that
obviously. As I stated earlier, this worked fine with my previous
ISP. All I did was share the folder and from this same laptop, could
see PAULPC with shared folders underneath it.

I do not have ANY firewalls enabled in XP or any 3rd party program.
The router (Actiontec) has a built in firewall, but I don't see
anything in it that would prevent me from seeing shared folders.

Am I missing something obvious? I tried calling Verizon FIOS and
after holding for 15 minutes, they say they don't support shared
files. WTF?!?!? LOL Even when their website shows in very plain
detail how to set it up.

Thanks a gazillion for any help.

What happens when you type \\PAULPC\SHARENAME in the address bar, SHARENAME
being the name you gave your shared folder?
Regards,
ern.

"paul8agrape" <paul8agrape******.com> wrote in message
news:1183430969.077638.307590@q69g2000hsb.googlegr oups.com...
> I am about to pull my hair out and need some help!
>
> For 3 months now, I've had Verizon FIOS internet service and love it.
> However, I'm having a problem with accessing shared folders.
>
> My main PC is XP Pro SP2. I also have a work laptop that is the same
> build. The home PC is named "paulpc" and is part of workgroup
> "@home". On my work laptop, I login to the local admin account. I
> had this exact same setup with my previous ISP and had NO problems
> accessing shared folders. But I can't get jack working here.
>
> PAULPC pulls an internal IP of 192.168.1.2. The laptop pulls an IP of
> 192.168.1.3. From the laptop, I can ping 192.168.1.2 just fine. I
> can also just ping PAULPC, and get a reply...so DNS is definitely
> working. When I go into My Network Places, I don't see PAULPC. In
> fact, the only network that shows up is my work domain (AMER) in
> Microsoft Windows Network. I am NOT connecting to this domain
> however. I have to run VPN to do that and am not doing that
> obviously. As I stated earlier, this worked fine with my previous
> ISP. All I did was share the folder and from this same laptop, could
> see PAULPC with shared folders underneath it.
>
> I do not have ANY firewalls enabled in XP or any 3rd party program.
> The router (Actiontec) has a built in firewall, but I don't see
> anything in it that would prevent me from seeing shared folders.
>
> Am I missing something obvious? I tried calling Verizon FIOS and
> after holding for 15 minutes, they say they don't support shared
> files. WTF?!?!? LOL Even when their website shows in very plain
> detail how to set it up.
>
> Thanks a gazillion for any help.
>

On Jul 4, 3:58 pm, "ernie" <e...@unspam.co.uk> wrote:
> What happens when you type \\PAULPC\SHARENAME in the address bar, SHARENAME
> being the name you gave your shared folder?
> Regards,
> ern.
>
> "paul8agrape" <paul8agr...******.com> wrote in message
>
> news:1183430969.077638.307590@q69g2000hsb.googlegr oups.com...
>
> > I am about to pull my hair out and need some help!
>
> > For 3 months now, I've had Verizon FIOS internet service and love it.
> > However, I'm having a problem with accessing shared folders.
>
> > My main PC is XP Pro SP2. I also have a work laptop that is the same
> > build. The home PC is named "paulpc" and is part of workgroup
> > "@home". On my work laptop, I login to the local admin account. I
> > had this exact same setup with my previous ISP and had NO problems
> > accessing shared folders. But I can't get jack working here.
>
> > PAULPC pulls an internal IP of 192.168.1.2. The laptop pulls an IP of
> > 192.168.1.3. From the laptop, I can ping 192.168.1.2 just fine. I
> > can also just ping PAULPC, and get a reply...so DNS is definitely
> > working. When I go into My Network Places, I don't see PAULPC. In
> > fact, the only network that shows up is my work domain (AMER) in
> > Microsoft Windows Network. I am NOT connecting to this domain
> > however. I have to run VPN to do that and am not doing that
> > obviously. As I stated earlier, this worked fine with my previous
> > ISP. All I did was share the folder and from this same laptop, could
> > see PAULPC with shared folders underneath it.
>
> > I do not have ANY firewalls enabled in XP or any 3rd party program.
> > The router (Actiontec) has a built in firewall, but I don't see
> > anything in it that would prevent me from seeing shared folders.
>
> > Am I missing something obvious? I tried calling Verizon FIOS and
> > after holding for 15 minutes, they say they don't support shared
> > files. WTF?!?!? LOL Even when their website shows in very plain
> > detail how to set it up.
>
> > Thanks a gazillion for any help.

"Network path not found"...even tho I can ping PAULPC and the IP

"paul8agrape" <paul8agrape******.com> wrote in message
news:1184004248.255022.123870@g4g2000hsf.googlegro ups.com...
> On Jul 4, 3:58 pm, "ernie" <e...@unspam.co.uk> wrote:
> > "paul8agrape" <paul8agr...******.com> wrote in message
> >
> > news:1183430969.077638.307590@q69g2000hsb.googlegr oups.com...
> >
> > > I am about to pull my hair out and need some help!
> >
> > > For 3 months now, I've had Verizon FIOS internet service and love it.
> > > However, I'm having a problem with accessing shared folders.
> >
> > > My main PC is XP Pro SP2. I also have a work laptop that is the same
> > > build. The home PC is named "paulpc" and is part of workgroup
> > > "@home". On my work laptop, I login to the local admin account. I
> > > had this exact same setup with my previous ISP and had NO problems
> > > accessing shared folders. But I can't get jack working here.
> >
> > > PAULPC pulls an internal IP of 192.168.1.2. The laptop pulls an IP of
> > > 192.168.1.3. From the laptop, I can ping 192.168.1.2 just fine. I
> > > can also just ping PAULPC, and get a reply...so DNS is definitely
> > > working. When I go into My Network Places, I don't see PAULPC. In
> > > fact, the only network that shows up is my work domain (AMER) in
> > > Microsoft Windows Network. I am NOT connecting to this domain
> > > however. I have to run VPN to do that and am not doing that
> > > obviously. As I stated earlier, this worked fine with my previous
> > > ISP. All I did was share the folder and from this same laptop, could
> > > see PAULPC with shared folders underneath it.
> >
> > > I do not have ANY firewalls enabled in XP or any 3rd party program.
> > > The router (Actiontec) has a built in firewall, but I don't see
> > > anything in it that would prevent me from seeing shared folders.
> >
> > > Am I missing something obvious? I tried calling Verizon FIOS and
> > > after holding for 15 minutes, they say they don't support shared
> > > files. WTF?!?!? LOL Even when their website shows in very plain
> > > detail how to set it up.
> >
> > > Thanks a gazillion for any help.
>
> > What happens when you type \\PAULPC\SHARENAME in the address bar,
SHARENAME
> > being the name you gave your shared folder?
> > Regards,
> > ern.
> >
> "Network path not found"...even tho I can ping PAULPC and the IP
>
So when you ran a setup program for Verizon on PAULPC, it broke your home
network? The IT dept. at your work may have policies preventing what you
want but you say this change in behaviour was due to a change in ISP?

There is a newsgroup which deals with networking issues to which I will
cross-post this as I don't know enough about these matters to help you.
microsoft.public.windowsxp.network_web
In the mean time, here is a crib from a post in that group which may help:

" Look at logs from
"browstat status" and "ipconfig /all", from each computer, so we can
diagnose
the problem. Read this article, and linked articles, and follow
instructions
precisely (download browstat!):
<http://nitecruzr.blogspot.com/2005/0...k-neighborhood.
html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/0...#AskingForHelp

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]"


Regards,
ern.

On Jul 10, 7:21 am, "ernie" <er...@unspam.co.uk> wrote:
> "paul8agrape" <paul8agr...******.com> wrote in message
>
> news:1184004248.255022.123870@g4g2000hsf.googlegro ups.com...
>
> > On Jul 4, 3:58 pm, "ernie" <e...@unspam.co.uk> wrote:
> > > "paul8agrape" <paul8agr...******.com> wrote in message
>
> > >news:1183430969.077638.307590@q69g2000hsb.googleg roups.com...
>
> > > > I am about to pull my hair out and need some help!
>
> > > > For 3 months now, I've had Verizon FIOS internet service and love it.
> > > > However, I'm having a problem with accessing shared folders.
>
> > > > My main PC is XP Pro SP2. I also have a work laptop that is the same
> > > > build. The home PC is named "paulpc" and is part of workgroup
> > > > "@home". On my work laptop, I login to the local admin account. I
> > > > had this exact same setup with my previous ISP and had NO problems
> > > > accessing shared folders. But I can't get jack working here.
>
> > > > PAULPC pulls an internal IP of 192.168.1.2. The laptop pulls an IP of
> > > > 192.168.1.3. From the laptop, I can ping 192.168.1.2 just fine. I
> > > > can also just ping PAULPC, and get a reply...so DNS is definitely
> > > > working. When I go into My Network Places, I don't see PAULPC. In
> > > > fact, the only network that shows up is my work domain (AMER) in
> > > > Microsoft Windows Network. I am NOT connecting to this domain
> > > > however. I have to run VPN to do that and am not doing that
> > > > obviously. As I stated earlier, this worked fine with my previous
> > > > ISP. All I did was share the folder and from this same laptop, could
> > > > see PAULPC with shared folders underneath it.
>
> > > > I do not have ANY firewalls enabled in XP or any 3rd party program.
> > > > The router (Actiontec) has a built in firewall, but I don't see
> > > > anything in it that would prevent me from seeing shared folders.
>
> > > > Am I missing something obvious? I tried calling Verizon FIOS and
> > > > after holding for 15 minutes, they say they don't support shared
> > > > files. WTF?!?!? LOL Even when their website shows in very plain
> > > > detail how to set it up.
>
> > > > Thanks a gazillion for any help.
>
> > > What happens when you type \\PAULPC\SHARENAME in the address bar,
> SHARENAME
> > > being the name you gave your shared folder?
> > > Regards,
> > > ern.
>
> > "Network path not found"...even tho I can ping PAULPC and the IP
>
> So when you ran a setup program for Verizon on PAULPC, it broke your home
> network? The IT dept. at your work may have policies preventing what you
> want but you say this change in behaviour was due to a change in ISP?
>
> There is a newsgroup which deals with networking issues to which I will
> cross-post this as I don't know enough about these matters to help you.
> microsoft.public.windowsxp.network_web
> In the mean time, here is a crib from a post in that group which may help:
>
> " Look at logs from
> "browstat status" and "ipconfig /all", from each computer, so we can
> diagnose
> the problem. Read this article, and linked articles, and follow
> instructions
> precisely (download browstat!):
> <http://nitecruzr.blogspot.com/2005/0...etwork-neighbo....
> html#AskingForHelp>http://nitecruzr.blogspot.com/2005/0...etwork-neighbo...
>
> --
> Cheers,
> Chuck, MS-MVP 2005-2007 [Windows - Networking]"
>
> Regards,
> ern.

Okay...here is the info after running the requested tests. Keep in
mind...PAULPC is my primary home PC and W2VZR05D03 is my work laptop.
While my laptop is not seeing the file shares on PAULPC, it is NOT in
the same workgroup (HOME) which was NOT a problem at my last
residence. I could see file shares on my home PC there...nothing has
changed on the laptop since.

Also, I spent some time on the phone with Verizon FIOS support. I
didn't have NETBIOS enabled (thought I did), so that was enabled.
So...I don't know why it is showing disabled in the PAULPC IPCONFIG
below. What's strange is I can see the shares on PAULPC from PAULPC
by going \\paulpc\ but NOT using the IP \\192.168.1.2\. The laptop
(192.168.1.3) can ping PAULPC and 192.168.1.2 successfully...but it
cannot see any shares...which I'm guessing is because it isn't seeing
NETBIOS enabled on this machine.

=========PAULPC IPCONFIG=========
Windows IP Configuration

Host Name . . . . . . . . . . . : paulpc
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : HOME


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : HOME
Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller
Physical Address. . . . . . . . . : 00-50-8D-DB-00-C1
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Disabled
Lease Obtained. . . . . . . . . . : Saturday, July 21, 2007
5:46:38 PM
Lease Expires . . . . . . . . . . : Sunday, July 22, 2007
5:46:38 PM

=========PAULPC NETCONFIG=========
Server Name \\PAULPC
Server Comment

Software version Windows 2002
Server is active on
NwlnkIpx (00508ddb00c1)
NwlnkNb (00508ddb00c1)


Server hidden No
Maximum Logged On Users 10
Maximum open files per session 16384

Idle session time (min) 15
The command completed successfully.

Computer name \\PAULPC
Full Computer name paulpc
User name Paul

Workstation active on
NwlnkNb (00508DDB00C1)

Software version Windows 2002

Workstation domain HOME
Workstation Domain DNS Name (null)
Logon domain PAULPC

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.

=========PAULPC BROWSTAT=========
Status for domain HOME on transport \Device\NwlnkNb
Browsing is active on domain.
Master name cannot be determined from GetAdapterStatus. Using \
\PAULPC
Master browser is running build 2600
1 backup servers retrieved from master PAULPC
\\PAULPC
There are 1 servers in domain HOME on transport \Device\NwlnkNb
There are 1 domains in domain HOME on transport \Device\NwlnkNb


Status for domain HOME on transport \Device\NwlnkIpx
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

=========W2VZR05D03 IPCONFIG=========
Windows IP Configuration

Host Name . . . . . . . . . . . . : w2vzr05d03
Primary Dns Suffix . . . . . . . : amer.corp.eds.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : amer.corp.eds.com
HOME
corp.eds.com
eds.com

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx
Gigabit Controller
Physical Address. . . . . . . . . : 00-14-22-B4-C0-42

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : HOME
Description . . . . . . . . . . . : Intel(R) PRO/Wireless
2200BG Network Connection
Physical Address. . . . . . . . . : 00-13-CE-35-A1-DD
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Saturday, July 21, 2007
5:40:10 PM
Lease Expires . . . . . . . . . . : Sunday, July 22, 2007
5:40:09 PM

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Bluetooth Device (Personal
Area Network)
Physical Address. . . . . . . . . : 00-10-C6-96-88-FA

=========W2VZR05D03 NETCONFIG=========
Server Name \\W2VZR05D03
Server Comment

Software version Windows 2002
Server is active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{0AEE7EBB-4A4C-47C8-9F84-C193757BD3EE} (0013ce35a1dd)


Server hidden No
Maximum Logged On Users 10
Maximum open files per session 16384

Idle session time (min) 15
The command completed successfully.

Computer name \\W2VZR05D03
Full Computer name w2vzr05d03.amer.corp.eds.com
User name vzr05d

Workstation active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{0AEE7EBB-4A4C-47C8-9F84-C193757BD3EE} (0013CE35A1DD)

Software version Windows 2002

Workstation domain AMER
Workstation Domain DNS Name amer.corp.eds.com
Logon domain W2VZR05D03

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.

=========W2VZR05D03 BROWSTAT=========
Status for domain AMER on transport \Device
\NetBT_Tcpip_{0AEE7EBB-4A4C-47C8-9F84-C193757BD3EE}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

On Sat, 21 Jul 2007 16:17:03 -0700, paul8agrape
<paul8agrape******.com> wrote:

>Also, I spent some time on the phone with Verizon FIOS support. I
>didn't have NETBIOS enabled (thought I did), so that was enabled.
>So...I don't know why it is showing disabled in the PAULPC IPCONFIG
>below. What's strange is I can see the shares on PAULPC from PAULPC
>by going \\paulpc\ but NOT using the IP \\192.168.1.2\. The laptop
>(192.168.1.3) can ping PAULPC and 192.168.1.2 successfully...but it
>cannot see any shares...which I'm guessing is because it isn't seeing
>NETBIOS enabled on this machine.

Paul:

I'm no guru, but I'll throw a few things at you.

First, there are some Verizon support newsgroups you can get to if you
use VZ's newsservers. Email me for details. But second, I doubt this
has anything at all to do with Verizon. As long as the router lets you
ping from system to system, the router is passing traffic. I don't
think the Actiontec has any capabilities to block internal traffic
between systems otherwise.

So, it's likely a coincidence and something else has changed that is
preventing networking. I'd be inclined to finger a change on the work
machine, perhaps some global configuration change they implemented.

The reason you can see the shares with the MS name, as opposed to by
the IP address, would be that sharing over the MS software is working,
but sharing over IP is not working. So, you can still ping (IP) but
you can't share (MS sharing over IP, for lack of a better term).

Have you tried changing them to be in the same workgroup? I've seen
some "interesting" things when machines were not in the same workgroup
in terms of sharing. Also, it looks like the laptop is doing a domain
login. If paulpc is not in the domain, it would not be entitled to see
anything in the domain (i.e. anything on the laptop).

Actually, the problem appears to be ONLY on my main PAULPC computer
and not with Verizon or the work laptop. Just now, I pulled out my
old linksys router and plugged both machines into it. This is the
router that worked just fine at my last residence. Both PCs are able
to ping each other, but I can't even access MY OWN SHARES on
PAULPC. ??? I go to My Computer and type in \\paulpc and see all the
shares on my computer. But when I go to open one, I get "\\paulpc
\downloads is not accessible. You might not have permission to use
this network resource". I also can't access it by the IP name ON MY
OWN PC.

This, of course, makes no sense. I am the administrator of this PC.
That I'm 100% positive of. The shared folder also has Sharing and
Security setup correctly. Again, this is a share that worked just
fine at my last residence and I've done absolutely nothing to change
it. NETBIOS is still disabled.

So it certainly does appear that the biggest problem is on THIS
COMPUTER ONLY. So the questions now are 1) How can NETBIOS be showing
as disabled when I am 100% absolutely, positively sure that it IS
enabled. 2) And why would I not have access to my own shares on my
own PC? Obviously something has changed in the network settings but
hell if I know what it is.

On Jul 23, 8:34 am, +Bob+ <uctra...@ultranet.com> wrote:
> On Sat, 21 Jul 2007 16:17:03 -0700, paul8agrape
>
> <paul8agr...******.com> wrote:
> >Also, I spent some time on the phone with Verizon FIOS support. I
> >didn't have NETBIOS enabled (thought I did), so that was enabled.
> >So...I don't know why it is showing disabled in the PAULPC IPCONFIG
> >below. What's strange is I can see the shares on PAULPC from PAULPC
> >by going \\paulpc\ but NOT using the IP \\192.168.1.2\. The laptop
> >(192.168.1.3) can ping PAULPC and 192.168.1.2 successfully...but it
> >cannot see any shares...which I'm guessing is because it isn't seeing
> >NETBIOS enabled on this machine.
>
> Paul:
>
> I'm no guru, but I'll throw a few things at you.
>
> First, there are some Verizon support newsgroups you can get to if you
> use VZ's newsservers. Email me for details. But second, I doubt this
> has anything at all to do with Verizon. As long as the router lets you
> ping from system to system, the router is passing traffic. I don't
> think the Actiontec has any capabilities to block internal traffic
> between systems otherwise.
>
> So, it's likely a coincidence and something else has changed that is
> preventing networking. I'd be inclined to finger a change on the work
> machine, perhaps some global configuration change they implemented.
>
> The reason you can see the shares with the MS name, as opposed to by
> the IP address, would be that sharing over the MS software is working,
> but sharing over IP is not working. So, you can still ping (IP) but
> you can't share (MS sharing over IP, for lack of a better term).
>
> Have you tried changing them to be in the same workgroup? I've seen
> some "interesting" things when machines were not in the same workgroup
> in terms of sharing. Also, it looks like the laptop is doing a domain
> login. If paulpc is not in the domain, it would not be entitled to see
> anything in the domain (i.e. anything on the laptop).