Timeline for Should I block incoming connections from "netbiosd"?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 21, 2016 at 17:40 | history | edited | mmmmmm | CC BY-SA 3.0 |
typo
|
| Feb 11, 2014 at 12:53 | comment | added | orome | A related answer also supports blocking or disabling netbiosd. | |
| May 10, 2013 at 8:16 | comment | added | athena |
→ raxacoricofallapatorius: you most probably blocked netbiosd access the first time you entered a Windows network where you were immediatly bombed by all Windows neighbor netbios broadcasting like a flock of geese. MacOS X asked you if you wanted to accept or block this unsollicited access. I bet that you blocked it. And this was an excellent reflex ☺!
|
|
| Feb 12, 2013 at 15:20 | vote | accept | orome | ||
| Feb 12, 2013 at 15:20 | comment | added | orome | I would be using the network exclusively for access outside of the hotel or client: cloud, mail, Web, etc. Some networks will require a password though, if that matters. | |
| Feb 12, 2013 at 15:18 | comment | added | mmmmmm | How are you using the networks netbiosd will affect Windows file sharing and possible windows authentication but not web use etc. | |
| Feb 12, 2013 at 15:16 | comment | added | orome |
Will I still be able to use arbitrary networks (e.g., wifi in a client's conference room; hotel wifi) if I block netbiosd incoming connections?
|
|
| Feb 11, 2013 at 16:54 | comment | added | orome | So is it safe to say that if I have no Windows machines there will be no consequences? Also: I don't recall ever setting this; could it somehow have happened automatically? | |
| Feb 11, 2013 at 14:40 | history | answered | mmmmmm | CC BY-SA 3.0 |