• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 768
  • Last Modified:


    A client of mine runs a pharmacy with QS/1(a pharmaceutical software package).  QS/1 operates using NETBEUI.  I have created a vpn server at the site and have no problems connecting.  I can not, however, locate the QS/1 server through the VPN connection because I can not figure out how to install the NETBEUI protocol into the VPN connection.  
     I do understand that NETBEUI was discontinued with Windows XP, but I have copied the files off the CD to add the NETBEUI protocol to the wireless network adapter as well as the lan adapter with no problems.
     Am I trying to do the impossible or is it possible to add NETBEUI to the VPN connection.
1 Solution
Lee W, MVPTechnology and Business Process AdvisorCommented:
you do know netbui is Not routable correct? making sure youre not attempting to route it
does netbui show up in the list if so make an ipsec tunnel his server ip to ip of workstation you use to fix it , pain in the ass yes
( unless you redirect the ip but thats another topic )
you need a device capable of switching protocols ie a router to get out of netbui and to ip or whatever you use
The Happy Dog is right. Netbeui is a non-routable protocol meant for use on small LANs only.

My tactic would be to see if the proprientary software could use NETBIOS over TCP/IP rather than Netbeui on your LAN. Then VPN access should be fairly simple.
We Need Your Input!

WatchGuard is currently running a beta program for our new macOS Host Sensor for our Threat Detection and Response service. We're looking for more macOS users to help provide insight and feedback to help us make the product even better. Please sign up for our beta program today!

Even if you both (rccbi and happy) are right with that NetBEUI isn't routable: haven't you read the article from leew? There it is proposed to setup a tunnel, where the NetBEUI protocol is lead through... thats no routing option - it's more like bridging, as if you where directly connected. Only the tunnel endpoints are connected using a routable protocol (TCP/IP). NetBEUI-data will be encapsulated at the tunnel entrance and comes unchanged out at the tunnel end.
So if you follow the extensive instructions at the site of leew's link you should get it work

Good luck
Another possibility might be to install ISA as a WinSock proxy between TCP/IP and NetBEUI.

why go winsock make an ipsec tunnel his server ip to ip of workstation you use to fix it , pain in the ass yes
( unless you redirect the ip but thats another topic ) provides more secrity. is integrated within windows.
this is the way to go as win2k pro and above along with xp all flavors has built in support for it just use netbios over tcpip service than make the tunnel
http://www.faqs.org/rfcs/rfc1001.html is the rfc for it , based on this and the integrated support for tcp and ipsec( not to mention the encrypted link ) i think winsock is suboptimal
Use the lmhosts.sam file found on your windows pc that connects with the vpn and rename it to lmhosts. Enter the following line in the lmhosts file:

x.x.x.x    netbiosname           #PRE

Where x.x.x.x is the ipaddress of the machine you try to connect to and netbiosname is the netbiosname of the machine you try to connect to. Save the file and reboot.

Al must work fine now.

-> points to leew (or if he doesn't want: me ;-) )
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now