For Programmers: Free Programming Magazines  


Home > Archive > Clipper > January 2006 > ADSDOSIP and NetBios









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author ADSDOSIP and NetBios
google@green-pig.co.uk

2006-01-10, 6:55 pm

I'm sure this problem has been reported already but a quick search has
not found it.

We have just expereinced (and resolved) a problem with multiple clients
using ADSDOSIP and long NetBios machine names. We are using Client v7
with Server v8.

We found that only one of our client PC's could connect via ADSDOSIP to
the server, at a time.
The problem was in the PC name. When NetBios is in use, ADSDOSIP
registers a name which is made up of "BD_"+MachineName. NetBios names
are limited to 16 characters so the name that finally gets registered
by ADSDOSIP will get truncated to 16 chars.

The problem arrises when the PC's already have a long name which is not
unique until the last few characters - i.e. PC1='MY_NETWORK_NODE1',
PC2='MY_NETWORK_NODE2' etc.
ADSDOSIP tries to register "BD_MY_NETWORK_NO" on both machines when the
DOS application starts up.
Only the first machine is succesful and the second fails. When the
first machine closes the DOS app and de-registers the name, then the
second can work.

The solution is to either ...
i) reduce the names of all PC's to less than 13 characters
or
ii) make sure the first 13 characters of the PC names are unique

Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com