[Lamer] Can't ping or FTP to Windows 2000 machine on LAN

  • Thread starter Thread starter Toh Sain
  • Start date Start date
T

Toh Sain

There are 3 PC's on my LAN connected with a Netgear RT314
router: Windows 2000 SP4, FreeBSD Unix 4.9, and Windows 98
SE. With each permutation of two machines I can successfully
ping except when the server is the Windows 2000 machine.
Correction: I can successfully ping the Windows 2000 machine
from the FreeBSD machine for 15 seconds or so while the
Windows 2000 machine is booting and displaying the white
logo screen. When the login background appears, pinging
stops.

I am troubleshooting because I am attempting to set up a
LAN-local FTP server on the Windows 2000 machine to serve up
an FTP install of SUSE Linux on the FreeBSD machine. The Unix
FTP client likewise receives a stony silence from Windows
2000.

From the Windows 2000 machine I successfully run all my
Internet apps., including Internet browsers, email, and instant
messaging. I run ZoneAlarm, but shutting it down does not
fix the problem. And ZoneAlarm never signals an alarm or
logs an attempted intrusion when the attempted pinging is
happening.

I don't think I have anything special in my TCP/IP setup to
block pinging or FTP. I have TCP/IP filtering enabled, but I
have "Permit All" checked for everything.

Any comments would be most appreciated.

TS
 
Minor correction: Zone Alarm was in fact blocking and logging,
but not alerting to, the ping requests. Again, however,
shutting down Zone Alarm did not result in a successful ping.

TS

Toh Sain said:
There are 3 PC's on my LAN connected with a Netgear RT314
Click to expand...
messaging. I run ZoneAlarm, but shutting it down does not
fix the problem. And ZoneAlarm never signals an alarm or
logs an attempted intrusion when the attempted pinging is
happening.
Click to expand...
<snip>
 
And removing ZoneAlarm should fix the problem.

Toh said:
Minor correction: Zone Alarm was in fact blocking and logging,
but not alerting to, the ping requests. Again, however,
shutting down Zone Alarm did not result in a successful ping.

TS



<snip>
Click to expand...
 
Bob, thanks for your reply. No, removing ZoneAlarm didn't work. I
prevented it from starting at bootup, then rebooted and confirmed that
ZoneAlarm was not active. Still no pings though.

TS
 
At the risk of totally clogging my own thread, here are
the outputs of ipconfig for each PC:

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : Marowak
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast Ethernet
Controller (3C905C-TX Compatible)
Physical Address. . . . . . . . . : 00-B0-D0-A1-E2-49
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Primary WINS Server . . . . . . . : 129.7.1.200
Secondary WINS Server . . . . . . : 129.7.32.200



Windows 98 IP Configuration

Host Name . . . . . . . . . : BLAZEKIN.optonline.net
DNS Servers . . . . . . . . : 192.168.0.1
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

0 Ethernet adapter :

Description . . . . . . . . : PPP Adapter.
Physical Address. . . . . . : 44-45-53-54-00-00
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :

1 Ethernet adapter :

Description . . . . . . . . : PPP Adapter.
Physical Address. . . . . . : 44-45-53-54-00-01
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :

2 Ethernet adapter :

Description . . . . . . . . : NETGEAR FA310TX Fast Ethernet PCI Adapter
Physical Address. . . . . . : 00-A0-CC-D6-95-8E
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.0.12
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . : 192.168.0.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 03 15 04 9:07:20 AM
Lease Expires . . . . . . . : 03 18 04 9:07:20 AM

FreeBSD Unix
----------------

ifconfig:

fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::2d0:b7ff:feb0:3aef%fxp0 prefixlen 64 scopeid 0x1
inet 192.168.0.11 netmask 0xffffff00 broadcast 192.168.0.255
ether 00:d0:b7:b0:3a:ef
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xff000000
ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
faith0: flags=8002<BROADCAST,MULTICAST> mtu 1500

netstat:

Active Internet connections
Proto Recv-Q Send-Q Local Address Foreign Address (state)
udp4 0 0 192.168.0.11.netbios-d *.*
udp4 0 0 192.168.0.11.netbios-n *.*
Active UNIX domain sockets
Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr
db1d2c80 dgram 0 0 0 db1d2f00 0 db1d2d20
db1d2d20 dgram 0 0 0 db1d2f00 0 db1d2dc0
db1d2dc0 dgram 0 0 0 db1d2f00 0 db1d2e60
db1d2e60 dgram 0 0 0 db1d2f00 0 0
db1d2f00 dgram 0 0 db1ce040 0 db1d2c80 0 /var/run/log
 
Back
Top