Problem with NobleNet portmapper and Omni-NFS server.
Ramnivas Laddad
I am trying to evaluate the Omni-NFS server from XLink Technologies.
I am also a Tornado (NT) user and it requires that I use portmapper
supplied by NobleNet. I eventually plan to mount drives exported by
nfs server running on NT box onto vxWorks target.
The problem, I am facing is I cannot start Omni-NFS service if the
NobleNet portmapper is already started.
If I start the Omni-NFS server first, when I start NobleNet's portmapper,
I get these messages.
"portmap: Cannot bind datagram socket.
portmap: Another Promapper may be running
winsock: Address already in use"
Then, if I start WindShell from Tornado, I get "Target Server <target>@<host>
is not responding. It may be too busy to answer..."
Can somebody help me resolve the issue.
Thanks.
-Ramnivas
============================================================
Ramnivas Laddad (408) 720 8312 x110
Real Time Innovations, Inc. ramn...@rti.com
155A Moffett Park Drive http://www.rti.com
Sunnyvale CA 94089.
Gerald van Kampen
Ramnivas Laddad wrote:
> Hello,
>
> I am trying to evaluate the Omni-NFS server from XLink Technologies.
> I am also a Tornado (NT) user and it requires that I use portmapper
> supplied by NobleNet. I eventually plan to mount drives exported by
> nfs server running on NT box onto vxWorks target.
>
> The problem, I am facing is I cannot start Omni-NFS service if the
> NobleNet portmapper is already started.
>
> If I start the Omni-NFS server first, when I start NobleNet's portmapper,
> I get these messages.
> "portmap: Cannot bind datagram socket.
> portmap: Another Promapper may be running
> winsock: Address already in use"
> Then, if I start WindShell from Tornado, I get "Target Server <target>@<host>
> is not responding. It may be too busy to answer..."
>
I once ran into the same problem (not fixed).
Only one portmapper can be active on a system for a given port (Portmap
uses port 111, I think). The problem is that Omni NFS wants to start and use it's
own
(restricted to NFS ?) built-in portmapper instead of using this service from
system global portmap applications like Noblenet.
Try instead: http://www.truegrid.com/nfs.html
--
Gerald van Kampen
XLink Technology
Thanks for interested on Omni software. I believe those two
portmappers comflict each other. but if you are going to use
Omni-NFS server you have to user the portmapper provide by Xlink,
currently no way let you disable it.
Regards
Support, Xlink Technology inc
On Fri, 4 Jun 1999, Ramnivas Laddad wrote:
> Hello,
>
> I am trying to evaluate the Omni-NFS server from XLink Technologies.
> I am also a Tornado (NT) user and it requires that I use portmapper
> supplied by NobleNet. I eventually plan to mount drives exported by
> nfs server running on NT box onto vxWorks target.
>
> The problem, I am facing is I cannot start Omni-NFS service if the
> NobleNet portmapper is already started.
>
> If I start the Omni-NFS server first, when I start NobleNet's portmapper,
> I get these messages.
> "portmap: Cannot bind datagram socket.
> portmap: Another Promapper may be running
> winsock: Address already in use"
> Then, if I start WindShell from Tornado, I get "Target Server <target>@<host>
> is not responding. It may be too busy to answer..."
>
> Can somebody help me resolve the issue.
>
> Thanks.
>
> -Ramnivas
>
> ============================================================
> Ramnivas Laddad (408) 720 8312 x110
> Real Time Innovations, Inc. ramn...@rti.com
> 155A Moffett Park Drive http://www.rti.com
> Sunnyvale CA 94089.
>
******************************************************************
+++ Visit our web site to participate in XLink Online Drawing
for FREE NFS Software for 98/95/NT!
Remember, you got to be in it to win it!
+++ XLink's Open Forum Welcomes you to join Network Discussion!
Visit our web site to post your thoughts!
********************************************************************
---------------------------------
XLINK TECHNOLOGY, INC.
Technical Support Team
http://www.xlink.com/SUPPORT.HTM
E-Mail:sup...@xlink.com
---------------------------------
cor...@my-deja.com
I think all of this stems from the use of the RPC ports on windows. The
portmapper from WRS implements RPC for the targets to talk through,
right? and it binds to the NFS port, so when the NFS server comes up, it
can't bind to a port. I just can't believe that no one at WRS has ever
fixed this or even looked into it.
In article <375BEB88...@oce.nl>,
Gerald van Kampen <k...@oce.nl> wrote:
>
>
> Ramnivas Laddad wrote:
>
> > Hello,
> >
> > I am trying to evaluate the Omni-NFS server from XLink Technologies.
> > I am also a Tornado (NT) user and it requires that I use portmapper
> > supplied by NobleNet. I eventually plan to mount drives exported by
> > nfs server running on NT box onto vxWorks target.
> >
> > The problem, I am facing is I cannot start Omni-NFS service if the
> > NobleNet portmapper is already started.
> >
> > If I start the Omni-NFS server first, when I start NobleNet's
portmapper,
> > I get these messages.
> > "portmap: Cannot bind datagram socket.
> > portmap: Another Promapper may be running
> > winsock: Address already in use"
> > Then, if I start WindShell from Tornado, I get "Target Server
<target>@<host>
> > is not responding. It may be too busy to answer..."
> >
>
> I once ran into the same problem (not fixed).
>
> Only one portmapper can be active on a system for a given port
(Portmap
> uses port 111, I think). The problem is that Omni NFS wants to start
and use it's
> own
> (restricted to NFS ?) built-in portmapper instead of using this
service from
> system global portmap applications like Noblenet.
>
> Try instead: http://www.truegrid.com/nfs.html
>
> --
> Gerald van Kampen
>
>
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
Hwa-Jin Bae
>
>
>I think all of this stems from the use of the RPC ports on windows. The
>portmapper from WRS implements RPC for the targets to talk through,
>right? and it binds to the NFS port, so when the NFS server comes up, it
>can't bind to a port. I just can't believe that no one at WRS has ever
>fixed this or even looked into it.
To be fair, the problem of running two copies of portmapper daemon has
to do with the fact that Windows does not have built in portmapper.
So in order to use RPC facilities, you basically have to run your own
portmapper, as do Tornado and Omni NFS product. If you installed another
NFS product you would have similar problems. I wouldn't categorize this
as WRS problem, although it would help to make an option available to
handle this problem -- use a different port for portmapper, for example,
even though it is not RFC standards compatible. Just my opinion.
--
Hwa-Jin Bae
PSO Systems Inc -- Embedded SW/HW design, consulting, support, training
mailto:h...@pso.com http://www.pso.com
Un-official VxWorks FAQ http://www.pso.com/vxfaq.html
Ramnivas Laddad
Thanks everyone for helping. The problem was with Omni's portmapper
and Omni-NFS requires that you use only their portmapper.
The solution I tried, which seems working so far, is using NFS server
from TrueGrid. (thanks Gerald, for suggesting it).
http://www.truegrid.com/nfs.html
With TrueGrid, I can use either the portmapper supplied by them or
the one that comes with Tornado 1.0.1.
Thanks again.
-Ramnivas
p.s. I am using Tornado 1.0.1.
At 10:19 AM 6/7/99 +0200, Peter Van Ackeren wrote:
>
>
>the vxWorks Users Group Exploder wrote:
>>
>> Submitted-by owner-vxwexplo-process Fri Jun 4 17:29:14 1999
>> Submitted-by: Ramnivas Laddad <ramn...@rti.com>
>>
>> Hello,
>>
>> I am trying to evaluate the Omni-NFS server from XLink Technologies.
>> I am also a Tornado (NT) user and it requires that I use portmapper
>> supplied by NobleNet. I eventually plan to mount drives exported by
>> nfs server running on NT box onto vxWorks target.
>>
>> The problem, I am facing is I cannot start Omni-NFS service if the
>> NobleNet portmapper is already started.
>>
>> If I start the Omni-NFS server first, when I start NobleNet's portmapper,
>> I get these messages.
>> "portmap: Cannot bind datagram socket.
>> portmap: Another Promapper may be running
>> winsock: Address already in use"
>> Then, if I start WindShell from Tornado, I get "Target Server
<target>@<host>
>> is not responding. It may be too busy to answer..."
>>
>> Can somebody help me resolve the issue.
>>
>> Thanks.
>>
>> -Ramnivas
>
>Hi Ramnivas,
>
>I ran into this on a few sites that had other portmappers running.
>
>The Tornado registry on T1.0.1 requires a portmapper. If you've installed
>it as a service, Tornado will have made it explicitly dependent on the
>NobleNet portmapper.
>
>What you want is to have the Registry use whatever portmapper that works and
>allows other NT s/w to run equally well.
>
>A solution that likely will work is :
>
>- In [Control Panel->Services] look up and write down the exact name
> of the Tornado portmapper and registry
>- Stop the Tornado portmapper and registry service
>- Run 'servutil' and remove the registry service
>- Run 'servutil' and remove the portmapper service (if needed)
>- Start OMNI-NFS server, which I gather starts another portmapper.
>- Run 'servutil' and install the registry service with the 'dependent
> service' field left open (use the exact info you wrote down earlier)
>- Start the registry service. Either the service starts and you're up,
> or the service returns an error, which indicates an incompatibility
> with the existing portmapper (I think this is quite unlikely, though)
>
>Notes :
>
>- If you start the other portmapper manually, then you will have the install
> the Tornado registry service as starting manually.
>- If the other portmapper is also a service, an alternative is to make the
> Tornado registry service depend on it explicitly.
>- If the registry does not work with the OMNI provided portmapper, then try
> to make OmniNFS work with the Noblenet one.
>
>
>Hope this helps,
>
>Peter Van Ackeren
>Field Application Engineer
>WRS Benelux
>
>-----------> WRS Home Page : http://www.wrs.com <----------
>
>!!! New mobile phone number : 0495-225.664 (from Feb 1) !!!
>Attachment Converted: "c:\eudora\attach\peterva.vcf"
XLink Technology
Thanks a lot for the information. We need think about it.
I hope we will support such functionality on the next release.
Best Regards
Support, Xlink Technology inc