Dear filterdude-ga,
There are two ways in which this is possible, depending on whether you
use the Mac or the Windows XP PC as the gateway to the Internet. The
method I describe here uses the XP machine as the gateway, that being
the configuration I'm familiar with personally.
"With Internet Connection Sharing, you can connect computers on your
home or small office network to the Internet over a single connection.
For example, if you enable ICS on a computer that connects to the
Internet by using a dial-up connection, other computers on the network
can connect to the Internet through the dial-up connection on the ICS
host. [...] Any IP-attached device can connect, including older
Windows-based clients, non-Windows-based clients, Microsoft Windows
98-based clients, Microsoft Windows 2000-based clients, and Microsoft
Windows XP-based clients with no additional client software required."
- Q310563: Description of Internet Connection Sharing in Windows XP
http://support.microsoft.com/default.aspx?scid=KB;en-us;q310563
To begin with, you'll need the XP machine connected to the Ethernet
switch - that is, you should have a "Local Area Connection" icon
visible in "Network Connections", labeled as "Enabled" - and your
dial-up Internet connection also installed and working on the XP
machine.
Detailed information on setting up Internet Connection Sharing is
available from the Microsoft Knowledge Base:
Q306126: HOW TO: Configure Internet Connection Sharing in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;306126
To summarise, you need to go to the properties of the dial-up
connection in "Network Connections", turn to the "Advanced" page, and
tick the "Allow other network users to connect through this computer's
Internet connection" check box. If you want the connection to dial
automatically when the Mac tries to access the Internet, also tick the
"Establish a dial-up connection whenever a computer on my network
attempts to access the Internet" check box.
When you OK this, you'll receive a warning about how this will affect
the network configuration for your LAN; unless you have other machines
connected as well as the XP machine and the Mac, you can safely ignore
this.
That's everything you need to do on the XP side. To configure the Mac,
you need to do the following:
1. Plug it into the switch, if it isn't already.
2. Go to the "Network" section of "System Preferences".
3. Select the network adapter you're using. You don't specify which
Mac you have; on an iMac, this would normally be "Built-in Ethernet",
but if you're using an add-on adapter, this may vary.
4. On the "TCP/IP" page, select "Using DHCP" in the "Configure" list.
Leave the other values on the page blank.
5. On the "PPPoE" page, make sure "Connect using PPPoE" is unticked.
6. On the "AppleTalk" page, make sure "Make AppleTalk Active" is
unticked.
7. On the "Proxies" page, make sure the check boxes for each type of
proxy are unticked.
This should be all that is necessary. While you shouldn't need to
restart the Mac to make this new network configuration active, I will
mention that I have occasionally found it to be required with mine.
That should be enough to allow Internet access from either machine,
and also to allow the two machines to communicate.
You also mention sharing files between the two machines. I have
located an excellent walk-through on how to set this up in both
directions:
"It's inevitable that many of you out there will, at some point, need
to network your Mac with a Windows machine. Of course, there have been
ways to do this before, either through expensive network servers or
through Thursby Software's Dave. But with the release of Mac OS X
10.2, the capability is built right into the Macintosh operating
system. Here's how you do it."
- Networking Windows with Mac OS X
http://www.digitalmediadesigner.com/2002/09_sep/tutorials/macwinnet020927.htm
If this answer isn't quite what you're looking for, or if you run into
any problems setting up this configuration, please feel free to
request a clarification.
Hope this helps,
cerebrate-ga
Search Strategy:
Internet Connection Sharing Windows XP -
://www.google.com/search?sourceid=navclient&ie=UTF-8&oe=UTF-8&q=Internet+Connection+Sharing+Windows+XP
"Mac OS X" "Windows XP" networking -
://www.google.com/search?sourceid=navclient&ie=UTF-8&oe=UTF-8&q=%22Mac+OS+X%22+%22Windows+XP%22+networking |
Request for Answer Clarification by
filterdude-ga
on
22 Dec 2002 05:25 PST
Hi there!
Thanks heaps for the help so far. Unfortunately I can't seem to get
the Mac to connect to my PC.
Sorry that I originally forgot to mention the model of the Mac - this
is an eMac. We've configured the settings on both the PC and the Mac
as described. Here's what happens when I try to connect on the eMac:
* From the Internet Connect pull-down menu in the Finder, I select
Open Internet Connect
* I click the Connect button
* The status reads "Contacting PPP Server..." for a while, then
appears with "Could not find a PPPoE server".
I've disabled all my security software on the PC, and the built-in XP
firewall is diasabled. The problem occurs if the PC is already
connected to the internet or not.
Hope you can help - please let me know if you need clarification on
anything I'm doing :)
|
Clarification of Answer by
cerebrate-ga
on
22 Dec 2002 06:22 PST
Hello again,
Sorry this didn't work for you straight off, but I'll do my best to
get it sorted out for you as fast as I can.
It should, in theory, work for you without you having to use "Internet
Connect" at all, as that's only used when the Mac is performing
dial-up or connecting to an ISP's server itself. In this
configuration, it should behave as if it was directly connected to the
Internet, so simply starting Internet Explorer or another internet
application on it's own should do all the work required.
(If you haven't tried that, that could well be it, but I'm assuming
it's something more complex.)
Can I ask you to confirm a few points? The first is almost certainly
rather obvious to you, but it never hurts to check; is the dial-up
connection on the Windows PC working correctly from that machine?
Secondly, could you double-check step five on the Mac setup list below
- that the "Connect using PPPoE" box is unchecked?
And lastly for now, could you confirm that the Mac can communicate
with the PC? You can do this by opening "Terminal" on the Mac, and
typing "ping 192.168.0.1" at the command prompt. Please quote the
output to this when replying.
(If it is working, this will produce output for ever; you'll need to
Control-C out of it after a few lines.)
If you could let me know the answers to those, that should let me
begin making progress on getting this debugged for you.
Thanks,
cerebrate-ga
|
Request for Answer Clarification by
filterdude-ga
on
22 Dec 2002 07:00 PST
Hi again,
The dialup is definitely working on the XP machine. I've just tried
accessing Internet Explorer on the eMac, although whenever I attempt
to load a website, I get a 'host not found' error. To make
double-sure, I loaded Mail on the Mac and was unable to check email
due to a 'Unable to receive mail' error.
I've just double-checked all of your steps specified for the Mac -
including step 5 - all is set up as you've detailed.
Here's the output of my Terminal query:
PING: 192.168.0.1 (192.168.0.1): 56 data bytes
ping: sendto: Host is down
ping: wrote 192.168.0.1 64 chars, ret=-1
The following text is then repeated many times:
ping: sendto: Host is down
ping: wrote 192.168.0.1 64 chars, ret=-1
I noted the ethernet switch was flashing for both the PC and Mac
connections when the ping attempt was made.
Hope this helps to narrow down the problem...
|
Clarification of Answer by
cerebrate-ga
on
27 Dec 2002 05:29 PST
First, apologies for taking so long to get back to you.
Yes, that does narrow down the problem considerably. It looks as if
there's a communication problem somewhere between the Mac and the PC,
so now I know where to concentrate the debugging efforts.
First - while this does sound rather obvious - could you double-check
all the cable connections? I've seen some situations before where,
although the connection is solid enough to produce activity lights,
data still doesn't flow, and it never hurts to eliminate the simple
things.
Then, could you shut down and power off both machines, then restart
the PC. After it's completely restarted, and you've logged in to it,
power-on the Mac and log in to that, which should ensure that both
machines are in a known state.
Having done that, could you post which ports on the switch the
computers are connected to, the output to "ipconfig /all" done on the
PC, and the information shown on the "Info" and "Netstat" - the first
two options, "Routing table information" and "Comprehensive Network
Statistics" - pages from the "Network Utility" application on the Mac?
This should clarify further where the problem lies.
(I'm afraid that this problem may take some time to debug for you -
I'd like to assure you that I'm also searching for any reports of
known problems with this configuration that might explain this
problem, and also to offer an alternative: if you would prefer, I can
describe the alternative configuration that uses the Mac to connect to
the Internet and has the PC connecting through the Mac? I'd add,
though, that there's a good chance that configuration might suffer
from the same problem.)
Thanks for your patience,
cerebrate-ga
|
Request for Answer Clarification by
filterdude-ga
on
28 Dec 2002 15:57 PST
Hi again,
I've double-checked the cable connections - everything seems to be
fine there.
Here's the output for "ipconfig /all" on the PC:
Windows IP Configuration
Host Name . . . . . . . . . . . . : Leigh
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter LEIGHCOMPUTER:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE
Desktop Connecti
on
Physical Address. . . . . . . . . : 00-02-55-F3-4F-54
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . . . . :
Here's the output for the Info page of Network Utility on the Mac:
Interface Information:
Hardware Address: 00:03:93:a7:ca:16
IP Address(es): 169.254.212.11
Link Speed: 100Mb
Link Status: Active
Vendor: Apple
Model: gmac+
Transfer statistics:
Sent packets: 93
Send errors: 0
Recv packets: 0
Recv errors: 17
Collisions: 0
Here's the output of the Netstat page:
Display routing table information:
Internet:
Destination Gateway Flags Refs Use Netif Expire
default tnt2.syd.ihug.com. UGSc 6 10 ppp0
localhost localhost UH 13 3347 lo0
169.254 link#4 UCS 0 0 en0
adam-berrys-comput localhost UHS 0 4 lo0
tnt2.syd.ihug.com. p4-tnt2.syd.ihug.c UH 7 0 ppp0
Internet6:
Destination Gateway Flags Netif Expire
UH lo0
fe80::%lo0 Uc lo0
link#1 UHL lo0
fe80::%en0 link#4 UC en0
0:3:93:a7:ca:16 UHL lo0
ff01:: U lo0
ff02::%lo0 UC lo0
ff02::%en0 link#4 UC en0
Display comprehensive network statistics for each protocol:
tcp:
3385 packets sent
3084 data packets (310284 bytes)
0 data packets (0 bytes) retransmitted
0 resends initiated by MTU discovery
218 ack-only packets (109 delayed)
0 URG only packets
0 window probe packets
0 window update packets
83 control packets
3390 packets received
3187 acks (for 310343 bytes)
27 duplicate acks
0 acks for unsent data
3135 packets (312226 bytes) received in-sequence
0 completely duplicate packets (0 bytes)
0 old duplicate packets
0 packets with some dup. data (0 bytes duped)
2 out-of-order packets (1662 bytes)
0 packets (0 bytes) of data after window
0 window probes
0 window update packets
3 packets received after close
0 discarded for bad checksums
0 discarded for bad header offset fields
0 discarded because packet too short
30 connection requests
27 connection accepts
0 bad connection attempts
0 listen queue overflows
57 connections established (including accepts)
61 connections closed (including 0 drops)
10 connections updated cached RTT on close
10 connections updated cached RTT variance on close
0 connections updated cached ssthresh on close
0 embryonic connections dropped
3187 segments updated rtt (of 3190 attempts)
0 retransmit timeouts
0 connections dropped by rexmit timeout
0 persist timeouts
0 connections dropped by persist timeout
0 keepalive timeouts
0 keepalive probes sent
0 connections dropped by keepalive
97 correct ACK header predictions
134 correct data packet header predictions
udp:
114 datagrams received
0 with incomplete header
0 with bad data length field
0 with bad checksum
1 dropped due to no socket
0 broadcast/multicast datagrams dropped due to no socket
0 dropped due to full socket buffers
0 not for hashed pcb
113 delivered
164 datagrams output
ip:
3505 total packets received
0 bad header checksums
0 with size smaller than minimum
0 with data size < data length
0 with ip length > max ip packet size
0 with header length < data size
0 with data length < header length
0 with bad options
0 with incorrect version number
0 fragments received
0 fragments dropped (dup or out of space)
0 fragments dropped after timeout
0 packets reassembled ok
3504 packets for this host
1 packet for unknown/unsupported protocol
0 packets forwarded (0 packets fast forwarded)
0 packets not forwardable
0 packets received for unknown multicast group
0 redirects sent
3573 packets sent from this host
0 packets sent with fabricated ip header
0 output packets dropped due to no bufs, etc.
32 output packets discarded due to no route
0 output datagrams fragmented
0 fragments created
0 datagrams that can't be fragmented
0 tunneling packets that can't find gif
0 datagrams with bad address in header
icmp:
1 call to icmp_error
0 errors not generated 'cuz old message was icmp
Output histogram:
destination unreachable: 1
0 messages with bad code fields
0 messages < minimum length
0 bad checksums
0 messages with bad length
0 multicast echo requests ignored
0 multicast timestamp requests ignored
Input histogram:
destination unreachable: 1
0 message responses generated
ICMP address mask responses are disabled
igmp:
0 messages received
0 messages received with too few bytes
0 messages received with bad checksum
0 membership queries received
0 membership queries received with invalid field(s)
0 membership reports received
0 membership reports received with invalid field(s)
0 membership reports received for groups to which we belong
14 membership reports sent
ipsec:
0 inbound packets processed successfully
0 inbound packets violated process security policy
0 inbound packets with no SA available
0 invalid inbound packets
0 inbound packets failed due to insufficient memory
0 inbound packets failed getting SPI
0 inbound packets failed on AH replay check
0 inbound packets failed on ESP replay check
0 inbound packets considered authentic
0 inbound packets failed on authentication
0 outbound packets processed successfully
0 outbound packets violated process security policy
0 outbound packets with no SA available
0 invalid outbound packets
0 outbound packets failed due to insufficient memory
0 outbound packets with no route
ip6:
0 total packets received
0 with size smaller than minimum
0 with data size < data length
0 with bad options
0 with incorrect version number
0 fragments received
0 fragments dropped (dup or out of space)
0 fragments dropped after timeout
0 fragments that exceeded limit
0 packets reassembled ok
0 packets for this host
0 packets forwarded
0 packets not forwardable
0 redirects sent
6 packets sent from this host
0 packets sent with fabricated ip header
0 output packets dropped due to no bufs, etc.
0 output packets discarded due to no route
0 output datagrams fragmented
0 fragments created
0 datagrams that can't be fragmented
0 packets that violated scope rules
0 multicast packets which we don't join
Mbuf statistics:
0 one mbuf
0 one ext mbuf
0 two or more ext mbuf
0 packets whose headers are not continuous
0 tunneling packets that can't find gif
0 packets discarded due to too may headers
0 failures of source address selection
0 forward cache hit
0 forward cache miss
icmp6:
0 calls to icmp_error
0 errors not generated because old message was icmp error or so
0 errors not generated because rate limitation
Output histogram:
multicast listener report: 5
neighbor solicitation: 1
0 messages with bad code fields
0 messages < minimum length
0 bad checksums
0 messages with bad length
Histogram of error messages to be generated:
0 no route
0 administratively prohibited
0 beyond scope
0 address unreachable
0 port unreachable
0 packet too big
0 time exceed transit
0 time exceed reassembly
0 erroneous header field
0 unrecognized next header
0 unrecognized option
0 redirect
0 unknown
0 message responses generated
0 messages with too many ND options
0 messages with bad ND options
0 bad neighbor solicitation messages
0 bad neighbor advertisement messages
0 bad router solicitation messages
0 bad router advertisement messages
0 bad redirect messages
0 path MTU changes
ipsec6:
0 inbound packets processed successfully
0 inbound packets violated process security policy
0 inbound packets with no SA available
0 invalid inbound packets
0 inbound packets failed due to insufficient memory
0 inbound packets failed getting SPI
0 inbound packets failed on AH replay check
0 inbound packets failed on ESP replay check
0 inbound packets considered authentic
0 inbound packets failed on authentication
0 outbound packets processed successfully
0 outbound packets violated process security policy
0 outbound packets with no SA available
0 invalid outbound packets
0 outbound packets failed due to insufficient memory
0 outbound packets with no route
pfkey:
0 requests sent to userland
0 bytes sent to userland
0 messages with invalid length field
0 messages with invalid version field
0 messages with invalid message type field
0 messages too short
0 messages with memory allocation failure
0 messages with duplicate extension
0 messages with invalid extension type
0 messages with invalid sa type
0 messages with invalid address extension
0 requests sent from userland
0 bytes sent from userland
0 messages toward single socket
0 messages toward all sockets
0 messages toward registered sockets
0 messages with memory allocation failure
I'm more than happy to try out the alternative configuration - I'm not
too concerned about which computer's the gateway to the net, as long
as it works :)
Do you think the problem could lie with the cables? Unfortunately I
don't have a spare set of cables to try, but do you think this could
be the cause?
|
Clarification of Answer by
cerebrate-ga
on
28 Dec 2002 16:08 PST
Thank you for your clarification. Now we've got something definitive,
I think - the information "ipconfig /all" is reporting for your PC is
definitely not what I'd expect to see if Internet Connection Sharing
was working happily on there. (The Mac's info is all OK - it's just
what I'd expect given that the PC isn't behaving.)
As it happens, I've been able to arrange access to a suitable PC I can
use with my iMac to try to replicate the problems you've been having,
which I'll be able to do tomorrow. Hopefully, that will get me a
definitive answer, and I'll also dig through the Microsoft knowledge
base, etc. on ICS to see if they've seen the particular symptoms
you've outlined before.
So, hopefully tomorrow we should have results! I'll post another
clarification as soon as I've run my tests.
Thanks,
cerebrate-ga
(Regarding cables: I had thought they might be a possibility,
actually, but the latest information seems not to point at them.
That's not definitive, as I've seen the strangest problems imaginable
come from cable issues, but it's enough to call it very unlikely.)
|
,
0 Comments
)