Win 2k not able to connect to a 95 peer

I wonder if I can hear your feedback on a win 2k station system which is set up to connect to a win 95 as a peer. It has mysteriously! disengaged itself from the action.

Fact is, the win 2k station has a working NIC, with a proper station ID, and workgroup name assigned. Its network setup uses 3 usual components (microsoft client/file and print share and TCP/IP in this case). The 95 PC uses tcp/ip as well. The 2k PC used to be able to map to a network drive off 95 PC, but no more. It basically hangs at the drive map pop up window and announces that it can't find the network drive.

Most articles i run into have the 9x peer trying to attach to a win 2k peer but haven't found one matching my specific set up.

I also have changed the physical set up entirely,gone from coax to hub and RJ45 and have a 3rd PC running 95 which connects fine to other 95 peer. So other units do connect to my peer except the 2k.
I have tried two different NICs and they both use (get configured PnP )irq 9 (could cascade be an issue ?) One is a good 3com NIC and i can't find a way to change/use any other irq. As far as s/w , there are no TSRs , not even a virus scanner (bad idea o/c).
thnx

1. ?'s
jkennedy55 Feb-04-02 08:31 PM
In response to message 0

Can the wkst's ping each other? What are your TCP/IP properties? What protocols do you have installed? What lights are showing on the nic's and hub?

2. RE: ?'s
mac Feb-05-02 05:02 AM
In response to message 1

I normally use dynamic IP addresses. I should learn to do that. what would be a typical class A address for this case? 10.x.x.x ? What are the considerations in doing that ? I understand you set the IP and ping .
I use plain vanilla tcp/ip setup only, has no properites i can think of. Is there anything to look for setting up tcp/ip ?
The NIC on 2K PC has one solid light and one blinking occasionally, only up to point of error message.
The hub has one link light on per connection , and occasional blink on the other. I believe that the lights indicate basic connection , but no activity. (not sure what the exact terminology for the two different lights are)
thanks in advance for any additional comments.

3. RE: ?'s
lbyard Feb-05-02 03:46 PM
In response to message 2

>what would be a typical class A address for this case?
http://duxcw.com/faq/network/privip.htm. I normally use 192.168.0.xxx
If you setup Internet sharing on the 2K computer it will assign a static IP of 192.168.0.1 to the NIC going to the local network and has a DHCP server that will assign 192.168.0.x IPs to the clients. But I do not see where you have ICS installed (or any need for it). I would check the IPs on all of the computers with Start, Run, winipcfg on the 9X computers and ipconfig /all from the DOS prompt on the 2K computer. You may have to use static IPs and hosts tables. See C:\windows\hosts.sam and c:\winnt\system32\drivers\etc. Use notepad. Larry

4. Gold Fingers AKA Larry
mac Feb-08-02 08:48 AM
In response to message 3

Thanks for forcing me to use IP addresses in a peer2peer net. It's the only net i work on once in a while.
I removed all netbuei references too, to make things smooth..
I believe another problem was my naming of win2k station as "win2k" . I think it doesn't like a numeric char in the name and possibly minimum 6 characters ? (i may be confusing that with recent hotmail.com password to be 6 char min !) It is in the documentation off help button.
Thnx for making the time to respond..

5. RE: Gold Fingers AKA Larry
lbyard Feb-08-02 06:15 PM
In response to message 4

http://duxcw.com/faq/network/names.htm. Larry

7. Also, Any known issues about AOL 6 and peer to peer net ?
mac Feb-08-02 09:16 PM
In response to message 5

LAST EDITED ON Feb-08-02 AT 09:19 PM (GMT)
excuse the double post, user error...I couldn't erase the previous post
It seemed activation of aol6 could screw things up on my 2k pc ....
this is off help in win 2k on naming issues, I can almost swear it didn't like a numberic in the units name , such as "win2k".... but this text says otherwise...
"It is recommended that you use computer names that are 15 characters or less. If your computer has TCP/IP networking protocol installed, the computer name can be up to 63 characters long but should only contain the numbers 0-9, the letters A-Z and a-z, and hyphens. You may use other characters, but doing so may prevent other users from finding your computer on the network. If your network is using the Microsoft DNS server, you can use any characters except periods. If other networking protocols are installed without TCP/IP, the name is limited to 15 characters.
If you specify a computer name longer than 15 characters and you want longer names to be recognized by the Active Directory domain, the domain administrator must enable registration of DNS names that are 16 bytes or longer.
If your computer is a member of a workgroup, no networking is installed, or TCP/IP is not installed, the computer name cannot be more than 15 characters, and the characters must all be uppercase. "

8. Computer and Workgroup Names
lbyard Feb-09-02 05:31 PM
In response to message 7

Your post is most certainly going to cause network problems for the average reader of this forum. I would suggest that readers visit http://duxcw.com/faq/network/names.htm and pick computer and workgroup names based on that advice and many years of networking experience. I am of course open to comments and counter arguments. I am also right about this issue. Larry