SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!











SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2026, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 06 | December | 2008 ]

<< Previous Message << >> Next Message >>


Date: Sat, 6 Dec 2008 17:33:30 -0800
From: "Jon Harrison" <jharrison@seadog.reno.nv.us >
Reply-To: scoug-help@scoug.com
To: < "scoug-help@scoug.com" > scoug-help@scoug.com >
Subject: SCOUG-Help: ecs peer2peer problem

Content Type: text/plain

I've seen this problem before but can't seem to figure it out this time.

My T-61 (rc5) works fine with peer connecting to other ecs machines, both eCS v 1.1 & 1.2.

But no machines connect to the T61. I have a share defined and I am using same login ID &
password on all machines.

The connection on the T-61 is wireless (genmac 2.20) to a linksys wrt54g which is used as an access
point inside the network (it's not used as the internet connection) and AFAIK is not blocking ports
137-139. I did not install the os/2 firewall with eCS. I have the same problem if I connect via
cat-5.

The requester, messenger, & peer are running on all machines.

[C:\HOME\DEFAULT]net view \\8bells
NET3502: OS/2 error 53 has occurred.
SYS0053: The network path was not found.

An iptrace of this command shows the originating ip sending a netbios udp packet to the T-61 on
port 137 but the T-61 does not answer. The source then drops to the MAC level sending arp requests
until it gets to 192.168.1.0 then it starts over again with the netbios request to the T-61.

I've checked the ibmlan.ini file, server is not hidden.
I've checked protocol.ini, it seems ok.

I've checked rfcnames & rfcbroadcast.

I'm fresh out of ideas.

Again, I can 'net use' from the T-61 to other computers, but not from other computers to the T-61.

What else to check? What is likely preventing the T-61 from replying to net commands?

Thanks, Jon

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"postmaster@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 06 | December | 2008 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.