This may be old hat to some, but I am at wit's end. In brief, I can't get two peer-to-peer networked Win98 computers to see each other all the time.
Details:

Computer #1 is Win98
Computer #2 is Win98SE
Each computer has its own dynamically assigned IP address from AT&T, no IP sharing.
LAN setup is this: AT&T cable -> Surfboard Cable Modem -> LinkSys 10/100 Switched Hub -> 2-computer LAN.

Everything was working fine with both internet connection and local file sharing handled by TCP/IP. Then the AT&T server switched the WinSE computer's IP address to a different gateway and subnet. As a result, both machines still had good Internet access, but lost local TCP/IP connectivity.

To restore file sharing I installed NetBEUI on each machine and made it the default protocol. Now the Win98 box can see and access the 98SE box in Network Neighborhood (sometimes) but the 98SE box only sees itself (sometimes), so file access on the LAN is one-way only. I was able to send messages both ways using WINPOPUP.EXE, so the machines are connected in spite of what Network Neighborhood says.

AT&T is no help and this is making me crazy. If you're wondering why I used two IP's instead of a router, the LAN is primarily for gaming and I didn't want address conflicts when both computers are tied into the same game server on the internet.

Network configuration for both computers is as follows:

Primary Network Logon: Windows Logon

File and Printer Sharing: file access enabled

Installed components
------------------------------
Clent for Microsoft Networks
Etherlink 10/100 NIC
Dial-Up Adaptor
NetBEUI -> Etherlink 10/100 NIC
TCP/IP -> Dial-up Adaptor
TCP/IP -> Etherlink 10/100 NIC
File and printer sharing for Microsoft Networks


Client for Microsoft Networks Properties
-----------------------------------------
Network logon options: Quick logon


NetBEUI->Etherlink NIC Properties
---------------------------------
Bindings:
'Client for MicroSoft Networks'
'File and printer sharing for Microsoft Networks'

NetBEUI is set as the default protocol


TCP/IP->Etherlink NIC Properties
--------------------------------
Bindings: none
IP Address: obtain IP address automatically
DNS: disabled
WINS Resolution: disabled


File and printer sharing Properties
-------------------------------------
Browse Master: automatic
LM Announce: no



Last edited by redkitty at Aug 15 2002, 03:28 AM

Just a thought- did you try enbaling netbui in the tcip properties? i see you have netbui installed as a seperate service but from wht i have read thats not neccessary.
Read more here hxxp://HomeNetHelp.com

DoG --
You are thinking of NetBIOS. Don't know much about it, but if it operates over TCP/IP I wouldn't think it could help. As you can see from the addresses below, the two machines in question now think they are on different networks.

computer___ip address________subnet mask
#1________12.235.176.x______255.255.255.0
#2________12.228.168.x______255.255.254.0


Thanks for the link.



Last edited by redkitty at Aug 15 2002, 03:38 AM

Hmmm....redkitty, have you checked the binding order of the protocols for each adapter? You might want to have netbeui (I believe it's non-routable) at the top of the stack....How are you getting the winpopup to work? By machine name or i.p.?

/JD

JackDynne --
To tell the truth, when I tested Winpopup I was broadcasting to the workgroup instead of using the computer name. I wasn't aware that you could specify an ip address in winpopup rather than a name.

I am pretty ignorant about networking. I don't know of a way to determine or specify a binding order for the protocols. In the Network settings window, the components are listed in the same order as in my first post above.



Last edited by redkitty at Aug 15 2002, 11:17 AM

Hmmm....redkitty check these links:

h**p://www.duxcw.com/digest/Howto/network/net2pc/intro.htm

and check these too:

h**p://www.wown.info/j_helmig/netcheck.htm

h**p://www.wown.info/j_helmig/w98defpr.htm

Hope that helps some... :blink:

If all that fails, you may be able to disable netbui and work around with hosts and lmhost files; check here for some more info on that:

h**p://www.tek-tips.com/gfaqs.cfm/spid/615/sfid/808

Also, I have been able to resolve problems occasionally by uninstalling then reinstalling problem protocols. That might be an option too... :( :huh:

Let us know how it works out... :)


/JD

Thanks for the links. If I figure out what's wrong, I'll post it here.

Solved!!

The Win98 computer had not been updated to ServicePack1. That seems to have fixed it. I also set BrowseMaster to "enabled" on the Win98SE machine to speed up network recognition, but it wasn't strictly necessary.

Contrary to what I read in several places, it was NOT necessary to use Client for Microsoft Networks as the default login. Windows Logon works just fine, with no logon passwords.

Thanks again for the links.