Re: Damned MBP to Winblows wireless networking issue

On Wed, 26 Nov 2008 15:07:08 -0500, Graham J wrote
(in article <492dac5f$0$1345$fa0fcedb@xxxxxxxxxxxxxx>):


"Jaimie Vandenbergh" <jaimie@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:rciqi4h0tsjnqv8ot9ske2mfjja1tjtmjl@xxxxxxxxxxxxxxxxxxxxxxxxxx
On Wed, 26 Nov 2008 04:56:29 -0800 (PST), Mentally Sub-Normal
<sarah.j.balfour@xxxxxxxxx> wrote:
On Nov 26, 12:04 pm, Jaimie Vandenbergh <jai...@xxxxxxxxxxxxxxxxxxxxx>
wrote:

If it's a router, there will be - it'll be NATting, which is
sufficient in almost all cases. Leave the XP firewall off while you're
experimenting.

Basic network stuff to try then - can you ping the XP box from the
Mac, and vice versa? What IP addresses are each on? I'm assuming both
get succesful Internet access via the router.

Can the Windows box see itself (and its shared things) in it's own
Network Neighborhood browser?

[various snips in the following quotes]

WOAH!!! Slow down there, my friend...Whilst I know what NAT stands
for, that is no suggestion that I know what it /does/.

Doesn't matter - it'll exist, and you don't need to consider it as
part of this problem.

Internet access is fine, yes.

Yes, the Windows box can see itself - as for IPs, well the MBP's on
192.168.1.101 and the Windows box 192.168.1.100.

Okay. But pings show that Mac->XP is not happening...

What is the IP address of the router? On XP, open a comand window and type:

ipconfig /all

This will report all the details of the network, including the Default
Gateway (i.e. the router).

First check whether the PC can ping its OWN ip address. This will at least
prove that the TCP/IP service is working. It will also prove that you can
type the numbers in correctly! Then check that the PC can ping the router.

If the local IP is 169.254.x.y where x is a number from 0 to 255 inclusive
and y is a number from 1 to 254 inclusive, you have a problem. That's an
APIPA address, an Automatic Private IP Address, and that means that your
machine is set to receive an IP via DHCP... but isn't seeing the DHCP server.
This is usually a Bad Thing(tm).


Now try the same test on the Mac. Others will tell you whether there is an
equivalent to "ipconfig /all" to report the network settings. Whatever, can
the Mac ping itself? Can it ping the router?

ifconfig -a will work. You'll get a long list of devices; the built in
Ethernet will usually be en0. On my machine, en0 shows:

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 <IP V6 address redacted>%en0 prefixlen 64 scopeid 0x4
inet <IP V4 address redacted> netmask 0xffffff00 broadcast <IP V4 address
redacted>
inet6 <IP V6 address redacted> prefixlen 64 autoconf
ether <MAC address redacted>
media: autoselect (100baseTX <full-duplex,flow-control>) status: active
supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP
<full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP
<full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex>
100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control>
1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT
<full-duplex,flow-control> none

You should have something similar.

en1 is usually the AirPort interface. On my machine, en1 shows:

en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 <IP V6 address redacted> %en1 prefixlen 64 scopeid 0x6
inet <IP V4 address redacted> netmask 0xffffff00 broadcast <IP V4 address
redacted>
inet6 <IP V6 address redacted> prefixlen 64 autoconf
ether <MAC address redacted>
media: autoselect status: active
supported media: autoselect

IP V4 is the old, decimal, IP address, based on four groups of three numbers
between 0 and 255, separated by dots. IP V6 is the new, hexadecimal, IP
address, based on six hex numbers 0000 to ffff, separated by colons.


If both of these are OK, then try pinging Mac to PC, and PC to Mac. Ensure
both machines have all firewalls off. XP has a built-in firewall, but the
suppliers often pre-install an AV which includes a firewall. Make sure this
is off also.

Especially if the AV is anything from Symantec.

The task manager will show a list of all the running
processes, so google for each one in turn to find out what they all do.

Some routers will run a ping test, so try router to XP, and router to Mac.
This should show whether either or both have a problem.

These tests are second nature to anybody familiar with networking - akin to
changing gear while driving a car. If you're struggling, it would be much
better to get help from somebody competent.





--
email to oshea dot j dot j at gmail dot com.

.

Relevant Pages

  • Re: Networking problem
    ... machine 2# HP Z8000 laptop xp media center on board lan and 802.11 windows firewall off. ... router linksys befw11s4 ... Network activity lights flash on the router on the port in use. ... I finally got it to the point that from the desktop i can ping the ip ...
    (microsoft.public.windowsxp.general)
  • Re: Cannot get IP address from Router DHCP
    ... > - I can ping both the preferred and alternate DNS servers from the ... > Ethernet adapter Wireless Network Connection: ... > the router by typing its address on a browser but I cannot get to the ... >> What DNS server did you assign? ...
    (microsoft.public.win2000.networking)
  • Re: Setting up Airport Express
    ... It is usually referred to as a "MAC Address", ... on their network. ... always the hardware address assigned to the computer sending the packet. ... When your router receives a packet destined for a computer on your LAN, ...
    (uk.comp.sys.mac)
  • Re: Cannot get IP address from Router DHCP
    ... - I can ping both the preferred and alternate DNS servers from the ... Ethernet adapter Wireless Network Connection: ... router by typing its address on a browser but I cannot get to the ...
    (microsoft.public.win2000.networking)
  • Re: Freebsd 5.1 <-> Win XP Networking problems
    ... Danny MacMillan wrote: ... >> from any ip number forming part of that network and from the netmask. ... > located external to my network it should send the packet to the router ... > (using the router's MAC address) instead of arp-ing for the MAC address ...
    (freebsd-questions)