| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 125492 | 2012-07-02 09:19:00 | The Apple guys are going to laugh at this one... shared folders | Agent_24 (57) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1285476 | 2012-07-02 11:19:00 | Since we're asking stupid questions about MACs :D How do you create a shortcut on the desktop, in OSX, to a share that's on a Windows PC or a NAS device? |
CYaBro (73) | ||
| 1285477 | 2012-07-02 11:21:00 | img141.imageshack.us Network>properties of the adapter you're using to connect to the network Doesn't seem to have helped :( Have you tried just using the ip address? Windows cannot access \\192.168.0.4 Error code: 0x80004005 Unspecified error |
Agent_24 (57) | ||
| 1285478 | 2012-07-02 11:50:00 | Turns out the OSX inbuilt firewall was blocking the connection. Everything is working now... :blush: Thanks for the help! |
Agent_24 (57) | ||
| 1285479 | 2012-07-02 11:54:00 | One would think a refused connection could be described better than "Unspecified Error" :groan: | fred_fish (15241) | ||
| 1285480 | 2012-07-02 12:23:00 | On the windows end it probably didn't know what was going on, the remote machine was broadcasting ARP but when windows tried to handshake nothing happened. A connection refused is different (I think) Firewalls dump any info that doesn't fit the rules so nothing is sent back, whereas a connection refusal means the remote machine sends back a response | The Error Guy (14052) | ||
| 1285481 | 2012-07-02 13:30:00 | Same goes for "No Response from target". Also, firewalls don't have to drop packets, a reject is equally effective. With the amount of network traffic generated by today's machines "pretending you are not there" is a bit silly. :) |
fred_fish (15241) | ||
| 1285482 | 2012-07-02 19:38:00 | Turns out the OSX inbuilt firewall was blocking the connection. Everything is working now... :blush: Thanks for the help!So if you had read my link the first thing it mentions is the firewalls:badpc: Now I will laugh, it seems window users dont follow instructions:lol: |
plod (107) | ||
| 1285483 | 2012-07-02 21:05:00 | So if you had read my link the first thing it mentions is the firewalls:badpc: Now I will laugh, it seems window users dont follow instructions:lol: looked at the link and its quite good. But I disagree with the part that says "Both computers may need to have their firewalls turned off " I never turn off the firewall on windows or MAC's, and theres never a problem, and the reason being if you are using a software firewall, and its set to allow the complete IP address of the router through theres nothing to stop it. Most people dont set their firewalls to allow traffic from within the LAN and end up having problems. Setting the LAN as as described still blocks attacks from outside on the WAN. |
wainuitech (129) | ||
| 1285484 | 2012-07-02 21:31:00 | So if you had read my link the first thing it mentions is the firewalls:badpc: Now I will laugh, it seems window users dont follow instructions:lol: Seeing as I had not installed a firewall myself I skipped over that, should have realised it would come with one, but didn't really think about it! There was no obvious "Firewall" in System Preferences either, just "Security" - Not that I am blaming OSX, but it wasn't obvious to me. |
Agent_24 (57) | ||
| 1285485 | 2012-07-02 22:16:00 | Because I have no idea what I'm doing :lol: We have all been there.:confused: |
mikebartnz (21) | ||
| 1 2 3 | |||||