Chuck said:
Daddy,
You have an intriguing network. Lots of fun there. ;-)
Node Types either Hybrid or Mixed, no problem there. The dual personality of
Falcon-II is interesting - Configuration 1 (with 802.11g) puts it on the
192.168.1.0/24 subnet, Configuration 2 (without 802.11g) puts it on
192.168.0.0/24 subnet - as 192.168.0.1. And you're using a bridge in both
configurations.
Is Falcon-II providing internet service for Falcon using the bridge? When does
Falcon-II run on 802.11g? What does Falcon do when Falcon-II is on 802.11g?
Falcon, OTOH, is on the 192.168.0.0/24 subnet. What does Falcon do for browsing
when Falcon-II is on 802.11g?
You disabled the browser on Falcon. Did you test its ability to see Falcon-II
(and Micron) when Micron is on the network, and when it's off?
What is the master browser (per Browstat from Falcon-II)?
I note that Micron also has its own internet service.
Let's get a diagnosis of your problem. Take the following code (everything
inside the "#####"). (Did I get the names and ip addresses right)?
Please disable the browser on Micron, and power everything off again to reset.
Highlight then Copy the code (Ctrl-C), precisely as it is keyed, and Paste
(Ctrl-V) into Notepad. Ensure that Format - Word Wrap is not checked.
Save the Notepad file as "cdiag.cmd", as type "All Files", into the root folder
"C:\".
Run it by Start - Run - "c:\cdiag".
Wait patiently.
When Notepad opens up displaying c:\cdiag.txt, first check Format and ensure
that Word Wrap is NOT checked! Then, copy the entire contents (Ctrl-A Ctrl-C)
and paste (Ctrl-V) into your next post.
Do this from all computers, please, with all computers powered up and online.
#####
@echo off
set FullTargets=FALCON-II 192.168.0.1 FALCON 192.168.0.179 MICRON 192.168.0.43
set PingTargets=127.0.0.1
Set Version=V1.05
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% (Targets %FullTargets%) >>c:\cdiag.txt
for %%a in (%FullTargets% %PingTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "net view %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view %%a >>c:\cdiag.txt
)
@echo End diagnosis for %computername% >>c:\cdiag.txt
notepad c:\cdiag.txt
:EOF
#####
--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.
Chuck,
My "intriguing" network? - a story of accretion, and making as minimal
changes as possible for things to work. Short story: Bought the Micron,
Falcon, and Falcon-II over a period of 7 or so years. So each came with an
independent ability to access the Internet. Falcon-II and Falcon have 56k
modems, Micron has a 28.8k modem. After losing battles with Internet
connection sharing a few years back, we basically logon to the Internet
separately from each machine. (Micron and Falcon II have Compuserve, which
has a separate DUN, or something.) The 802.11g adapter is a recent
inexpensive gift and is an addition on a USB port. Turns out there are
indeed unprotected access points in our neighborhood. On an experimental
basis, we use it on and off.
In fact, the impetus for this whole exercise, and my original question, was
a concern that others could see folders on Falcon-II, and so I was hoping to
set it up so that anyone logging onto the Falcon or Micron through our wired
LAN would have access to Falcon-II files, but no one else. Don't know
whether I should be worried, or even worried about Falcon and Micron files.
On my home network problem, I think I've found a fix. I successfully ran
cdiag on the XP machine, but it wouldn't run on the 98SE or 98 machines. The
98SE machine just pulled the file up in Wordpad; the 98 machine said it
needed to have the program associated with file. So I looked at the content
of the file, and it seemed that it was checking to see whether all 3 machines
could ping one another. A-ha.
Last fall, I had to reinstall Win98SE on the Falcon, and had home network
problems after that, which I now remembered trouble-shooting through the
Win98 community newsgroup. I found my lengthy notes, and succeeded in
pinging the other two machines from the network from each of the three. OK.
I then found in my notes that a common problem when you can't browse the
network but can ping the other machines is that a user isn't logged on. As I
think I mentioned earlier in this chain, I had added a "Test" user on the
98SE machine to see whether I could limit access to that user from the XP
machine. (I noticed at that point that the machine had a "user" logged on,
but it was not in Control Panel - Users screen.) No luck in making that
solution work to selectively share folders, so I deleted the Test user. So
in logging on, I was getting the Windows logon screen with no users listed,
and was hitting "Cancel."
So I've gone to Users and created a "DaddySchlich" user with no password.
Booted up that way, and full access was restored. Yea!!
Of course, now I had to hit enter to logon every time! nuts. So I
downloaded TweakUI 1.33. Activated Autologon and Client for Microsoft
Networks as Primary Network Logon, so a Logon screen shows, but it disappears
automatically. Not nearly as elegant as before - when it just booted
straight to Desktop with no logon screen. And there's a beep at the end of
the bootup routine that suggests that something's still not quite right.
So, where I now stand,
1. should I worry about others looking at my files over the wireless link?
(I have a firewall on the XP machine.) If so, should I pursue the Safe Mode
option you first suggested to disable Simple File Sharing? Can I set it up
so that the Falcon boots directly to Desktop, and there is a logged on User
that the XP can validate without more?
2. independently, is there a way to set up the Falcon so it boots directly
to Desktop without showing a Logon screen at all, as it was set up at the
beginning? (Coincidentally, I made an image of my Boot partition this past
weekend, just before starting all this, so I can just restore that image if
need be.)
Chuck, thank you for all your help on this matter. This certainly is not
easy stuff.
What do you think are my options at this point?
Thanks,
Daddy Schlich