To close NetBIOS access, you need a hardwre or software firewall that can block the packets. You'll never be able to rip it out of Windows directly...
At 10:09 9/26/2003, jhon wong wrote: >Tracy, > Thank you. I know the truth now. > As a programmer,I don't like microsoft really. >One day in future,I will use linux to run mail server. > And a question more is how to close NETBIOS on win2000? >I had stop NETBIOS helper service. > > Best regards, > Jhon > > > >----- Original Message ----- >From: "Tracy" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Friday, September 26, 2003 9:42 PM >Subject: [xmail] Re: question about RDNS > > > > "getnameinfo" is new with Windows XP - it is not supported (as far as I >can > > tell) on older platforms (such as Windows 2000 or Windows 9x). > > > > MSDN lists this function as being defined in the ws2tcpip.h file - as far > > as I know, this is only available in the January 2003 or later version of > > the Platform SDK. > > > > Because this function is only supported for Windows XP, it is not >something > > that can be targeted in a package such as XMail, due to the wide level of > > support required. > > > > Also, it is a very good example of Microsoft breaking things for their own > > purposes - gethostbyaddr has been around since (IIRC) the original >Berkeley > > Sockets implementation. Just because Microsoft decided to add "special" > > functionality to it for Windows (ie. NetBIOS name resolution) doesn't mean > > that it was right for this to be done - all it does is force programmers >to > > break code compatibility across OS platforms by requiring a Windows > > specific call (getnameinfo) to avoid NetBIOS resolution. > > > > I suspect you'll continue to see gethostbyaddr used in Windows code for a > > long time to come. > > > > BTW, because of the insecure nature of NetBIOS, many companies block > > NetBIOS at their firewalls. You may want to consider this on your network, > > as well - there are many Windows exploits that use NetBIOS.... > > > > At 09:42 9/26/2003, jhon wong wrote: > > > > >Hi Tracy, > > > > > > You are right. I trid the nbtstat -A 218.246.127.68, > > >it really return NETBIOS name. > > > > > > Yes,in windows platform,"gethostbyaddr" is adapted to > > >NETBIOS. And microsoft advise to use "getnameinfo" > > >instead of "gethostbyaddr". please see: > > > > > > >http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/wi >n > > >sock/gethostbyaddr_2.asp > > > > > > But I can't find "getnameinfo" in <winsock2.h> at all > > >with vc6.0.I don't know why. > > > > > > Best regards, > > > Jhon > > > > > > > > >----- Original Message ----- > > >From: "Tracy" <[EMAIL PROTECTED]> > > >To: <[EMAIL PROTECTED]> > > >Sent: Friday, September 26, 2003 9:07 PM > > >Subject: [xmail] Re: question about RDNS > > > > > > > > > > You're running Windows, yes? If so, this is "by design". If Windows is >not > > > > able to resolve an address by finding a PTR record, it attempts to >resolve > > > > the address using NetBIOS - to do this, it issues a NetBIOS request to >the > > > > machine in question and listens for a response. Assuming no firewalls >get > > > > in the way, the machine will answer that request with it's "computer >name" > > > > (the locally assigned name that was created during the installation of > > > > Windows). > > > > > > > > Try using: > > > > > > > > nbtstat -A 211.149.111.76 > > > > > > > > and see what comes back (note that the -A must be a capital A, not a >lower > > > > case a). I'm guessing that the name you are seeing in your mail logs >will > > > > show up in the output from that command. (I'd try it here, to give you > > > > sample output, but I have NetBIOS blocked at my border router.) > > > > > > > > At 09:13 9/26/2003, jhon wong wrote: > > > > > > > > > > > > >Hi,Jeff: > > > > > > > > > > According to my knowledge, when gethostbyname > > > > >execute RDNS result,it should return FQDN result > > > > >if ip has PTR. > > > > > But I find that sometimes non FQDN result > > > > >is returned and in fact the ip hasn't PTR at all. > > > > >That is the problem. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Davide, > > > > > > > > > > > > Could his problem have anything to do with Verisign's new policy >of > > > > > > redirecting lookups for bogus domains to one of their sites? > > > > > > > > > > > > Jeff > > > > > > > > > > > > > > > > > > - > > > > > > To unsubscribe from this list: send the line "unsubscribe xmail" >in > > > > > > the body of a message to [EMAIL PROTECTED] > > > > > > For general help: send the line "help" in the body of a message to > > > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > >- > > > > >To unsubscribe from this list: send the line "unsubscribe xmail" in > > > > >the body of a message to [EMAIL PROTECTED] > > > > >For general help: send the line "help" in the body of a message to > > > > >[EMAIL PROTECTED] > > > > > > > > > > > > - > > > > To unsubscribe from this list: send the line "unsubscribe xmail" in > > > > the body of a message to [EMAIL PROTECTED] > > > > For general help: send the line "help" in the body of a message to > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > >- > > >To unsubscribe from this list: send the line "unsubscribe xmail" in > > >the body of a message to [EMAIL PROTECTED] > > >For general help: send the line "help" in the body of a message to > > >[EMAIL PROTECTED] > > > > > > - > > To unsubscribe from this list: send the line "unsubscribe xmail" in > > the body of a message to [EMAIL PROTECTED] > > For general help: send the line "help" in the body of a message to > > [EMAIL PROTECTED] > > > > > > >- >To unsubscribe from this list: send the line "unsubscribe xmail" in >the body of a message to [EMAIL PROTECTED] >For general help: send the line "help" in the body of a message to >[EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
