Thread View: comp.sys.next.sysadmin
3 messages
3 total messages
Started by J.B. Nicholson-Owens
Sun, 26 Jul 1992 20:37
Windowserver can't find port when SLIP is up
Author: J.B. Nicholson-Owens
Date: Sun, 26 Jul 1992 20:37
Date: Sun, 26 Jul 1992 20:37
25 lines
1562 bytes
1562 bytes
I've followed all the directions that came with the SLIP 920506 package and I'm running 2.1 extended and using Mamakos' SLIP package (nice package by the way). When I get the proper IP address and complete host name (all four parts of the name, not just the first) in NetManager and reboot, SLIP comes up and connects with the SLIP server. But then the windowserver says it's sleeping and then it says it can't find a port. SLIP, meanwhile, seems to be connected fine and doing some data transfer (I can see both send and receive lights flashing) of some kind. I don't know what it's trying to do. I just get continuous messages saying windowserver is sleeping or it cannot find some port. I never get a login window. Also, before any of this happens, the machine puts up the 'can't find parent NetInfo server, press 'c' to continue without parent server' prompt, even though i configured the machine (in NetMgr) to be a non-netinfo machine. If I hit 'c' it continues up to the point I describe above. Could someone help me to get SLIP running? Any help you could provide will be most appeciated. Thanks. -- -- Jeff (jeffo@uiuc.edu) -- No NeXTmail please
Re: Windowserver can't find port when SLIP is up
Author: Louis A. Mamakos
Date: Thu, 30 Jul 1992 12:54
Date: Thu, 30 Jul 1992 12:54
6 lines
692 bytes
692 bytes
It sounds like the SLIP problem you are having is being caused by your NeXT thinking it is on a "NetInfo Network" and it trying to bind to a NetInfo master server which it will never find. louie
Re: Windowserver can't find port when SLIP is up
Author: J.B. Nicholson-Owens
Date: Thu, 30 Jul 1992 17:00
Date: Thu, 30 Jul 1992 17:00
16 lines
1176 bytes
1176 bytes
louie@sayshell.umd.edu (Louis A. Mamakos) writes: >It sounds like the SLIP problem you are having is being caused by your >NeXT thinking it is on a "NetInfo Network" and it trying to bind to a >NetInfo master server which it will never find. Yes, that was the problem (although my wife and I could have sworn that I hit non-netinfo network). And thanks for the response. I'd also like to thank two other people, they know who they are, I'm not sure broadcasting their addresses is a wise idea (I never received explicit mail from them saying I can do so and I wouldn't want them having to fend off tons of other people seeking advice). -- -- Jeff (jeffo@ux1.cso.uiuc.edu) -- No NeXTmail please
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads