Windows 2000 won't talk to Linux

[prince_kenshi]

I have a 3 computer network at my house. This computer is Debian. Another computer is Windows 98. The other is Windows 2000. Now this is kind of funny. The Linux box is a gateway to the internet and also runs other services. Linux and Windows 98 have no problem communicating with each other. Linux can use the NetBIOS services on Windows 2000. But Windows 2000 can't seem to communicate at all with Linux other than pinging. Whenever I try to use ftp or other, it says it failed to open a connection. So I logged everything coming from or going to that machine and here's what it shows:

Apr 18 21:57:06 kenshi kernel: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:50:bf:38:8d:cc:08:00 SRC=192.168.0.2 DST=192.168.0.255 LEN=229 TOS=0x00 PREC=0x00 TTL=128 ID=254 PROTO=UDP SPT=138 DPT=138 LEN=209
Apr 18 21:57:11 kenshi kernel: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:50:bf:38:8d:cc:08:00 SRC=192.168.0.2 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=255 PROTO=UDP SPT=137 DPT=137 LEN=58
Apr 18 21:57:11 kenshi kernel: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:50:bf:38:8d:cc:08:00 SRC=192.168.0.2 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=256 PROTO=UDP SPT=137 DPT=137 LEN=58
Apr 18 21:57:12 kenshi kernel: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:50:bf:38:8d:cc:08:00 SRC=192.168.0.2 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=257 PROTO=UDP SPT=137 DPT=137 LEN=58
Apr 18 21:58:46 kenshi kernel: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:50:bf:38:8d:cc:08:00 SRC=192.168.0.2 DST=192.168.0.255 LEN=237 TOS=0x00 PREC=0x00 TTL=128 ID=258 PROTO=UDP SPT=138 DPT=138 LEN=217

This was after attempting to telnet from the Win 2K machine. I noticed that it's communicating on port 137 and 138 instead of 23. Aren't these ports for NetBIOS? What's up with that? Does anyone have a clue? It won't ping with DNS either by the way.

[Lorithar]

Kenshi:

??? Thats a broadcast address destination.....DST=192.168.0.255

Which machine is on 192.168.0.2 --

MAC=ff:ff:ff:ff:ff:ff:00:50:bf:38:8d:cc:08:00 --- this does not seem correct to me ... but might well be..


I have to wonder if 192.168.0.2 knows where his neighbours are ... This looks to be a discovery packet for SMB/netbios ...

Without re-reading my notes farther, I'd bet that you've run into the SMB samba/W2K differences ... There was an issue for a bit where Samba wasn't talking properly to W2K boxen as MS had altered the packet coding (again) ... however this is fixed in newer samba implementations...


I don't like that mac address ... but I could be wrong ... all the cards on my network are Dlinks and the mac addys are a consistent through the first 8 bytes...

Questions:

from ifconfig what is ip/mac of linux connection to internal network

from network/services/protocols what is ip addy of W2K box...
(what make/model of network card out of curiosity, it would make me less suspicious of that mac if I could index it...)

can W2K see the 98 box???

[XxMaCaBrExX]

Maybe it knows??? :eek: :D

[twofoolish2b]

I have Windows 2000 at home on one box and Slackware 7.1 on the other and I have no problems with telnet from Windows to Linux. What distro are you using?

[prince_kenshi]

Here is some more information. The Debian box's address is 192.168.0.1. The Win 2K machine is 192.168.0.2. Win 98 is on 192.168.0.10 although it's not in the log. The Debian and Win 98 machines both have a Dlink Card while Win 2K (which the listed MAC address should belong to) has a 3C509. I know that's a broadcast address but what is that port used for? NetBIOS? It just repeatedly sends out broadcast packets on 137 and 138. I don't even seem to get any packets at all on 23 just after trying to telnet. I have it set to log all incoming, forwarded, and output packets to or from the Win 2K machine. The Win 2K machine can see itself and the Win 98 in network neighborhood even though Win 98 can't see anything, including itself. Debian can mount shared folders on either machine. I think you just may be right XxMaCaBrExX.

[prince_kenshi]

[bump]

[Lorithar]

*grins*

Kenshi ... linux and W2K are arguing about browse master ... I suspect there is something that can be done to keep this down.. Yes those are SMB ports. IIRC W2K will try to be browse master for a domain until either 1) it finds an official PDC or 2) it gets told to stop ....

(half awake right now) I think you can turn this off in W2k, I know you can set the Samba box to Master with a priority thing, since I've done it myself ...

I'd be checking netmask on the W2k and making sure the TCP/IP config on W2K matched the rest of the network.

Try running netstat -rn on the W2K box and making sure that the routing is correct...
? I wonder .... you can use tcp/ip netbios connections but cant use tcpip ..
Do you have tcp ip turned off? ~~ NT can do this, as can W98 .... you can install only netbios/netbeui and share disks and whatnot, but no tcpip.... the netstat -rn will show this.
(just poured coffee ...if more occurrs to me I'll post from work)

[XxMaCaBrExX]

No, I'm tellin' you. It Knows! :D It's just jealous, that's all. :p

The statement below is non of your D4MN business and I'll thank you to stay out of my personal affairs! :P

[ 20 April 2001: Message edited by: XxMaCaBrExX ]

[prince_kenshi]

Here are the results of the netstat. Again Win 2K is 192.168.0.2 and Linux 192.168.0.1.

================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 50 bf 38 8d cc ...... NDIS 5.0 driver
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 1
192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 1
224.0.0.0 224.0.0.0 192.168.0.2 192.168.0.2 1
255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2 1
Default Gateway: 192.168.0.1
================================================== =========================
Persistent Routes:
None

Route Table