RE: [WinMac] Cabel modem and Ethernet Blues.
Subject: RE: [WinMac] Cabel modem and Ethernet Blues.
Brian,
I'm not a networking expert, by I'll offer my $0.02 worth based on using DSL at home with a self-configured software router (IPNetRouter) and a more substantial network in the office. I believe if PPPOE was required by your cable company, it would be needed on either platform (Mac or Win), since they would be connecting through the same upstream device.
The following is what I've gathered from your messages. Please correct any that are wrong:
1) The Win machine seems to work Ok when connect directly to the cable modem.
2) The Win machine does not seem to function when connected through the LinkSys or US Robo routers.
3) When the Mac is connected directly to the cable modem, the IP address is changing very often and the system performance goes down.
Since (1) indicates that the cable connection CAN work, try to see what characterizes that configuration. Under Win98, I run the utility "winipcfg", select the adapter, and click on the "More Info" button in order to easily see a wide range of info regarding the IP connection. This display shows IP address, DHCP server address (if any), the date/time that the IP address lease was issued and expires, as well as other information. Write down this information so it might later be compared to what comes up on the Mac side.
I don't have a clue about how to fix (2). I would assume the computer must have an application that allows you to configure the router to match the requirements of your cable company.
To debug (3), I'd start by opening the TCP/IP control panel, choosing "Advanced" user mode, and then clicking "Options". Select "Inactive" and close all the TCP/IP windows. This disables TCP/IP. Is the system still very slow? How about AppleTalk? Is it "Active" and set to use the same ethernet port? Is so, select another port or make it "Inactive" through the AppleTalk control panel or Chooser. Is the system still slow? If not, try to re-activate the TCP/IP side? Does the poor performance return?
On a parallel line of attack, try to get ahold of IPNetMonitor from Sustainable Networks. You can download a demo version which is operational for 30 days or something. Two tools therein are the "DHCP Lease" display and the "DHCP Test". These might produce info comparable to that identified through winipcfg above. I'd look at the DHCP lease times to see if there's an explanation for why the address is changing so frequently.
That's about it for me. I wish you luck. Sorry you're not able to get better support.
One last question just came to mind. Does your cable company use the etherenet hardware address to assign the IP address via DHCP? I think I've heard of such cases. They ask for the MAC (ethernet hardware) address during client registration and only that device will be recognozed. That might explain why neither the Mac nor the router will work.
Brooks Peters
> ----------
*** Windows-MacintoshOS Cooperation List ***
To unsubscribe, send mail to winmac-unsubscribe@iffy.com
This archive was generated by hypermail 2b28 : Thu Dec 13 2001 - 10:32:50 EST |