AEBS (802.11n) and hp laserjet 2300 series

Has anyone had success with wireless printing using hp laserjet 2300 series?
I've installed the 2300 series drivers, but can only print when the printer is attached directly to the computer.

Unfortunately, not all USB printers are compatible with AirPort base stations. A quick look at the iFelix Unofficial AirPort Printer Compatibility List doesn't show this particular model. This doesn't necessarily mean it won't work, but simply that it has not been verified. iFelix also provides the following workaround for printers not on the list that would certainly be worth a try.
Also, you may find the following Apple article helpful.

Similar Messages

  • AEBS 802.11n and PPPoE AGAIN!!!!

    Ok, does apple read any of these posts? I am very irritated that I spent money on the AEBS (mostly for the support of USB disks for backups) and PPPoE is totally broken! I get frequent disconnects, and long down times before it establishes a connection. I just borrowed a Linksys 802.11n router and it works LIKE A CHAMP (no disconnects WHAT SO EVER)!
    I am constrained to run my DSL in bridge mode, as we have both a web server and a VPN set up on our home network, so this PPPoE issue is going to have me kicking my AEBS into the trashcan in favor of a Linksys.
    Please Apple - get on the ball, how hard could it be?
    What is your experience with PPPoE?
    -jmj75

    "Ok, does apple read any of these posts"
    Most likely not, as this is a user to user forum.
    Why not provide your feedback directly to Apple?
    http://www.apple.com/feedback/airportextreme.html

  • AEBS (802.11n) and AEX WDS Headaches

    I've been trying to get my Airport Express to extend the wireless network set up through my Airport Extreme Base Station using WDS and have had nothing but headaches.
    I've been able to use the AEBS to connect to the internet without problems, and can use AirTunes on the AEX—great fun. Unfortunately, the family room—where the AEX is—is at the opposite end of the house and on a different floor from where the AEBS is, and so WiFi reception there is less than spectacular. I want to extend the network—after all, I have the equimpment, right? But every time I try to set up a WDS, everything goes loopy.
    When I try to turn on WDS, one of two things happens: either the AEX disappears from the list of base stations, and the AEBS starts flashing yellow, giving me an error that "no WDS peer is available"; or both stations are in the list, green lights merrily on, but the internet connection becomes incredibly sporadic—off three minutes, on one, etc.... Eventually the connection just disappears. This is true not only from the G5, but from the iBooks as well, whether wired or wireless. The WiFi network shows up fine, the ethernet connection is still strong, the various components on the LAN are pingable... But the connection to the internet is gone.
    The two AirPort base stations are connected via ethernet (cat 5e) through a NetGear gigabit switch (the AEX connects through a Netgear gigabit hub that it shares with the family TiVo... and hopefully one day with either a Mac Mini or an Apple TV). My main computer is a PowerMac G5 1.8GHz single CPU with 4GB of RAM running 10.4.10, and connected to the network via both ethernet and AirPort. I have two iBooks (and occasional visitors) that use the network (wired and wireless), as well as the TiVo and a PS2.
    Peripheral-wise, the AEBS has a printer and a hard drive connected to the USB port via a powered USB hub. The AEX is hooked up to my home theater system (such as it is) using TOSlink cable, and has AirTunes enabled. I'm using AirPort Utility 5.0.
    I've set the network up according to the directions. The AEBS has WDS turned on, "Allow this network to be extended" is checked, it's set as the main base, and the AEX's ID is included in the remotes list. The AEX is using the same network and password, also has "Participate in a WDS Network" selected; it's set as a WDS Remote, and has the AEBS set as the main. The AEBS is the DHCP and NAT server for the network; it is connected directly to the DSL modem (a SpeedStream 5360). The AEX is set to connect to the internet through DHCP—it gets its address properly from the AEBS.
    I've had to turn WDS off yet again to post this message.
    Help????

    Set up a roaming network. WDS is for wireless coneection between the base stations.
    To set up roaming:
    1 Connect all of the AirPort Extreme Base Stations to the same subnet on your Ethernet
    network.
    2 Give each base station a unique name.
    3 Give each base station the same network name and password.
    4 Set up the base stations as bridges, following the instructions in the previous section.
    If you want one AirPort Extreme Base Station to assign IP addresses using DHCP, also
    do the following:
    1 Set up one base station to act as the DHCP server.
    2 Set up the other base stations as bridges, following the instructions in the previous
    section.
    The base station acting as a DHCP server can also receive its IP address via DHCP from a
    server on an Ethernet network or from a cable or DSL modem connected to an Internet
    service provider (ISP).

  • AEBS(802.11n) and WDS with Express or Extreme

    This problem is making me doubt my sanity.
    I have an Extreme Basestation and and Express and a new AEBSn.
    I previoulsy set up the Extreme as the WDS master and the Express as a Relay.
    Now the AEBSn is the master and I can NOT get either of the other two Apple routers to connect and function as WDS Relay stations or WDS Remote stations. I have attempted both using manual configuration following exactly the same steps I did with the Extreme/Express combination.
    But it will not work. Neither the Extreme nor the Express will connect to the AEBSn. I do note that the AEBSn does not have a WDS page or tab in Airport Utility but I did select "Allow this network to be extended" and I selected Create a wireless network.
    Does anyone know how to make this work? Does it work?
    Thanks for any suggestions.

    .. the automated system, i'm assuming that you mean selecting next, next next.
    Correct - except the word on my Airport Utility is "Continue"
    then after the first reboot and the configuration is loaded, go into manual and select "Allow this network to be extended",
    Correct - and be sure to turn off Access Control and turn off "Create a closed network". Once you have both basestations configured and working, you can go back in manually and set those options if you need those two extra levels of security.
    ..it tells me that it can't find any networks to connect to!!
    Always make sure you have updated the software and the firmware for both basestations and for your computers. There have been several Airport connect bug and fixes, both to the basestations and to the Airport cards in the computers. And make sure you have the lastest version of the Airport Utility.
    (When I first loaded 10.4.10 I screwed up all my wireless connections. I had to go back, reinstall the OS and use the Combo updater to update to 10.4.9 before my wireless would work. Later, on these forums, I learned that the 10.4.10 update had some issues in the first release. About two months after the initial release, I updated to 10.4.10 - using the Combo, NOT Delta - updater and finally had reliable wireless connections.)
    Once other note: I have done a LOT of work on my neighbor's LAN. I finally figured out that their ISP's modem had NATs and DHCP running on the modem. I could not make their network work until I turned off NATs and DHCP on the LAN router (bridge mode). Make sure you do not have DHCP/NATs conflicts with your ISP's modem.
    Leave the second device unplugged until you have the first basesetation configured and you can connect to it wirelessly. Disconnect your Ethernet cables to make sure there are no conflicting IP addresses or host names.
    Once you have connected to the first basestation, then open Airport Utility and wait for the second device to come up.
    Do not double click on the second basestation. Just click it once to select it then click "Continue" . Read all of the options carefully. I do not remember the exact language but one option is to connect to or expand and existing network. Once you get to that point, it is fairly simple.
    Good luck! Let me know if it works.

  • AEBS 802.11n question about bridging

    using AEBS 802.11n and connecting to an existing network which is using DHCP...
    internet button chosen
    internet connection panel chosen
    connect using : ethernet
    configure ipv4 : using dhcp
    ethernet wan port : automatic (default)
    connection sharing : share a public ip address
    is the AEBS acting as a bridge here? so, now the AEBS can pass out ip addresses that are different (local) network addresses than what the AEBS is receiving from the established network, which it is joining?? the established network 192.168.1 the AEBS DHCP network 10.0.1
    internet button chosen
    internet connection panel
    connect using : ethernet
    configure ipv4 : using dhcp
    ethernet wan port : automatic (default)
    connection sharing : Off (bridge mode)
    or...
    the AEBS is acting as a bridge here? (off (bridge mode)) can the AEBS pass out ip address using a different network address here? and if it does so there will be no NAT functionality?
    what does it mean to have DHCP functionality and no NAT. does using DHCP and no NAT mean that each computer, on the local network connected to the AEBS, that segment, must have a static address?

    In your first configuration, where connection sharing = share a public IP address, the AEBSn is still acting as a wireless router and, effectively, has created a second wireless subnet.
    In the second configuration, where connection sharing = Off (bridge mode), the AEBSn is "passing thru" the NAT/DHCP services from the router it's connected to so any devices connected to the AEBSn will still be on the same network as the upstream router.

  • Laserjet 1505 connected to AEB 802.11n via USB keeps timing out after print

    I have a HP Laserjet 1505 connected on my AEB 802.11n via USB and shared on my network, on my network are two macs connected via wifi and 3 WinXP PC connected via wire. I have Bonjour and WinXP laserjet drivers installed on all Win PC. Everytime I print from any of the computers, it will print the first time, but when I try printing again from any of the machines, the macs and winxp pc's cannot detect the printer. When I go to airport utility, the printer cannot be detected anymore. I have to hard reset the AEB for it to detect the laserjet printer again. But the same thing happens again after I print out another document. Has anybody encountered this kind of problem. Can anyone help me resolve this?

    Here is what I got from HP support :
    The driver for the Laserjet P1006 is not available yet for Os 10.5...we are hoping it will be release in the next week or so...please click on the link below to sign up for an email update as soon as it is available..As a workaround, some people have been able to use the 10.4 driver from the cd, but this is not guaranteed to work in all applications therefore the only solution is to wait and install the 10.5 driver.
    So we wait.
    Yves

  • AEBS 802.11n, TC and APXn with 7.3.1 is very flaky indeed - cant connect -

    HI Guys I think many of you on these forums have posted because you are having joyless experiences with the new APX 802.11n, the AEBSn and the TC not able to be managed via the AIRPORT UTILITY.app v5.3.2 with firmware 7.3.1 in the former devices. After a search there's many of these posts with people with the same issues.
    I have these devices in my place so I have had lost of experience configuring these over the years:
    1 x 802.11n AEBS, 1 x TC, 1 xUFO white AEBS, 2 x APXg's and lastly the problematic 1 x APX802.11n (one subnet and 2 x networks 2.4Ghz and 5 Ghz)
    I am at my wits ends trying to get the new APXn regularly responding to the AP utility.app (error reading configuration).
    I have tried most of the remedies on these forums but they do not consistently solve the problems of the APX not responding to the AP utility.None of these have consistently worked:
    • trying to factory reset it using the POWER ON+RESET and waiting for the amber flashes then green - butt this procedure NEVER WORKS to factory reset!
    • using the reset button in any form (it doesn't do anything)
    • connection through ethernet (sometimes works ).
    • takes long to power up (than the older 802.11g)
    • rest APXn back to factory defaults through the AP utility then ...
    • downloaded 7.3 firmware - worse and wont work
    • lastly I found that RESET+POWER ON then wait for 20 secs as as it powers up DEPRESS the RESET again and then it becomes readable.
    Additionally, I have been unsuccessful in getting PORT FORWARDINg to work at all for the AEBS 802.11n with and without the TC in the mix. I had this working for several years with the White UFO AEBS ... It beats me.
    I think the firmware is very very flaky and i have no resolutions for these recent problems.
    Hope for a fix soon.
    I will be polling these forums for any clues.
    w

    Hi Guys
    REgarding the APXn's (802.11N Airport express) inability to consistently be seen by the Airport Utility.
    this just worked finally for me now and have tested this 7 times and all seems ok now..
    Simply: when APXN in list, save configs, reset to factordeafuts, downgrade to 7.3, upgrade to 7.3 and reinstate .configs.
    UPdate: a probable work instruction that seems to consistently work.
    Here is the work instruction i used.
    (1) turn off all other WIFI base stations where you are that you can. (important I believe)
    (2) turn off airport in your mac
    (3) connect troublesome APXN to mac via ETHERNET cable. Set DHCP on your mac or some address in IPV4
    (4) power off and on the APXn  (yes again )
    (5) whilst it is powering up, use a pen of toothpick to RESET the APXn again (i think this causes something to move around inside the magic-ware)
    (6) the light will flash amber (no network to connect to)
    (7) launch /utilities/airport utility.app
    (8) the one and only APXn appears in the list
    (8.5) optional: (cross fingers and legs :))
    (9) when profile comes back, use FILE/SAVE a COPY AS to the ~/desktop to save the complete profiles and settings of what you have in there currently.
    (10) select the one and only APXn and perform a airport utility.app/base station/ RESET TO FACTORY DEFAULTS - and wait for 30 secs and then it will restart
    (11) when complete, quit and relaunch the /utilities/airport utility.app
    (12) the APXN will be as when you bought it (pristine and no stuff in it from you)
    (13) connect your mac back to internet via ethernet if possible. (avoid the wireless just to be sure but at this stage you could reinstate all your exiting wireless infrastructure)
    (14) select the one and only APXn AGAIN and perform a airport utility/base station/ UPLOAD FIRMWARE and select version 7.3 (back level) . THe firmware will load into APXn 0%-100% guage and then it will restart.
    (15) when complete, quit and relaunch the /utilities/airport utility.app and it will warn that one of the basestations (the only on the list - the APXN) has later FIRMWARE available for it. [This is 7.3.1].
    (16) reply OK to UPLOAD NEW 7.3.1 firmware. (yes yes I realise ths sounds silly but it works ok ) 7.3.1 Firmware will up load into the APXN as above and restart will take place.. so say 120 seconds.
    (17) quit and relaunch the /utilities/airport utility.app. THE APXN will appear as before as now with 7.3.1.
    (18) just to make sure, (we're not quite finished), remove the ETHERNET cable. If not already done form previous optional step, ENABLE the AIRPORT (WIFI) on your mac.
    (19) power OFF then power ON the APXn.. wait for the usual 70 secs..
    (20) Again, to be sure, QUIT and RESTART the /utilities/airport utility.app, the APX as factory default with amber icon will appear in the list [along wit the rest of your apple airport base stations).
    (21) Select it in the list fo MANUAL and the configuration will be read quickly.
    (22) do this (steps 18-21) 3 or 4 times to see that it is consistent. (I this it 7 before posting this).
    last step...
    • select the APXN (default settings) and IMPORT the save configuration file (~/desktop/nnn.baseconfig) (all it) from the ~/desktop. Ignore any errors (untick them), add a password for the base station and UPDATE!
    • wait for the usual 70 secs.
    • without quitting the /utilities/airport utility.app, the UPDATED APXN with your configuration will be in the list.
    NOw try and selectit for manual and it should respond in time without timing out.
    Test by powering off and removing from wall socket and moving around too to make sure you can SEE it in the /utilities/airport utility.app and select it for MANUAL CONFIGURATION.
    After many days of frustration on weekend and over night, this appears to have worked ok for me.
    (now to work out the AEBSn port forwarding issue - it wont work).
    HTH
    w

  • Why doesn't the AEBS 802.11n support NTFS?

    I am wondering why users need to go through hoops to make the $200 AEBS 802.11n recognize NTFS formatted disks. Is it really that complicated for Apple engineers to add this support? Is there any way to reach Apple tech and request this? Or is asking for NTFS support utterly ludicrous and fundamentally not feasible. If it is futile to hope for Apple to add support for NTFS to the AEBS 802.11n, then how does one go about returning - who to contact to return and get the money refunded.

    Hello durlov. Welcome to the Apple Discussions!
    ... how does one go about returning - who to contact to return and get the money refunded.
    Here is Apple's Return and Refund Policy.

  • Gigabit vs. Fast Ethernet (AEBS 802.11n)

    Hi,
    I have an AEBS 802.11n that I bought back in September 2007. It currently has the 7.2.1 Gigabit Ethernet firmware on it. I want to revert back to older firmware (because of some file transfer problems I have been having) and I see my choices are 7.2 Gigabit Ethernet, 7.1.1 Fast Ethernet, 7.1 Fast Ethernet. I am not sure which one to choose. Is it OK to put Fast Ethernet firmware on the AEBS even if it currently has Gigabit Ethernet firmware? What is the difference between those?
    Thanks.

    You should choose "7.2 Gigabit Ethernet".
    The older versions are for the Airport Extreme N Base Station model previous to the one you own, which had only 100Mbps ethernet ports.

  • Unusual setup experience on AEBS 802.11N

    I got my new AEBS 802.11N only 3 days ago, this was intended to upgrade my old AEBS 802.11b/g device. I installed the new Airport Utility software on my MacBook Pro, it went through the usual setup steps.
    My MBP saw the old AEBS when Airport Utility was open for first time, I saved the config file of the old AEBS onto my MBP, shut it down and then started up the new AEBS 802.11N.
    Since new AEBS device was at factory default, I imported the old AEBS config file into new AEBS, noticed that it would automatically set the Wireless security to None. The old config file definitely had the security settings on WPA/WPA2 Personal.
    After applying the config to new AEBS noticed that it will not even advertise the SSID which I had set and yellow light was lit steady, probably meaning - no security enabled.
    My MBP's Airport will not see the new AEBS' SSID no matter what I tried WEP, WPA, WPA2, even tried joining it manually with no security. Occasionally when security was set to None, the SSID would appear on my MBP momentarily then when I try to join it, it would say "Error Joining network".
    I do have Airport Extreme Update 2007-001 installed too, even a reboot of my MBP did not help. I even reset the new AEBS to factory default and started fresh, it still did not work, it simply will not advertise it's SSID even when setting for Closed Network was left unticked in the Wireless Options pane and network mode was in Create a Wireless Network??
    However I was able to get to the Internet when using the Ethernet ports on new AEBS which was connected to a DSL Modem but not on Wireless because the SSID is not advertised??
    Next I fired up my MacMini which I had been using as a Media Center, it came on and saw the new AEBS SSID and joined it just fine at 54Mbps 802.11g (MacMini has no N) by this time I had the new AEBS set to WPA/WPA2 Personal security. ??
    So I went in and tinkered further with the new 802.11n AEBS, I decided ah well lets create a WDS network pairing with my old AEBS, I set the new AEBS to WDS Main and old AEBS as WDS relay.
    The new AEBS decided to announce Network Status as Error WDS, I went in and set the correct MAC addresses for the peer-to-peer WDS and then suddenly at this point the new AEBS refused to restart?? I really thought ah well it's time to call Apple?? Then I decided to unplug power source wait 60 seconds and started up the new AEBS again, it still reported Error WDS probably because old AEBS was also off by then.
    I decided to go back to "Create a network" and suddenly voila the new AEBS started to work, the SSID was appearing on my MBP's Airport pane and I could join it. My MacMini was at this point happily chugging along on Wireless Internet as well. However my X-Box360 wireless will not join even when I selected WPA, it worked fine on my old AEBS in WPA Personal security mode.
    There is something not right with the new AEBS 802.11N that I got, could it be a firmware issue? I have version 7.0 on mine. Just out of curiousity, I restarted my old AEBS and it works fine on 802.11b/g with all my devices including the XBox360.
    My MBP reports it's only running at 144Mbps on the new 802.11n AEBS, is this right? I thought N could go higher or could it be because I have radio mode set at 802.11n (802.11B & G compatible) ??
    Anyway thought it was worth reporting this.

    I discovered something new with these AEBS 802.11N (firmware ver 7.0) devices last night.
    It seems when I set it on Create Wireless network, 802.11n (b/g compatible) with WPA/WPA2 security and Channel selection set to Automatic (13), the unit will not advertise it's SSID even when Closed Network is deselected?
    My MBP C2D and PB 15in will not pick up the SSID at all.
    Howver when I switch the Channel selection from Automatic or anything other than channel 13, the SSID is picked-up by the MBP and PB and able to join the network perfectly ??
    Has anyone out there discovered this issue with the new AEBS 802.11n? Does anyone have fix for it yet?
    However my MacMini C2D seem to chug along just fine in any setting i select on the AEBS?
    XBox360 only works in No security settings.
    MBP C2D, MacMini C2D, PB Alu 15in.   Mac OS X (10.4.8)  

  • Win xp unable to print using AEBS 802.11n

    I have a PC with winxp. Trying to print through AEBS 802.11n causes my printer to freak out. I tried to print this page, and the printer kept printing blank pages over and over. It prints one line of numbers/letters at the top of the page.
    I am able to print fine directly from the usb port on the PC.
    thanks
    roger

    Try installing Bonjour for Windows on your XP box. Available here: http://www.apple.com/support/downloads/bonjourforwindows.html
    This has solved printing problems for me on XP machines on several mixed Apple and Wintel networks.
    Hope this helps.

  • AEBS 802.11n only connects at 54Mbps?

    http://img266.imageshack.us/img266/6168/airportwifi1dm6.png
    im wondering if this the proper connection speed for the AEBS 802.11n im on wifi so im not connected to my router via ethernet, and im sue a MacPro with a preinstalled AirPort Extreme card.
    any suggestion on how to get a faster transfer speed/rate?
    thank you very much!

    thank you very much for your time.
    alright i applied that to the airport i did the 802.11n 5GHz option
    and it states in my network utility im connected at Link Speed: 270mb so i'm assuming thats the proper speed?
    its been a quite long time since ive messed around with wireless and all that, and im new to the apple wireless hardware.
    i mean the connection is fast and great but im just wondering which option is better to use for a faster connection?
    thanks again!

  • AEBS 802.11n - what speed are you seeing ?

    I consistently get around 4.5 MB/s syncing from Mac to Apple TV over wireless, using AEBS 802.11n (5 GHz) network.
    Is this normal experience for other users ? Seems slow to me.
    What would be "normal" for an 802.11n network ?
    Baron.

    Well it all depends on your setup and where the bottlenecks are. Having the tape drives attached directly to the EMC is obviously faster than having it backup over the network to another media server. It also depends how fast the EMC is itself at serving the data. Then there is the type of data you are backing up, lots of small files will take longer to backup than few large files (with any backup tool).
    I have my tape drives fibre attached and the EMC therefore backs up to its attached drives via that.
    Personally I am seeing around 35MB/s, but in lab tests we've seen much higher than that. Our EMC is quite old and that is to LTO-2 tape drives.

  • AEBS 802.11n, Crashing while using bittorrent

    Hi, I have recently purchased an AEBS 802.11n (gigabyte ed. and using the 7.2.1 firmware) and am experiencing some problems using bittorrent.
    First off, I use azureus for my torrents, and with my former linksys router I had no issues. However since purchasing the AEBS I have tried multiple torrents now, and seemingly randomly during the transfer I loose wired/wireless connectivity to my router and am unable to restore it. When looking at the actual base station though the status light is still green, but going through my mbp the device will not appear when I scan for base stations. The only way to fix this problem is to unplug/replug the router.
    This happened with the first AEBS and thinking it may be an error with the actual router, I returned it. However, after unpacking the new one, configuring it... I am having the exact same issue. I haven't experienced the router crashing any other times outside of using bittorrent, so I am unable to pinpoint whether this is something random or not. However it is almost a sure bet that letting azureus run for a few minutes will crash it. Furthermore upon restarting the router, all of its logs seem to clear so I can't even begin to troubleshoot this.
    I can't see how a $60 linksys router is able to outperform this very nice offering from apple, and I really would like to see this problem fixed. I hope this doesn't come down to tweaking some rare setting in the bittorrent client as I have many people that use my network weekly and it will be an increasable pain to take them through some unique setup which should not be required.
    If anyone has any ideas let me know, I am fairly competition with computers and networking issues and willing to do whatever is needed to fix this. Thanks in advance.

    I'm using Azureus 3.0.2.2. However this really shouldn't be an issue of client settings or what not.
    The fact of the matter is, I can sit here on my friends $30 d-link, and download from BT just fine, close my laptop, open it at my house, continue downloading/seeding, and almost guarantee a crash... with the exact same settings. Furthermore how can I expect anyone on my network to dig through their respective clients settings just to use my network, and the first time someone forgets... poof router/network locked.
    This is definitely a problem with the router, however I'm not sure if its a firmware or hardware issue. Hopefully this is a bug that they will be able to fix, if not the AEBS is going straight back.
    I still haven't had a chance to call apple on the matter, as I am away on business... I will be returning Monday and hopefully they have some answers.

  • Lose Network Connection w/AEBS 802.11n when transferring large data amounts

    Hi,
    I have a LaCie 500GB external hard drive that is connected to my AEBS 802.11n via a USB hub. Lately, when I am backing up my MacBook Pro to that drive, transferring 5GB or so of data, I notice that my MacBook Pro loses connection with the AEBS (i.e. the network goes down) right smack in the middle of the data transfer. I either have to reboot the MacBook Pro -- or -- unplug and replug the AEBS to reestablish connection.
    I was just wondering if this sort of network connectivity loss is being experienced by other people doing large data transfers over the AEBS to an external drive?
    Thanks.
    Message was edited by: jmFightSpam

    I hate to be the one adding a "me too" post, but, me too!
    When I try to open iPhoto (library stored on a USB drive attached to AEBSn) the AEBSn crashes, flashes orange once or twice and then restarts. Currently running firmware 7.2 because 7.2.1 wasn't allowing me to reconnect to AirDisks after MacBook went to sleep. If the drive is connected directly to my MacBook there is no problem.
    If anyone, anywhere has any idea, I'd be very grateful!

Maybe you are looking for