unable to connect to certain nodes
i’m running a shari node with a raspberry pi 3. my node number is [42437](http://stats.allstarlink.org/nodeinfo.cgi?node=42437). i built it two weeks ago and had it working great. i would use it mainly to connect to our local club repeater node 43763.

last night, after not using the node for a few days, i fired it up, but i was unable to connect to the …
i was able to solve this with david’s help.

the issue was on the 43763 node (the one i was trying to connect to). since i have shell access to the remote node 43763 as well, i was able to update the rpt\_extnodes file there. in non-hamvoip asl, this is performed by running the rc.updatenodelist scri…
hi,

do you have joy package installed with all necessary packages/dependencies ?

try to search for joy\_node or run joy package examples to find out what is going wrong. Dear Jay Nelish


Your Question is incomplete


is the specific system is not on Network? its might be a problem discovered last year, that system ping but not share any data, or cannot access the system


you click on start menu and then click on run  

type serivces.msc  

and run the computer browser service, Remote Procedure call service, Server, and Client service


and your problem will resolved  

but actually this is because of virus change your antivirus program and scan your system wtih updated A/V hi gerryos,there are some network communication errors showing up. how are your sonos units connected to your network? are they wired into a switch or directly into your router?it may help to reboot your router, sonos units and any other network hardware you have connected. this may clear up the network errors and help with spotify playback and the 1002 timeout errors. sorry i took so long to respond on this post. i’ve had a busy week! so i found the issue. in my template for endpoints i realized i accidentally set them to provision using the external ip address of my pbx. changed it to internal and this fixed my issues :stuck\_out\_tongue: you have to forward the sip and rtp ports of the snom. (before the update this was done by a sip application layer gateway, but we had to remove this because it breaks security.)

[image]

[security announcement: mitigating nat slipstreaming - the ipfire blog](https://blog.ipfire.org/post/security-announcement-mitigating-nat-slipstreaming)

last autumn, we learned about … thank you [@colin](/u/colin)! i enabled port 1880 on my pi using "sudo ufw allow 1880" and after it worked! problem fixed. despite what citi told me, krista at tiller said my card was indeed linked. what i had to do was go into tiller feeds and find the list of linked accounts. the box next to citi was unchecked, so i checked it and now everything seems to work. that is where i'd start as well. osi...
so:
1. physical link (maybe check the patch panel and the cabling that's involved in connecting to the computer, maybe swap cables and try a usb to ethernet adapter to rules the nic out.
2. data link - check the switches and switchports on the way. maybe try to use different portts
3. network - most likely not an issue if all the other computers are working fine...
etc.
but this is pretty much it: Have you tried restarting your browser? welcome to the forum! :slight\_smile:

[image] adamski234:

i had linux59 installed since the nvidia drivers were released. but after the update to rc4, the driver stopped working, and while trying to update/reinstall i found out that the driver was not in the unstable repos. not 440xx, not 450xx,…