RE: [OT] network problems guru req'd

["Paul Gordon" <paul_gordon@xxxxxxx>]

OK Stuart, lets work through this methodically....

First off, can you post a list of all your devices, their OS versions, 
workgroup (or domain) names, and their IP addresses...

Machine
Name           
OS               
IP          Workgroup
============           
==               
==          =========
1:
2:
3:
4:
5:
.
.
.etc...

Your symptoms seem to suggest that there is no browse master available on
your network when TCPIP is the only protocol installed (or that Win98 
clients can't reach one). There was a known problem with this with earlier
windows versions, but to my knowledge it only affected WFWG3.11...

In the meantime, here are a few pointers which may (or may not!)
help...

- Make sure that you have NetBIOS over TCPIP enabled on all machines
- Provide a NetBIOS Name service (ie WINS) if possible, or place an LMHOSTS
file on each machine. (If your IP's were static, then putting both a HOSTS
_and_ an LMHOSTS file on every machine could help...)
- On one of the "invisible" machines, type "nbtstat -n"
at a DOS prompt, and 
post the results here...

Do you have access to any of the Windows NT resource kits? (I think any
version would do) - there is a tool in there called "Browmon"
which is 
invaluable for determining the state of the browser services on the 
network... You need to determine which of your machines is the master 
browser on your network, - in theory, it should be one of your windows 2000
machines.

Can you try using NetBEUI instead of IPX? - when you install IPX on all the
PC's on your network the redirector and server networking components in
Windows 98 communicate with the IPX protocol directly without NetBIOS, so
it 
makes it a bit tricky to troubleshoot netBIOS problems!

Could you not use static IP assignments on your machines?  - barring a
laptop that you might use on other networks, what reason is there for 
needing your home LAN to use dynamic addressing?

We *can* get to the bottom of this!

Paul G.




>From: "Stuart Booth" <stuart@xxxxxxx>
>Reply-To: ukha_d@xxxxxxx
>To: ukha_d@xxxxxxx
>Subject: RE: [ukha_d] [OT] network problems guru req'd
>Date: Tue, 14 May 2002 20:42:15 +0100
>
>Earlier in the month it was pointed out to me in no uncertain terms
>that I was utterly, utterly wrong about needing IPX/SPX to enable
>my computers to browse their network neighbourhoods.
>
>On 1 May 2002, at 8:52, Chris Bond wrote:
>
> > > I am still utterly convinced I need IPX/SPX for Network
> > > Neighbourhood to work !!!
> >
> > Fraid not - TCPIP is all you need (with Client for Microsoft
Network).
> > TCIPIP is certainly a better stack that IPX/SPX
>
>d8-)
>
>Well, I've got rid of IPX/SPX and my network is nigh on ****ing
>unusable !!!
>
>Win98 can't browse anything in Net. Neigh. "Unable to browse
the
>network".
>
>My Win98 machine can see one of the machines but not Server in
>any way shape or form. Running \\Server gets an error. It can
>ping it fine though!
>
>Win2000 cannot see the Win98 machines in NN, only by running
>\\<machine name>
>
>Win2000 machines *can* see each other in their own NN though!
>Hoorah! One success in a bleak world right now.
>
>Not being able to browse the NN makes using the Fuji's a bit
>awkward as I'm then having to make new folders/shortcuts
>and/or use the virtual keyboard instead of browsing a nice
>desktop icon.
>
>I don't have that complicated a configuration: DHCP on Server (via
>SyGate) which *is* allocating IP addresses to all clients from its
>own fixed IP. All clients get their TCP/IP IP via server
assignment.
>
>For me, this is totally and utterly unacceptable, no matter how
>many of you tell me otherwise! ! ! <BIG smiley grin>.
>
>If somebody can tell me their secret, I'm listening, but until then,
it's
>back to IPX/SPX for me.
>
>Stuart
>
>--
>Stuart Booth
>Somewhere in Buckinghamshire, England, UK
>
>stuart@xxxxxxx



_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com

Yahoo! Groups Sponsor

ADVERTISEMENT

Height:	4 5 6 7  ft 0 1 2 3 4 5 6 7 8 9 10 11 in
Weight:
Sex:	F M

For more information: http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx 
Subscribe:  ukha_d-subscribe@xxxxxxx 
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx 
List owner:  ukha_d-owner@xxxxxxx

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.