Connect to who?

unlearnthetruth

Recycle Me!
Ok so when i use "connect to server" to browse the local area net, or appletalk, i get repeated listings for computers, as you can see in the attach... i know it's inaccurate... any ideas? Additionally, each listing has a different afp:\\ address... and only one of them will work... i'm perplexed
 

Attachments

  • finderscreensnapz001.jpg
    finderscreensnapz001.jpg
    78.4 KB · Views: 77
I've seen this same effect. I think it may be a bug in OS X, but what you should do is find the computer (or call the owner of the computer) and confirm the IP address. Then use the corresponding entry.
 
well a lot of time i don't know who i'm looking at, i'm just looking... i think i remember seeing on some website that there is a file i can delete or something that will correct this... is there anyway to clean up the list?
 
I have this. If you look at the IPs I have one computer with the IP given to it from the DHCP server (10.0.1.x) and one with a 192.168.x.x IP, which is given to it when my DHCP server fails.

It could be that it is caching the information somewhere and displaying all IPs that it can find based upon the computer (MAC?? or something similar). It would then make sense that there is a file cache that you can delete.

R.
 
hrm..... still no luck with this.... it makes lurking about on my network a lot more inconvenient.... no one has any ideas? i tried restarting appletalk, and making it rebuild it's little registry or whatever, but that didn't work........ grrr......
 
1. Turn off AppleTalk.

2. From the Terminal enter...

sudo rm /var/slp.regfile

... followed by your login password.

3. Re-enable AppleTalk.
 
Code:
[localhost:~] gregoryk% sudo rm /var/slp.regfile
rm: /var/slp.regfile: No such file or directory

is what i get when i try that... any ideas?
 
Interesting that the file doesn't exist on your system, but maybe you've never enabled AppleTalk, using TCP/IP instead...? I can only speculate.

I should have mentioned that in order to eliminate all the false server listings you need to delete the slp.regfile on all the affected machines on your network, not just on your own machine.
 
Back
Top