Error No Via Ports Were Found
Contents |
by CloudFlare Ray ID: 2f18c34df2fd15e3
I'm trying to get the details of the drive but whenever I open Jungle Flasher I will get the warning dialog box . I'm running Windows 8.1 x64. I've already disabled the driver stuff so the driver works and I'm running Jungle http://team-xecuter.com/forums/threads/55020-No-VIA-Ports-were-Found-in-Jungle-Flasher Flasher in compatibility mode Windows XP (Service Pack 3). The BIOS is detecting the drive correctly. Thanks in advance. Kakkoii 2013-09-16 17:49:29 UTC #2 Make sure your SATA chipset mode is set to "IDE" and not "AHCI" in your BIOS settings. https://community.wemod.com/t/jungle-flasher-no-i-o-ports-found/2893 sgt_frankieboy 2013-09-16 18:29:15 UTC #3 Kakkoii: Make sure your SATA chipset mode is set to "IDE" and not "AHCI" in your BIOS settings. Yea already discovered that after hours of searching. But idgaf anymore. Currently installing the game xogxmcxprimex 2014-05-23 22:02:22 UTC #4 explaing how you figured this out pls i have the same problem and am unsure what to do! sgt frankieboy: Yea already discovered that after hours of searching. But idgaf anymore. Currently installing the game Chris 2014-05-23 22:17:46 UTC #5 Please do not bump old threads. If you have an issue create a new one or message the original poster. Closed. Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled Infinity Horizon Blog
You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. No Via Ports Found! Started by slader155 , Feb 02 2013 03:57 AM This topic is locked 8 http://forums.xbox-scene.com/index.php?/topic/745682-no-via-ports-found/ replies to this topic #1 slader155 slader155 X-S Enthusiast Members 8 posts Posted 02 February 2013 - 03:57 AM Hi Everyone,I can't seem to get JungleFlash to detect my drive.I've disabled my VIA card, Renamed the https://community.spiceworks.com/help/Inventory_WMI driver, Enabled it, Restarted my computer, Opened JF, And I get a "No VIA Ports Found" error.How can I fix this? Would greatly appreciate the help.Thanks,Collin Back to top #2 Aldanga Aldanga X-S Hacker Head error no Moderators 2,730 posts Gender:Male Interests:Hardware,software,coding,algorithms, troubleshooting, tinkering with anything I can get my hands on. Xbox Version:none 360 version:v5.0 (360S - trinity) Posted 02 February 2013 - 05:11 AM Does the card show up in your device manager? Back to top #3 slader155 slader155 X-S Enthusiast Members 8 posts Posted 02 February 2013 - 05:13 AM Yeah, It says VIA RAID CONTROLLER 6421 Back to top #4 Aldanga Aldanga X-S error no via Hacker Head Moderators 2,730 posts Gender:Male Interests:Hardware,software,coding,algorithms, troubleshooting, tinkering with anything I can get my hands on. Xbox Version:none 360 version:v5.0 (360S - trinity) Posted 02 February 2013 - 05:21 AM Try the suggestions in this thread at TX and this thread at JungleFlasher.net.If those don't work, sometimes it's just the PC. I've had trouble with individual PCs and Via cards before. It's definitely not unheard of. Back to top #5 slader155 slader155 X-S Enthusiast Members 8 posts Posted 02 February 2013 - 06:30 AM Nope, I already found those threads Oh, When I start JF I get a "No I/O Ports Were Found During Enumeration!" Error. Back to top #6 slader155 slader155 X-S Enthusiast Members 8 posts Posted 02 February 2013 - 07:29 AM I'm using Win7, A Rosewill 212, And I'm trying to flash a Liteon DG-16d2s.So just to be clear: Disc drive's power cord is connected to the Xbox, Liteon's Sata is connected to the VIA card, And the VIA card is connected to my MOBO.I really wanna play halo 4, I've been working on this for 2 weeks now.PLEASE HELP ME! Back to top #7 Aldanga Aldanga X-S Hacker Head Moderators 2,730 posts Gender:Male Interests:Hardware,software,coding,algorithms, troubleshooting, tinkering with anything I can get my hands on. Xb
Profile ActionsView SourceRevisionsBacklinks ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events Browse Help No Open Ports For This Device Were Found To Be Responding Error “No open ports for this device were found to be responding. This typically means that there is a firewall or permission issue preventing remote access.” Symptoms Spiceworks can find the device on the network (and can return an IP address), but there are no open ports for Spiceworks gather any more information from. Causes Incorrect WMI Permissions Incorrect DNS information. Windows Firewall blocking ports. Antivirus Program blocking ports. Resolution NOTE: If after any of the following troubleshooting steps you rescan the device in Spiceworks and get a DIFFERENT error, follow the troubleshooting steps for that error in the Help and Support section. Follow each of these steps to alleviate the problem: 1. Confirm WMI Connectivity. This is the first step of all inventory related troubleshooting in Spiceworks. Follow the below steps: Open a command prompt on the Spiceworks machine. Type the following command: c:\> wmic /user:USER_NAME /password:USER_PASSWORD /node:IPADDRESS systemenclosure get serialnumber USER_NAME and USER_PASSWORD should be the username and password you are using to run a scan in Spiceworks. IPADDRESS is the IP address of the machine you are trying to troubleshoot. Be sure to use the IP address, not the hostname. Note: You should not run this command from the machine you are troubleshooting, it needs to be run from the machine on which Spiceworks is installed. The results of the command should return the serial number of that machine or None. If you see either of these, the command was successful and you should try to rescan the device within Spiceworks. If you see the “Access Denied” error, this indicates that Spiceworks can talk to Windows on that remote device, but the credentials that were supplied don't have permissions on that machine. Follow the steps in this article starting with Account Doesn’t have WMI Access. If you see the “RPC Unavailable” error, there is a firewall in the way. Skip down to turning off the firewall. After you have followed the instructions based on the error message you were getting, verify that WMI is now configured correctly by repeating the steps. If WMI isn’t configured correctly, or if ports 135 and 445 are blocked on the machine, WMI won’t be able to get that information. The firewall exceptions below should