 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / General / General / October 2008File, Screen, and Printer Sharing Stopped Working
My wife tried to print yesterday, using the wifi network to reach the printer attached to my Intel iMac from her G5 iMac. It wouldn't print. Printer sharing, file sharing, and screen sharing all used to work, but now none of them do. The two computers do appear in the "Shared" lists in one another's Finders, but connection always fails. I hadn't changed anything in Network or Sharing Preferences since forever. The only change made recently that might affect the network is the upgrade from 10.5.4 to 10.5.5. However, file and screen sharing are almost never used, and printer sharing not very often, so I don't know for sure that the sharing failure didn't preexist the upgrade. Ping usually works in both directions using the IP addresses, but never works using the names that appear in Sharing Preferences (and in the Finder's Shared lists), yielding the message "ping: cannot resolve [name]: Unknown host". How can the host be unknown if it's been found on the network and put in the "Shared" list? Changing the computers' names causes the Finder lists to be updated. And why would pinging with IP address work only some of the time? I have tried messing around with the Preferences and resetting the router, but nothing I've done makes any difference.  SignatureJohn Varela Trade NEW lamps for OLD for email. > My wife tried to print yesterday, using the wifi network to reach the > printer attached to my Intel iMac from her G5 iMac. It wouldn't print. [quoted text clipped - 18 lines] > I have tried messing around with the Preferences and resetting the > router, but nothing I've done makes any difference. Two questions: 1 what are the IPs of _both_ computers? 2 have you recently restarted either or both computers? Signatureemail to oshea dot j dot j at gmail dot com. > Two questions: > > 1 what are the IPs of _both_ computers? 192.168.0.101 and .102 > 2 have you recently restarted either or both computers? Daily. SignatureJohn Varela Trade NEW lamps for OLD for email. >> Two questions: >> >> 1 what are the IPs of _both_ computers? > > 192.168.0.101 and .102 Okay. Are they fixed IPs, or are you using DHCP?? If using DHCP, are you reserving the IPs? Can either or both machines ping the router? > >> 2 have you recently restarted either or both computers? > > Daily. Well, that eliminates one possible problem. Signatureemail to oshea dot j dot j at gmail dot com. >>> Two questions: >>> [quoted text clipped - 3 lines] > > Okay. Are they fixed IPs, or are you using DHCP?? If using DHCP, I had confirmed the IP addresses in Network Preferences and they were as I had expected them to be. Interesting. I'm sure I had assigned .101 and .102 as Static DHCP addresses in the router, but when I looked, both computers had dynamic addresses. So I changed them to static and it didn't help anything. We get power outages around here so maybe the router's settings somehow got changed in a power-up. SignatureJohn Varela Trade NEW lamps for OLD for email. On 06/10/2008 22:00, in article 0001HW.C50FF4A100101536B01AD9AF@news.verizon.net, "John Varela" <OLDlamps@verizon.net> wrote: >> Two questions: >> [quoted text clipped - 5 lines] > > Daily. Are you absolutely sure those are the IP addresses of your 2 computers? If both can log on to the router then you should be able to see exactly which computers are attached to it and their own IP addresses via the router interface pages. If those addresses are correct then they have been fixed manually and DHCP should not be active ( ie: The router would not be allocating IP addresses itself ). SignatureWelsh Gas Remove usual to reply direct. > On 06/10/2008 22:00, in article > 0001HW.C50FF4A100101536B01AD9AF@news.verizon.net, "John Varela" [quoted text clipped - 16 lines] > should not be active ( ie: The router would not be allocating IP addresses > itself ). Absolutely sure, and as I say this was working for months and then stopped working for no apparent reason. Also, and this is really weird, I recalled that there was one more sharing item that I hadn't tested and damned if it didn't work: iTunes. The iTunes list on one computer pops right up on the other and the tunes play. What is it about iTunes that it can connect to the other computer while the Finder cannot? SignatureJohn Varela Trade NEW lamps for OLD for email. > My wife tried to print yesterday, using the wifi network to reach the > printer attached to my Intel iMac from her G5 iMac. It wouldn't print. [quoted text clipped - 18 lines] > I have tried messing around with the Preferences and resetting the > router, but nothing I've done makes any difference. Did you look at the console or system logs while this was happening? That's usually the very *first* thing I do, since error messages usually show up there first. SignatureSend responses to the relevant news group rather than to me, as E-mail sent to this address may be devoured by my very hungry SPAM filter. Due to Google's refusal to prevent spammers from posting messages through their servers, I often ignore posts from Google Groups. Use a real news client if you want me to see your posts. JR >> I have tried messing around with the Preferences and resetting the >> router, but nothing I've done makes any difference. > > Did you look at the console or system logs while this was happening? > That's usually the very *first* thing I do, since error messages usually > show up there first No, because I don't know how to read them, but I just now did so after an unsuccessful ping and there were no messages in the log files. I looked in All Messages and system.log. Was I looking in the right places? SignatureJohn Varela Trade NEW lamps for OLD for email. > Ping usually works in both directions using the IP addresses, but never > works using the names that appear in Sharing Preferences (and in the > Finder's Shared lists), yielding the message "ping: cannot resolve > [name]: Unknown host". How can the host be unknown if it's been found > on the network and put in the "Shared" list? Changing the computers' > names causes the Finder lists to be updated. The names in that list are likely just the host names. With utilities like 'ping', you'll need the entire qualified name. If you are relying on Bonjour for name resolution, then the fully qualified name will be something like: hostname.local > And why would pinging > with IP address work only some of the time? That points to a different connectivity problem likely having to do with your particular network configuration. SignatureSend responses to the relevant news group rather than to me, as E-mail sent to this address may be devoured by my very hungry SPAM filter. Due to Google's refusal to prevent spammers from posting messages through their servers, I often ignore posts from Google Groups. Use a real news client if you want me to see your posts. JR >> Ping usually works in both directions using the IP addresses, but never >> works using the names that appear in Sharing Preferences (and in the [quoted text clipped - 9 lines] > > hostname.local How did you know I call my home network "local"? With and without the .local appended produces the same outcome. Anyway, using the IP address should either work or not work, but sometimes it does and sometimes it doesn't, unpredictably. Just now, pinging 192.168.0.1 (the router) produces immediate good pings (as it always does); adding 01 to the address to make it 192.168.0.101 produces Ping has started ... ping: sendto: No route to host ping: sendto: Host is down ping: sendto: Host is down ping: sendto: Host is down ping: sendto: Host is down PING 192.168.0.101 (192.168.0.101): 56 data bytes --- 192.168.0.101 ping statistics --- 10 packets transmitted, 0 packets received, 100% packet loss The other computer is up and awake. >> And why would pinging >> with IP address work only some of the time? > > That points to a different connectivity problem likely having to do with > your particular network configuration. That could be it. I'm afraid the repeater is flaky, but wife's computer (the one that needs the repeater) has had no problem going through the repeater to the router to the Internet. My computer (which speaks directly to the router) occasionally loses Airport connectivity for no apparent reason and even though iStumbler reports a strong signal. Connectivity is usually restored by turning Airport off at the menu bar widget and then turning it back on again. That seems unrelated to this other problem, however, because when Airport is lost it's lost to all apps; there's no some things work and some things don't about it. SignatureJohn Varela Trade NEW lamps for OLD for email. > >> Ping usually works in both directions using the IP addresses, but never > >> works using the names that appear in Sharing Preferences (and in the [quoted text clipped - 11 lines] > > How did you know I call my home network "local"? That's how you reference any Bonjour-enabled device on the network. SignatureSend responses to the relevant news group rather than to me, as E-mail sent to this address may be devoured by my very hungry SPAM filter. Due to Google's refusal to prevent spammers from posting messages through their servers, I often ignore posts from Google Groups. Use a real news client if you want me to see your posts. JR >>> Ping usually works in both directions using the IP addresses, but never >>> works using the names that appear in Sharing Preferences (and in the [quoted text clipped - 11 lines] > > How did you know I call my home network "local"? Since the advent of OS X all Macs show up on the local net as something.local unless the user goes out of his way to change it. > With and without the .local appended produces the same outcome. > Anyway, using the IP address should either work or not work, but [quoted text clipped - 3 lines] > pings (as it always does); adding 01 to the address to make it > 192.168.0.101 produces Okay, you can ping the router. > Ping has started ... > [quoted text clipped - 9 lines] > > The other computer is up and awake. The other machine is not on the network. I'd say that you're using fixed IPs and that there's a connectivity problem. Need more data. > >>> And why would pinging [quoted text clipped - 6 lines] > computer (the one that needs the repeater) has had no problem going > through the repeater to the router to the Internet. Both machines are connected using wireless? What happens if you use a wired connection? > My computer (which speaks directly to the router) occasionally loses > Airport connectivity for no apparent reason and even though iStumbler > reports a strong signal. That, unfortunately, is a different problem and is a known problem. 10.5.5 was supposed to fix it. > Connectivity is usually restored by turning > Airport off at the menu bar widget and then turning it back on again. > That seems unrelated to this other problem, however, because when > Airport is lost it's lost to all apps; there's no some things work and > some things don't about it. Signatureemail to oshea dot j dot j at gmail dot com. > Both machines are connected using wireless? What happens if you use a wired > connection? Not tried, nor easily tried. A lot of unplugging and hauling to do. Both machines have Internet connectivity, and both Finders see the other computer over the wireless LAN. >> My computer (which speaks directly to the router) occasionally loses >> Airport connectivity for no apparent reason and even though iStumbler >> reports a strong signal. > > That, unfortunately, is a different problem and is a known problem. 10.5.5 > was supposed to fix it. It didn't fix it here. Maybe for both these problems I have to wait for 10.6. SignatureJohn Varela Trade NEW lamps for OLD for email. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.