Tom,
perhaps I didn't understand your question. 127.0.0.2 still belongs to same interface as 127.0.0.1, and points back to your computer. And, you can bind it on port 139, I've seen few customers doing that without any problems.
On XP I think it's important to have windows patch installed from
http://support.microsoft.com/default.aspx?kbid=884020
and after that, just open channel on 139. That should do it.
Complete thread:
We are having great success with your component ... email server that has over 750 000 mailboxes back ended by a SQL server...
We have recently completed a large 1200+ location project where reliable Telnet and SSH connectivity was required. wodSSH worked flawlessly and allowed our staff to complete our project ontime and within budget.
May I say how nice it is to work with components so complete and self-explanatory that using them in my application is as instinctive as though I wrote them myself?
...with the SFTP interface you produced, everything was so simple to understand, we were able to start coding almost immediately!
...with a minimum of effort as the DLL interface was written with such simplicity...
Congratulations on an excellent product and first rate support!
I've heard that you are amazing with your replies coming back so quickly - and now I've seen the speed in which you reply first hand.
The wodCrypt product is great and we appreciate your effort to add support for UNIX Crypt.
You have been great as far as offering support is concerned and has been extremely responsive to both support requests and suggestions for product enhancements.
Many thanks for your excellent support service. I can see why you have a long list of excellent testimonials on your website.
![[*]](themes/default/images/complete_thread.png "Open whole thread"){kind=small}