Mac OSX users - what have you got in your TCP/IP box? ?
Mac OSX users - what have you got in your TCP/IP box? ?
Author
Discussion

MikeyT

Original Poster:

18,432 posts

301 months

Tuesday 29th November 2005
quotequote all
Help - I have been trying to get my new G5 configured for the best part of a week - and have hit deadend after deadend - never had this trouble with a Mac before.

Apple menu > System Preferences > Network ...

Location: Automatic

Show: Built-in Ethernet

Configure: Using DHCP ...

Right, now underneath where the IP Address, subnet mask and Router words are - what is opposite these words? Anything - numbers, boxes in which to write number s or just 'nothing' ?? (ie, the background of the window)

Please help.

_DeeJay_

5,057 posts

284 months

Tuesday 29th November 2005
quotequote all
What are you trying to do? I figure the boxes are going to be blank (probably greyed out) because you've set the card to use DHCP which will set those values automatically when the machine gets a lease from the DHCP server.

MikeyT

Original Poster:

18,432 posts

301 months

Wednesday 30th November 2005
quotequote all
_DeeJay_ said:
What are you trying to do? I figure the boxes are going to be blank (probably greyed out) because you've set the card to use DHCP which will set those values automatically when the machine gets a lease from the DHCP server.


I'm trying to get my new imac set up for the internet (wirelessly if poss) and can't do it!

I go to the boxes mentioned and the NTL helpline guy told me there should be numbers in there ... or will be when the modem speaks to the mac, but there are no boxes, no numbers, etc, nothing, just the background of the window ...

What has yours got if you're on OSX?

jamieboy

5,929 posts

259 months

Wednesday 30th November 2005
quotequote all
MikeyT said:
What has yours got if you're on OSX?

It's got the IP address, subnet mask, and gateway in the format aaa.bbb.ccc.ddd. They're not in boxes or anything, just text against background.

As you say, I reckon they'll stay blank until your Mac can contact a DHCP server, whether that's another machine, or your router, or whatever.

rednotdead

1,256 posts

256 months

Wednesday 30th November 2005
quotequote all
You might find your mac has assigned itself an ip - probably in the 16x.x.x.x range.

If your wireless router has a 192.168.1.x address try putting in a similar address on your mac with the router address as your gateway.

_DeeJay_

5,057 posts

284 months

Wednesday 30th November 2005
quotequote all
OK, so I assume the Mac will populate that information once it has a DHCP address.

Sorry if this sounds patronising, but have you checked the basics?
If you're using an Ethernet card, does the card have a link light (I read elsewhere that you'd used a crossover cable to connect to the router)?
If you're using a wireless LAN, can you see any wireless networks from that machine?

What I'm basically trying to ascertain is whether your machine is in a position to communicate with the router. When it is, you can then worry about how you get an IP address.

D

MikeyT

Original Poster:

18,432 posts

301 months

Wednesday 30th November 2005
quotequote all
_DeeJay_ said:
OK, so I assume the Mac will populate that information once it has a DHCP address.

Sorry if this sounds patronising, but have you checked the basics?
If you're using an Ethernet card, does the card have a link light (I read elsewhere that you'd used a crossover cable to connect to the router)?
If you're using a wireless LAN, can you see any wireless networks from that machine?

What I'm basically trying to ascertain is whether your machine is in a position to communicate with the router. When it is, you can then worry about how you get an IP address.

D


I presume the modem isn't telling the Mac a DHCP address - why though I have no idea ...

I was told by the guy at NTL to use a CROSSOVER cable to connect the modem to the Airport Express Router. But it doesn't work with either this or a normal Ethernet cable ...

I can see the wireless network on the Mac that I have set up so I think the Airport card is working OK - but I presume the link between the router and the modem is duff somehow ...

??

Anyway, it's gone down to the local Apple shop to cost me an arm and a leg - but I bought it from a place 100 miles away so no option really.

MikeyT

Original Poster:

18,432 posts

301 months

Wednesday 30th November 2005
quotequote all
Clean bill of health at the apple shop - so an ntl problem or modem problem surely ... ??

jmorgan

36,010 posts

314 months

Wednesday 30th November 2005
quotequote all
Not really knowing my way around it and having a problem, I stumbled on setting up a new location and naming it and setting up for built in ethernet and saving it. Until I did that I had no options for built in ethernet.

HiRich

3,337 posts

292 months

Wednesday 30th November 2005
quotequote all
Let's go back to basics

I understand that you have:
- A DSL modem connected to NTL
- An Airport Express 'pod'
- An OSX machine, with an airport card installed
- A Classic machine without Airport
Correct?

From what you have said so far, I understand
- The modem is supplying an external (internet) signal through its Ethernet jack (because it works when you connect it to the Classic machine)
- The Classic machine can receive this signal properly, and it's Ethernet is working (because it works if you connect it to the modem)
- The Classic machine is correctly set up for when the modem Ethernet cable is plugged directly into the back. However, it may not be correctly set up for a network
- The OSX machine has an Ethernet card that is working (because the shop tested it)
- The OSX machine has an Airport card that is working (because the shop tested it)
- We do not know whether the Airport pod is working
- We do not know whether the OSX machine is correctly set up for your network, either by Ethernet or Airport
Correct?

Now as I see it, there are two routes you can go down:
1- Get the airport system running (pod + OSX machine). Then get the modem talking to the Airport
2- Get the OSX machine talking to the modem via Ethernet. Then try to introduce the Airport
If you can jury rig the Classic machine to work with the modem via Ethernet 9and therefore access the internet for the time being). i recommend you go Route 1. But which way do you want to approach it?

Answer those questions, get all the manuals and paperwork out, and we can start working through the problems.

thepassenger

6,962 posts

265 months

Thursday 1st December 2005
quotequote all
Damn, if I'd spotted this earlier I'd have flashed up the mac.

I'm not 100% sure how different NTL is when you go via a cable modem as the inlaws use one of the set top boxes but... the STB will only talk to one registered MAC address (basically the internal address of your network card) so you might find that you can't go Modem -> WiFi -> 2x computers (I need to look in to an Airport to see if it will do the full on router/NAT business).
Personally I go ADSL -> Router -> WiFi -> Computers (yeah should have got an all-in-one I know) the WiFi on it's own isn't enough to allow multiple computers to share the connection.

Not wishing to seem stupid but have you actually configered the Airport 'pod' yet? I know my Mac has little apps for configuring them burried in it although never needed to use them. If the thing isn't configured it probably won't allow anything to connect via it.

/Suspect I'm preaching to the choir