If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
can't browse network accessed via VPN
I'm connecting to a network over a VPN. the VPN is hosted by a machine
running server 2003. it's also running a WINS server. the machine is a stand-alone server. on the vpn client machine, i get the WINS address of the WINS server correctly and i can ping internal machines using netbios names. however, i cannot browse the network using the vpn client. when i click "view workgroup computers", i get the error: workgroup is not accessible. you might not have permissions to use this network resource. the vpn client is running xp pro. -- Gary Roach ADB Services |
Ads |
#2
|
|||
|
|||
can't browse network accessed via VPN
Do the workgroup names match? Is the network you connect to a Domain or
just a workgroup? -- Phillip Windell [MCP, MVP, CCNA] www.wandtv.com "Gary Roach" wrote in message ... I'm connecting to a network over a VPN. the VPN is hosted by a machine running server 2003. it's also running a WINS server. the machine is a stand-alone server. on the vpn client machine, i get the WINS address of the WINS server correctly and i can ping internal machines using netbios names. however, i cannot browse the network using the vpn client. when i click "view workgroup computers", i get the error: workgroup is not accessible. you might not have permissions to use this network resource. the vpn client is running xp pro. -- Gary Roach ADB Services |
#3
|
|||
|
|||
can't browse network accessed via VPN
If you don't have a domain in either location you will not be
able to get this to work. You cannot browse remote workgroups without the presence of a DMB or domain master browser. The PDC or PDC emulator (W2k or higher) by default is always the DMB which is responsible for querying remote segments to get their local browse list. Having said all that if you have a domain in place attempt to map to a share from the remote location to the W2k3 server and vice versa. If the drive map fails post the exact error. "Gary Roach" wrote in message news: I'm connecting to a network over a VPN. the VPN is hosted by a machine running server 2003. it's also running a WINS server. the machine is a stand-alone server. on the vpn client machine, i get the WINS address of the WINS server correctly and i can ping internal machines using netbios names. however, i cannot browse the network using the vpn client. when i click "view workgroup computers", i get the error: workgroup is not accessible. you might not have permissions to use this network resource. |
#4
|
|||
|
|||
can't browse network accessed via VPN
I agree with Michael. This won't work with a workgroup. Apart from
anything else, you will find that the client will search for a browse list by sending a domainname 1b request to WINS. This doesn't exist without a domain, and the client just sits there until it times out. Browsing WANs needs a domain setup. "Michael Giorgio - MS MVP" wrote in message ... If you don't have a domain in either location you will not be able to get this to work. You cannot browse remote workgroups without the presence of a DMB or domain master browser. The PDC or PDC emulator (W2k or higher) by default is always the DMB which is responsible for querying remote segments to get their local browse list. Having said all that if you have a domain in place attempt to map to a share from the remote location to the W2k3 server and vice versa. If the drive map fails post the exact error. "Gary Roach" wrote in message news: I'm connecting to a network over a VPN. the VPN is hosted by a machine running server 2003. it's also running a WINS server. the machine is a stand-alone server. on the vpn client machine, i get the WINS address of the WINS server correctly and i can ping internal machines using netbios names. however, i cannot browse the network using the vpn client. when i click "view workgroup computers", i get the error: workgroup is not accessible. you might not have permissions to use this network resource. |
#5
|
|||
|
|||
can't browse network accessed via VPN
it's a workgroup i'm trying to browse. interesting that since i posted, a
windows 98 VPN client produced a browse list. it included XP clients from the local LAN and the server that runs the WINS server but not the XP remote client that's also connected via a VPN. the XP client still gives an error when i try to browse, but i can connect to shares on the LAN using UNC with netbios names. "Michael Giorgio - MS MVP" wrote in message ... If you don't have a domain in either location you will not be able to get this to work. You cannot browse remote workgroups without the presence of a DMB or domain master browser. The PDC or PDC emulator (W2k or higher) by default is always the DMB which is responsible for querying remote segments to get their local browse list. Having said all that if you have a domain in place attempt to map to a share from the remote location to the W2k3 server and vice versa. If the drive map fails post the exact error. "Gary Roach" wrote in message news: I'm connecting to a network over a VPN. the VPN is hosted by a machine running server 2003. it's also running a WINS server. the machine is a stand-alone server. on the vpn client machine, i get the WINS address of the WINS server correctly and i can ping internal machines using netbios names. however, i cannot browse the network using the vpn client. when i click "view workgroup computers", i get the error: workgroup is not accessible. you might not have permissions to use this network resource. |
#6
|
|||
|
|||
can't browse network accessed via VPN
it's a workgroup i'm trying to browse. interesting that since i posted, a
windows 98 VPN client produced a browse list. it included XP clients from the local LAN and the server that runs the WINS server but not the XP remote client that's also connected via a VPN. the XP client still gives an error when i try to browse, but i can connect to shares on the LAN using UNC with netbios names. "Phillip Windell" @. wrote in message ... Do the workgroup names match? Is the network you connect to a Domain or just a workgroup? -- Phillip Windell [MCP, MVP, CCNA] www.wandtv.com "Gary Roach" wrote in message ... I'm connecting to a network over a VPN. the VPN is hosted by a machine running server 2003. it's also running a WINS server. the machine is a stand-alone server. on the vpn client machine, i get the WINS address of the WINS server correctly and i can ping internal machines using netbios names. however, i cannot browse the network using the vpn client. when i click "view workgroup computers", i get the error: workgroup is not accessible. you might not have permissions to use this network resource. the vpn client is running xp pro. -- Gary Roach ADB Services |
#7
|
|||
|
|||
can't browse network accessed via VPN
You can sometimes get an (incomplete) browse list when you first connect,
but that is a fluke. When the browser settles down, it tells you (correctly) that it can't find the browse master. The remote clients will not appear in the LAN browse list. Browse lists are built by broadcasts, and these don't normally cross routers or WAN links. If you were using a site-to-site VPN, browsing would be possible because you would have a segment master browser at the remote site. But here again it only works with a domain. Only a PDC can merge browse lists to give you a network-wide list. "Gary Roach" wrote in message ... it's a workgroup i'm trying to browse. interesting that since i posted, a windows 98 VPN client produced a browse list. it included XP clients from the local LAN and the server that runs the WINS server but not the XP remote client that's also connected via a VPN. the XP client still gives an error when i try to browse, but i can connect to shares on the LAN using UNC with netbios names. "Michael Giorgio - MS MVP" wrote in message ... If you don't have a domain in either location you will not be able to get this to work. You cannot browse remote workgroups without the presence of a DMB or domain master browser. The PDC or PDC emulator (W2k or higher) by default is always the DMB which is responsible for querying remote segments to get their local browse list. Having said all that if you have a domain in place attempt to map to a share from the remote location to the W2k3 server and vice versa. If the drive map fails post the exact error. "Gary Roach" wrote in message news: I'm connecting to a network over a VPN. the VPN is hosted by a machine running server 2003. it's also running a WINS server. the machine is a stand-alone server. on the vpn client machine, i get the WINS address of the WINS server correctly and i can ping internal machines using netbios names. however, i cannot browse the network using the vpn client. when i click "view workgroup computers", i get the error: workgroup is not accessible. you might not have permissions to use this network resource. |
#8
|
|||
|
|||
can't browse network accessed via VPN
what you're telling me is consistent with what i've experienced. i've been
doing tests on a test LAN on which i've got a windows server 2003 server. this is why i tried to use WINS - because i had the ability to easily install it. ultimately, the LAN i'll be connecting to is workgroup of XP Pro machines with no WINS server (unless the router happens to have that capability - i don't know yet). in this environment i won't be able to resolve netbios names at all for the dial-up clients unless i can somehow maintain hosts or lmhosts files on the vpn client machines. the only way to do it automatically would be to enable global broadcasts to the vpn clients. i tried adding the 255.255.255.255 route to the routing table but "route" gave me an error saying this address is invalid. "Bill Grant" not.available@online wrote in message ... You can sometimes get an (incomplete) browse list when you first connect, but that is a fluke. When the browser settles down, it tells you (correctly) that it can't find the browse master. The remote clients will not appear in the LAN browse list. Browse lists are built by broadcasts, and these don't normally cross routers or WAN links. If you were using a site-to-site VPN, browsing would be possible because you would have a segment master browser at the remote site. But here again it only works with a domain. Only a PDC can merge browse lists to give you a network-wide list. "Gary Roach" wrote in message ... it's a workgroup i'm trying to browse. interesting that since i posted, a windows 98 VPN client produced a browse list. it included XP clients from the local LAN and the server that runs the WINS server but not the XP remote client that's also connected via a VPN. the XP client still gives an error when i try to browse, but i can connect to shares on the LAN using UNC with netbios names. "Michael Giorgio - MS MVP" wrote in message ... If you don't have a domain in either location you will not be able to get this to work. You cannot browse remote workgroups without the presence of a DMB or domain master browser. The PDC or PDC emulator (W2k or higher) by default is always the DMB which is responsible for querying remote segments to get their local browse list. Having said all that if you have a domain in place attempt to map to a share from the remote location to the W2k3 server and vice versa. If the drive map fails post the exact error. "Gary Roach" wrote in message news: I'm connecting to a network over a VPN. the VPN is hosted by a machine running server 2003. it's also running a WINS server. the machine is a stand-alone server. on the vpn client machine, i get the WINS address of the WINS server correctly and i can ping internal machines using netbios names. however, i cannot browse the network using the vpn client. when i click "view workgroup computers", i get the error: workgroup is not accessible. you might not have permissions to use this network resource. |
#9
|
|||
|
|||
can't browse network accessed via VPN
That about sums it up. Without a domain and without WINS you have to fall
back to lmhosts files and no browsing. This applies to a routed network too, not just remote users. "Gary Roach" wrote in message ... what you're telling me is consistent with what i've experienced. i've been doing tests on a test LAN on which i've got a windows server 2003 server. this is why i tried to use WINS - because i had the ability to easily install it. ultimately, the LAN i'll be connecting to is workgroup of XP Pro machines with no WINS server (unless the router happens to have that capability - i don't know yet). in this environment i won't be able to resolve netbios names at all for the dial-up clients unless i can somehow maintain hosts or lmhosts files on the vpn client machines. the only way to do it automatically would be to enable global broadcasts to the vpn clients. i tried adding the 255.255.255.255 route to the routing table but "route" gave me an error saying this address is invalid. "Bill Grant" not.available@online wrote in message ... You can sometimes get an (incomplete) browse list when you first connect, but that is a fluke. When the browser settles down, it tells you (correctly) that it can't find the browse master. The remote clients will not appear in the LAN browse list. Browse lists are built by broadcasts, and these don't normally cross routers or WAN links. If you were using a site-to-site VPN, browsing would be possible because you would have a segment master browser at the remote site. But here again it only works with a domain. Only a PDC can merge browse lists to give you a network-wide list. "Gary Roach" wrote in message ... it's a workgroup i'm trying to browse. interesting that since i posted, a windows 98 VPN client produced a browse list. it included XP clients from the local LAN and the server that runs the WINS server but not the XP remote client that's also connected via a VPN. the XP client still gives an error when i try to browse, but i can connect to shares on the LAN using UNC with netbios names. "Michael Giorgio - MS MVP" wrote in message ... If you don't have a domain in either location you will not be able to get this to work. You cannot browse remote workgroups without the presence of a DMB or domain master browser. The PDC or PDC emulator (W2k or higher) by default is always the DMB which is responsible for querying remote segments to get their local browse list. Having said all that if you have a domain in place attempt to map to a share from the remote location to the W2k3 server and vice versa. If the drive map fails post the exact error. "Gary Roach" wrote in message news: I'm connecting to a network over a VPN. the VPN is hosted by a machine running server 2003. it's also running a WINS server. the machine is a stand-alone server. on the vpn client machine, i get the WINS address of the WINS server correctly and i can ping internal machines using netbios names. however, i cannot browse the network using the vpn client. when i click "view workgroup computers", i get the error: workgroup is not accessible. you might not have permissions to use this network resource. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Can't browse network using wireless adapter (but wired works) | Dylan Keon | Networking and the Internet with Windows XP | 6 | October 8th 04 03:09 PM |
error log | David King | Networking and the Internet with Windows XP | 2 | August 30th 04 04:06 PM |
Network Cable Unplugged Error | Alan | Networking and the Internet with Windows XP | 2 | August 23rd 04 07:36 PM |
XP connects to network then can't see network | Kent Meyer | Windows XP Help and Support | 0 | July 30th 04 05:32 AM |
Can't browse My Network Places - help anyone? | [email protected] | Networking and the Internet with Windows XP | 0 | July 24th 04 04:01 AM |