[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDV #KLI-817328]: attempts to connect to adde servers refused

> Hi Yuan,
> 
> I think you hit on something.  I checked the IDV plugins, and under "Data
> Sources" saw a plugin installed called "access to Unidata ADDE server via
> port 80".
> Not sure what that plugin was for?  I removed it, and I can now connect to
> both Unidata and SSEC adde servers.
> 
> I'm still curious, which port is the default for adde access?  Is it 112?
> If that's the case, then maybe we don't have an issue with 112?
> 
> Thanks so much Yuan for your help troubleshooting this!
> 
> Patrick

112 is the officially registered port number and it is internationally 
recognized.

Yuan
> 
> address@hidden> wrote:
> 
> > > > Yuan, is port 112 on the server side for adde.ucar.edu?  And could
> > that be
> > > > the reason for my IDV ADDE connections being refused?
> > > >
> > > > It's confusing to me why then my McIDAS-V adde connections to
> > adde.ucar.edu
> > > > are being allowed.  Could IDV and McIDAS-V be using different ports
> > for the
> > > > server connections?
> > > >
> > > > If port 112 is an issue, it seems reasonable for UCAR to see that port
> > 112
> > > > flows to all staffnet systems in UCAR, if that makes sense.
> > > >
> > > > What do you think?
> > > >
> > > > Patrick
> > >
> > > Port number opening is controlled by the network adm., so I am trying to
> > find out
> > > who I should contact, I am working with the system adm of Unidata to
> > find the solution.
> > >
> > > Yuan
> >
> > Hi Patrick,
> >
> > You might be installed one of the plugin that mapped the port 112 to 8080,
> > could you check?
> >
> >
> > Yuan
> > > >
> > > > address@hidden> wrote:
> > > >
> > > > > > Yuan, I wonder if the non-connect to ADDE servers issue from IDV
> > could be
> > > > > > related to a port or ports being blocked on either the server or
> > client
> > > > > end?
> > > > > >
> > > > > > Bob Bubon ran a couple port checks on adde.ucar.edu.  Port 112 is
> > open,
> > > > > > 8080 is not.  It sounds like these are important.
> > > > > >
> > > > > > comet-zebulon:~ root# ssh -p 8080 128.117.135.126
> > > > > > ssh: connect to host 128.117.135.126 port 8080: Connection refused
> > > > > >
> > > > > > comet-zebulon:~ root# ssh -p 112 128.117.135.126
> > > > > > kex_exchange_identification: read: Connection reset by peer
> > > > > > Connection reset by 128.117.135.126 port 112
> > > > > >
> > > > > >
> > > > > > Then, I also did a quick check of my Mac ports and both 112 and
> > 8080
> > > > > appear
> > > > > > to be open.
> > > > > >
> > > > > > comet-astro:~ dills$ nc -vnzu 128.117.138.251 112
> > > > > >
> > > > > > Connection to 128.117.138.251 port 112 [udp/*] succeeded!
> > > > > >
> > > > > >
> > > > > > comet-astro:~ dills$ nc -vnzu 128.117.138.251 8080
> > > > > >
> > > > > > Connection to 128.117.138.251 port 8080 [udp/*] succeeded!
> > > > > >
> > > > > > Any ideas or suggestions here?
> > > > > > Thanks,
> > > > > >
> > > > > > - Patrick
> > > > >
> > > > > It looks like the port 112 of network is not open. I am not sure it
> > is
> > > > > only your building or all UCAR campus.
> > > > > Someone should contact the network people to find out.
> > > > >
> > > > > Yuan
> > > > > >
> > > > > > ---------- Forwarded message ---------
> > > > > > From: Patrick Dills <address@hidden>
> > > > > > Date: Wed, May 8, 2024 at 3:04?PM
> > > > > > Subject: Re: [IDV #KLI-817328]: attempts to connect to adde servers
> > > > > refused
> > > > > > To: Yuan Ho <address@hidden>
> > address@hidden>
> > > > > >
> > > > > >
> > > > > > Hi Yuan,
> > > > > >
> > > > > > Thanks so much for your quick response!
> > > > > >
> > > > > > Still no luck connecting to ADDE servers in IDV, via either
> > ethernet or
> > > > > > wifi Staffnet.  I'll keep an eye on it, and will also try from an
> > outside
> > > > > > non-UCAR connection later today.
> > > > > > And will also follow up with IT on our end here.
> > > > > >
> > > > > > I'm not sure if this is relevant.  I'm able to make ADDE server
> > > > > connections
> > > > > > in my McIDAS-V install.
> > > > > >
> > > > > > Thanks again and I'll update on any changes.
> > > > > >
> > > > > > Patrick
> > > > > >
> > > > > > address@hidden> wrote:
> > > > > >
> > > > > > > > Full Name: Patrick Dills
> > > > > > > > Email Address: address@hidden
> > > > > > > > Organization: COMET
> > > > > > > > Package Version: 6.2u2 build date:2023-12-05 18:26 UTC
> > > > > > > > Operating System: Mac OS X
> > > > > > > > Hardware: Java: home:
> > > > > /Applications/IDV_6.2u2/jre.bundle/Contents/Home
> > > > > > > version: 1.8.0_302 j3d:1.6.1 fcs fcs
> > > > > > > > Description of problem: Connecting to server:adde.ucar.edu
> > > > > > > > Connection refused (Connection refused)
> > > > > > > >
> > > > > > > > I can not "connect" to any of the servers listed under the
> > "Server"
> > > > > > > select menu in IDV, when trying to call up an available
> > "Dataset",
> > > > > EASTALL,
> > > > > > > WESTALL, etc.
> > > > > > > >
> > > > > > > > Also, when I click the callout to the right of the DataSet
> > options
> > > > > list,
> > > > > > > I receive the message "no public datasets found on adde.ucar.edu.
> > I
> > > > > get
> > > > > > > the same response when trying to connect to other ADDE servers.
> > > > > > >
> > > > > > > Hi Patrick,
> > > > > > >
> > > > > > > I just tested adde.ucar.edu with dataset as  "EASTALL" and
> > "WESTALL",
> > > > > > > both worked as expected. What you experienced might be
> > > > > > > the temporary network or server issue. Please try again.
> > > > > > >
> > > > > > > Yuan
> > > > > > > >
> > > > > > > > ******************
> > > > > > > > Stack trace:
> > > > > > > > java.net.ConnectException: Connection refused (Connection
> > refused)
> > > > > > > > at java.net.PlainSocketImpl.socketConnect(Native Method)
> > > > > > > > at java.net
> > > > > > >
> > .AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> > > > > > > > at java.net
> > > > > > >
> > > > >
> > .AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> > > > > > > > at java.net
> > > > > > >
> > .AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> > > > > > > > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> > > > > > > > at java.net.Socket.connect(Socket.java:607)
> > > > > > > > at java.net.Socket.connect(Socket.java:556)
> > > > > > > > at java.net.Socket.<init>(Socket.java:452)
> > > > > > > > at java.net.Socket.<init>(Socket.java:229)
> > > > > > > > at
> > > > > > >
> > > > >
> > edu.wisc.ssec.mcidas.adde.AddeURLConnection.connect(AddeURLConnection.java:644)
> > > > > > > > at
> > > > > > >
> > > > >
> > edu.wisc.ssec.mcidas.adde.AddeURLConnection.getInputStream(AddeURLConnection.java:819)
> > > > > > > > at
> > > > > > >
> > > > >
> > ucar.unidata.idv.chooser.adde.AddeChooser.checkIfServerIsOk(AddeChooser.java:1209)
> > > > > > > > at
> > > > > > >
> > > > >
> > ucar.unidata.idv.chooser.adde.AddeChooser.canAccessServer(AddeChooser.java:1252)
> > > > > > > > at
> > > > > > >
> > > > >
> > ucar.unidata.idv.chooser.adde.AddeImageChooser.connectToServer(AddeImageChooser.java:802)
> > > > > > > > at
> > > > > > >
> > > > >
> > ucar.unidata.idv.chooser.adde.AddeImageChooser.handleConnect(AddeImageChooser.java:634)
> > > > > > > > at
> > > > > > >
> > > > >
> > ucar.unidata.idv.chooser.adde.AddeChooser.handleConnectFromThread(AddeChooser.java:601)
> > > > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > > > > > > at
> > > > > > >
> > > > >
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > > > > > > > at
> > > > > > >
> > > > >
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > > > > > > > at java.lang.reflect.Method.invoke(Method.java:498)
> > > > > > > > at ucar.unidata.util.Misc$2.run(Misc.java:1215)
> > > > > > > > at ucar.unidata.util.Misc$3.run(Misc.java:1243)
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Ticket Details
> > > > > > > ===================
> > > > > > > Ticket ID: KLI-817328
> > > > > > > Department: Support IDV
> > > > > > > Priority: Normal
> > > > > > > Status: Open
> > > > > > > ===================
> > > > > > > NOTE: All email exchanges with NSF Unidata User Support are
> > recorded in
> > > > > > > the Unidata inquiry tracking system and then made publicly
> > available
> > > > > > > through the web.  If you do not want to have your interactions
> > made
> > > > > > > available in this way, you must let us know in each email you
> > send to
> > > > > us.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > Ticket Details
> > > > > ===================
> > > > > Ticket ID: KLI-817328
> > > > > Department: Support IDV
> > > > > Priority: Normal
> > > > > Status: Open
> > > > > ===================
> > > > > NOTE: All email exchanges with NSF Unidata User Support are recorded
> > in
> > > > > the Unidata inquiry tracking system and then made publicly available
> > > > > through the web.  If you do not want to have your interactions made
> > > > > available in this way, you must let us know in each email you send
> > to us.
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: KLI-817328
> > Department: Support IDV
> > Priority: Normal
> > Status: Open
> > ===================
> > NOTE: All email exchanges with NSF Unidata User Support are recorded in
> > the Unidata inquiry tracking system and then made publicly available
> > through the web.  If you do not want to have your interactions made
> > available in this way, you must let us know in each email you send to us.
> >
> >
> >
> 
> 


Ticket Details
===================
Ticket ID: KLI-817328
Department: Support IDV
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with NSF Unidata User Support are recorded in the 
Unidata inquiry tracking system and then made publicly available through the 
web.  If you do not want to have your interactions made available in this way, 
you must let us know in each email you send to us.