| Title: | Microsoft Windows 95 ("Chicago") |
| Notice: | Please read topics 1 to 22 before writing anything |
| Moderator: | EEMELI::BACKSTROM |
| Created: | Sun Nov 13 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2958 |
| Total number of notes: | 19968 |
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2464.1 | Is WINS enabled? | TURRIS::twuwuv.zko.dec.com::hower | Mon Sep 30 1996 09:45 | 6 | |
| 2464.2 | CPCOD::CODY | Mon Sep 30 1996 11:23 | 6 | ||
| 2464.3 | FRSBEE::BROOKS | Natural Born Hackers | Mon Sep 30 1996 14:19 | 1 | |
| 2464.4 | WRKSYS::DEROSA | It's only a movie..... | Wed Oct 02 1996 12:41 | 10 | |
| 2464.5 | A very strange fix for this problem | NETRIX::"[email protected]" | Adrian Moore | Thu Feb 20 1997 17:30 | 20 |
Hi all, I think I've hit on a fix for this but I don't understand it. If you add a dummy network card driver into the Windows 95 Network setup then WINS mysteriously works (with WINS enabled). WINIPCFG shows a primary WINS server, and browsing via network neighbourhood works fine. I suspect that adding a network card driver also adds other components which allow WINS to work properly. I suspect these don't get added with just the Dial-up-adapter installation, but I guess I'll have to tear apart the INFs to find out. Comments are most welcome. Thanks & regards, Adrian Moore http://cscnw410.stl.dec.com/ [Posted by WWW Notes gateway] | |||||