[WriteLog] ?Help:WriteLog networking?
Tony
ad6id at qsl.net
Sun Jun 29 19:14:00 EDT 2003
Well, our Writelog network worked pretty well this weekend. Recall it consisted of a Win2000, Win98, and Win95 machine. The Win2000 machine was left belonging to the domain I belong to at work. The other machines belong to a workgroup.
The thing that finally got them all talking was to make all computer names UPPERCASE with no spaces, etc.
We did have to give Win2K login and passwords when linking to it from the other machines, but only once per boot.
Occasionally, we would lose the net spontaneously and have to reconnect. This happened only ~5 times during the contest.
Hope you all had a great contest.
73, Tony, AD6ID
At 08:38 PM 6/23/03 -0700, Andreas KU7T wrote:
>Just on a side note, since I have seen this mentioned a couple of times now:
>
>Having the networked machines be part of a domain DOES work. Tried it
>myself today at work. The networking protocol is transparent at that level
>of course. Workgroups really are domains of the small user. No need to set
>one up as workgroups should work (even though I cannot get it to work, but
>many have...)
>
>
>Andreas, KU7T
>
>
>----- Original Message -----
>From: "Kevin Brown" <kc0czi at midmoskywarn.net>
>To: "'Tony'" <ad6id at qsl.net>; <writelog at contesting.com>
>Sent: Monday, June 23, 2003 8:10 PM
>Subject: RE: [WriteLog] ?Help:WriteLog networking?
>
>
>> You missed precisely what it requires.
>>
>> Contrary to the documentation - your users do NOT have to be part of the
>> 'administrators' group on the machines. However - we found that you do
>need
>> to be logged in with the same username/password on all machines to allow
>the
>> DDE shares to work properly. DDE of course, is a very old and archaic
>> sharing mechanism...so it simply needs to be tolerated... for now (hint,
>> hint).
>>
>> Another issue is to ensure you login as the selected userid at system
>> startup. The shares are made, and then cached when writelog initializes on
>> the machine. Just logging out as one user, then back in as another will
>not
>> suffice. To do that - you will need to run the netsetv.exe (or similarly
>> named - cannot remember) to restart the DDE shares with the proper user
>> attributes.
>>
>> Additionally - workgroups are the way to go - not domains. Not sure that
>> domains wouldn't work - but they take a ton more effort to establish
>(PDC/AD
>> server, etc). A real knuckle-biter for what should be a simple networking
>> effort.
>>
>> An alternative is to download and support the IP Logbook function - but
>know
>> that it requires a Linux machine to run the server code.
>>
>> I spent an entire evening with 5 other networking 'gurus' trying to setup
>> our writelog network last week - this is what we ended up proving was
>> repeatable, time and again. Any minor variations caused
>> inconsistencies...regardless of platform. EXCEPT: win98 seems to always
>> require the user to enter the same userid/password (as you did when first
>> logging into the machine) when making the connection to the server.
>>
>> Again- common workgroup, common userid/password to EVERY machine. Reboot.
>> Try it again.
>>
>>
>>
>> Wayne - please find a way to abandon the DDE api. The IP based
>> client/server code is much better - and more appropriate given today's
>> technology.
>>
>>
>>
>> -----Original Message-----
>> From: writelog-bounces at contesting.com
>> [mailto:writelog-bounces at contesting.com]On Behalf Of Tony
>> Sent: Sunday, June 22, 2003 9:19 PM
>> To: writelog at contesting.com
>> Subject: [WriteLog] ?Help:WriteLog networking?
>>
>>
>> Hi folks,
>> I'm checking out the laptops we used for Writelog logging for last
>year's
>> Field Day, just to make sure...
>> Well, the networking (which worked great last year) will not work. Here
>> are the details:
>> One laptop is running Win98SE the other Win2000.
>> TCP/IP is set for both at fixed IP addresses - 192.168.1.2 and
>> 192.168.1.10. They are the only two connected so far.
>> I can ping both from each other.
>>
>> When I try to connect, I get the Writelog error status window reporting
>> "Lost connection to <name>". The error is the same from either computer.
>>
>> NetBUI is configured on both to use Microsoft networking.
>> The Win98 laptop DOES network fine with my Win98 desktop computer.
>> Writelog works fine between them.
>> I tried the Writelog doc check of running NETSETV9.EXE - it reported
>the
>> "Network is OK" on both.
>> The workgroups are NOT common, though. The win2000 computer can either
>> belong to a domain OR a workgroup but not both. (I'd prefer not to use the
>> win2000 machine as a non domain system as I'd haver to coerce a local
>admin
>> password out of the folks at work).
>>
>> Clues? What did I miss?
>>
>> Thanks & 73,
>>
>> Tony, AD6ID
>>
>> Garlic Valley ARC, W6GGF
>> Gilroy, CA
>> _______________________________________________
>> WriteLog mailing list
>> WriteLog at contesting.com
>> http://lists.contesting.com/mailman/listinfo/writelog
>>
>> _______________________________________________
>> WriteLog mailing list
>> WriteLog at contesting.com
>> http://lists.contesting.com/mailman/listinfo/writelog
>>
>
>_______________________________________________
>WriteLog mailing list
>WriteLog at contesting.com
>http://lists.contesting.com/mailman/listinfo/writelog
>
>
More information about the WriteLog
mailing list