Re: Linksys BEFSX41 problems

From: MyndPhlyp (nobody_at_home.now)
Date: 01/08/04 

Date: Thu, 08 Jan 2004 14:59:09 GMT

"Rich McMahon" <rhmc@austin.rr.com> wrote in message
news:iaqqvvk458tei4it6009d6i9t2nesd7tga@4ax.com...
> To all that have replied so far
>
> Ill check that the router will allow all outgoing.
>
> Right now as stated below they cant even ping each other. Ips are
> handed out by dhcp. no hard coded settings. netmask and gateway are
> the same on both boxes and ips are on the same subnet.
>
> Yes they are in the same workgroup however the problem isnt a
> workgroup config error. The boxes cant ping each other by IP.

I doubt the Linksys is the cause of the problems. Traffic on the LAN side
flows freely from port to port (within the bounds of its switch behavour,
for those who were getting ready to flame on).

When you attempt to PING, are you doing so by IP address or by name?

If you can't PING by IP address from workstation to workstation on the LAN
side, start off by checking the simple stuff using IPCONFIG /ALL. Carefully
examine the IP address and the Netmask to ensure each workstation has a
unique IP address, has the same Netmask, and that the IP address (with
respect to the Netmask) is in the same network.

Once you are able to PING, the next thing to look at are the services
installed for your network. Start => Settings => Control Panel => Network
and Dial-up Connections. There should be an entry there for Local Area
Connection. Wrong-click it and select Properties from the pop-up menu. In
the center of the dialog box is a list of protocols and services installed.
You should have, as a minimum, Client for Microsoft Networks, File and
Printer Sharing for Microsoft Networks, and the ever popular Internet
Protocol (TCP/IP).

Chances are you lack the File and Printer Sharing for Microsoft Networks
service.

Relevant Pages

  • multi-homed systems stop answering ARP on local addresses w/ifconfig aliases
    ... But while it still responds from the Internet, even the host itself can't initiate a ping to that IP. ... inet 10.11.185.146 netmask 0xfffffff8 broadcast 10.11.185.151 ...
    (freebsd-net)
  • RE: Strange routing configuration problem
    ... >Given your netmask, both IP addresses of R are in the same subnet ... >The card in R which is on the same subnet as A should have an IP ... so I could ping R on both the interfaces but still cant ping A. ...
    (freebsd-net)
  • RE: Upgrading to 6.2-RELEASE from 6.2-STABLE
    ... inet 71.4.48.6 netmask 0xfffffe00 broadcast 71.4.49.255 ... What's interesting is I can ping 71.4.48.6 from the console. ... ping: sendto: Invalid argument ...
    (freebsd-questions)
  • Re: Linksys BEFSX41 problems
    ... Rich McMahon wrote in ... > workgroup config error. ... The boxes cant ping each other by IP. ...
    (comp.security.firewalls)
  • Starting/stopping a network interface
    ... I've searched high and low, but can't find an answer to this problem. ... I cannot ping ... # Enable network daemons for user convenience. ... ifconfig_rl1="inet 192.168.99.2 netmask 255.255.255.0" ...
    (freebsd-newbies)
Quantcast