Hi Will,
K, sorry that wasn't any help. I'll explain my setup here, and maybe
running though a few of the versions/settings will help!
I'm writing this on a G3 PowerBook, running OS9.1. I have TCP/IP set to use
Airport (although it would work with Ethernet too). I also have Appletalk
set to Airport (again, this would work with Ethernet). My TCP/IP settings
are set to use a DHCP server. The DHCP Client Id is set to NickT, to
identify my laptop, and the name server address is 192.168.0.1, the Windows
NT server.
That's it as far as the laptop goes.
On the Windows NT box, I'm running NT4 with SP 6a. I have WinGate running
on that to provide Internet Connection Sharing. In my browser, I simply set
the HTTP Proxy to be 192.168.0.1 Port 8080, and I can browse. Nothing
fancy.
I also have DoubleTalk from Connectix running on the laptop that lets me use
Windows Shares on the server. I find this works really well.
For what it's worth... I'm currently looking at replacing the Windows NT
server with an old P166 running e-smith (a Linux distro purely for being an
Internet Server and also a Gateway to provide Internet Connection Sharing.
So far, I'm really impressed. Security it great. I don't need to set Proxy
Servers up in all my Internet Applications. And I'm a) recycling an old
machine, b) freeing up a higher spec'd machine and c) removing the need for
licensed versions of software that need to be updated!! I've had problems
with Modem's not working properly, Proxy servers and endless other troubles
on the NT box... E-smith installed in a few minutes, detected all my
hardware, and bingo, was connected almost immediately. Beautiful!!!
I guess Win2K could be affecting the Mac... I haven't had the chance of
playing with it much yet, so I don't know how that may be affecting it. Can
you see what IP addresses are being allocated from your Win2k server? And
can you also check what the IP address is that has been allocated to the
other Win2k machine. You should not specify 192.168.0.1 as the DHCP Client
Id as this could cause conflictions with the DHCP Server. You said you
couldn't connect... What are you connecting to? Try setting TCP/IP to use
Ethernet, Specify a DHCP Client Id of 'test' and set the DNS Ip address to
192.168.0.1. Does that get you anywhere? One thing I have noticed is that
while most things can be done in the TCP/IP control panel without requiring
a restart, sometimes the Mac gets a little confused... And a restart does
actually help. If the Win2k Server is allocating numbers in the 192.168.0.n
range, and the ethernet connection is ok, then you should see the allocated
number appear in the TCP/IP control panel without any hitches. It sounds
like the DHCP is working to some degree as you got that other 169.n.n.n
address, so I would check the range that is being assigned on the server,
and also redo the TCP/IP settings on the Mac, including a restart.
All the best
Nick
on 30/8/01 11:34 PM, Will Swain at [EMAIL PROTECTED] wrote:
> Hmmm,
>
> tried that, and no go I'm afraid. It's still doing the same thing as
> before....unable to connect etc.
>
> I wonder if there is something in w2kserver, like mayybe the active
> directory stuff, that is causing problems for the Mac?
>
> Cheers
>
> Will
>
> -----Original Message-----
> From: Nick Texidor [mailto:[EMAIL PROTECTED]]
> Sent: 30 August 2001 11:58
> To: Will Swain
> Subject: Re: ics and macs...thanks
>
>
> Hi Will,
>
> The first thing I'd try on the Mac is setting the TCP/IP to try manually.
> Give it an IP address of 192.168.0.200 or something similar, and then in IE
> or Netscape, try and connect to 192.168.0.1 (providing you have a web server
> running on that machine)
>
> I think that with the TCP/IP control panel, when you use DHCP, you just set
> the Client Id to whatever you want to call that machine, and the Name Server
> Address to be 192.168.0.1. I'm pretty sure that's all it is. I can't check
> at the minute as I'm setting up a new gateway/server using Linux rather than
> NT... So far it's working excellently!!
>
> See how you go, and feel free to email if you have more questions etc!
>
> Nick
>
>
> on 30/8/01 8:36 PM, Will Swain at [EMAIL PROTECTED] wrote:
>
>> Hi Nick,
>>
>> Thanks for your offer of help.
>>
>> Well, I have set ICS on the w2k server, and it seems to work, giving
> itself
>> an IP of 192.168.0.1. The other w2k machine is set up to get its IP from
>> DHCP, and it does, no problem!!
>>
>> The problem is the Mac. We opened TCP/IP settings on it, set it to use the
>> correct ethernet port, and to it to obtain its details through DHCP. We
> had
>> to specify an identification for the DHCP server, so we gave it the IP
>> address 192.168.0.1 to look for.
>>
>> The Mac seems to have been assigned an IP address starting 169.x.x.x which
>> seems wrong, as I would assume it should be 192.x.x.x. When I try to ping
>> the IP the Mac has been assigned the ping just times out.
>>
>> The Mac itself slows right down, to the point where it becomes impossible
> to
>> use, and it can't connect to the internet.
>>
>> Sadly, I'm no Mac expert.....so I have to say I'm a little stumped......
>>
>> Will
>>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
