🚀 go-pugleaf

FWIW NetBIOS sets up and maintains connections. It is a non-routable 
protocol. NetBIOS uses broadcasts to spread information about servers. It 
supports 3 services:
Session service, This is a connection oriented protocol, peer-to-peer and 
client/server.
Datagram service
This is used to deliver broadcasts and is connectionless.
Name service
This means that no central name servers are required. There is a possibility 
to run NetBIOS over TCP/IP and then you need a name resolution-system like a 
LMHOSTS-file or A WINS server. So I don't think that is the issue. Since it 
works from a workgroup I would look at probably a Domain trust issue or a 
Policy issue. What VPN software are you using.


-- 
The Real Truth http://pcbutts1-therealtruth.blogspot.com/
*WARNING* Do NOT follow any advice given by the people listed below.
They do NOT have the expertise or knowledge to fix your issue. Do not waste 
your time.
David H Lipman, Malke, PA Bear, Beauregard T. Shagnasty, Leythos.




"Al" <bigal.nz@gmail.com> wrote in message 
news:9c973f6f-1112-46bc-bf2c-a59a7436f5df@h40g2000prf.googlegroups.com...
On Oct 6, 11:36 pm, Al <bigal...@gmail.com> wrote:
> On Oct 6, 11:01 pm, Al <bigal...@gmail.com> wrote:
>
>
>
> > Hi guys,
>
> > I have a VPN connection to works router, and from there I have access
> > to the network/workgroup.
>
> > The VPN Router/DHCP etc is on a LAN IP of 10.1.1.1.
>
> > I can connect to various network resources via IP but not via netbios
> > name. I assume I have to add 10.1.1.1 into WINS server, but that didnt
> > help!
>
> > Anyone tell me what I might be doing wrong?
>
> > Cheers
>
> > -Al
>
> PS: I just checked a PC on the lan uses DNS of 10.1.1.1. So I have
> changed my VPN connection to also use 10.1.1.1 (it was picking up the
> DNS servers of my internet provider).
>
> But sitll no joy.

PPS: Computers on the workgroup lan dont suffer from this problem
either....