fugazer
asked on
DHCP for 2 NIC connected to 1 computer with cross over cable
Hello, My setup goes as follows:
- Windows 2003 behind linksys router (dd wrt) via NIC #1 (static ip)
- DHCP is disabled on router and installed and working on W2K3
I can successfully have other people connect to my router and the server and my windows DHCP works no problem.
- I have a second NIC installed within my W2K3 machine
- I have NAT setup to allow internet and networking via NIC#2
- My working computer (mac) is connected to NIC #2 with a cross over cable
The reason i connect to NIC#2 via crossover cable is because my router doesn't connect at 1000T.. I would like this fast connection with my working computer (mac mini) and my server so that's why i have not connected directly to the router.
So my mac only works if i manually assign its TCP/IP settings.. Which are:
IP: 169.254.219.182
Subnet: 255.255.0.0
Router: 69.254.127.33 (this is the ip address of NIC#2 in the windows box)
DNS: 192.168.1.100
Search Domain: mydomain.com
This is fine.. it connects (i can use the internet and connect to my active directory).. But when i change my setting from a static configuration to DHCP i get these settings:
IP: 169.254.250.179
Subnet Mask: 255.255.0.0
Router: 169.254.127.33
DNS: 'nothing'
Search Domain: 'nothing'
and nothing works.. i can't see my server, can't connected to the internet etc..
I'm connected the mac directly via a cross over cable so i'm wondering if thats the problem?? Why isn't DHCP assigning an address to my mac? Is it because i need router in between or something? Is my understand of NAT wrong in the first place? Does a DHCP scope need to be assigned to NIC#2? and what's DHCP relay, does this have anything to do with it?? It all seems confusing at first, but with a little logic i will understand what i'm doing wrong.
I've figured out alot of W2K3 on my own as well as understanding how networking works.. But i'm still kind of new to the termanolgies used and i often find myself spending hours trying to fix a problem that would ordanarly take minuits if i knew my logic was correct in the first place..
Any advice regarding my setup would be most helpful.. Thanks in advance, i'm new to Experts Exchange and have already found this to be a great community.
- Windows 2003 behind linksys router (dd wrt) via NIC #1 (static ip)
- DHCP is disabled on router and installed and working on W2K3
I can successfully have other people connect to my router and the server and my windows DHCP works no problem.
- I have a second NIC installed within my W2K3 machine
- I have NAT setup to allow internet and networking via NIC#2
- My working computer (mac) is connected to NIC #2 with a cross over cable
The reason i connect to NIC#2 via crossover cable is because my router doesn't connect at 1000T.. I would like this fast connection with my working computer (mac mini) and my server so that's why i have not connected directly to the router.
So my mac only works if i manually assign its TCP/IP settings.. Which are:
IP: 169.254.219.182
Subnet: 255.255.0.0
Router: 69.254.127.33 (this is the ip address of NIC#2 in the windows box)
DNS: 192.168.1.100
Search Domain: mydomain.com
This is fine.. it connects (i can use the internet and connect to my active directory).. But when i change my setting from a static configuration to DHCP i get these settings:
IP: 169.254.250.179
Subnet Mask: 255.255.0.0
Router: 169.254.127.33
DNS: 'nothing'
Search Domain: 'nothing'
and nothing works.. i can't see my server, can't connected to the internet etc..
I'm connected the mac directly via a cross over cable so i'm wondering if thats the problem?? Why isn't DHCP assigning an address to my mac? Is it because i need router in between or something? Is my understand of NAT wrong in the first place? Does a DHCP scope need to be assigned to NIC#2? and what's DHCP relay, does this have anything to do with it?? It all seems confusing at first, but with a little logic i will understand what i'm doing wrong.
I've figured out alot of W2K3 on my own as well as understanding how networking works.. But i'm still kind of new to the termanolgies used and i often find myself spending hours trying to fix a problem that would ordanarly take minuits if i knew my logic was correct in the first place..
Any advice regarding my setup would be most helpful.. Thanks in advance, i'm new to Experts Exchange and have already found this to be a great community.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That's a great start guys..
I'm not quite sure what that appropriate IP, Subnet, Gateway and DNS i should set up for NIC2 though..
NIC#1 is (which works fine):
IP: 192.168.1.100
Subnet: 255.255.255.0
Gateway: 192.168.1.1
DNS: 192.168.1.100
Here's what i have choosen for NIC#2, but i'm not sure if my choices are correct:
IP: 10.0.0.100
Subnet: 255.0.0.0
Gateway: 192.168.1.1
DNS: 192.168.1.100
It's my understanding that i need to have a different Subnet then NIC#1, correct?? When i hit 'ok' after putting in those settings for NIC#2 it gave me a warning message saying 'Warning - The default Gateway is Not on the same Network Segment that is defined by the IP and Subnet Mask. Do you want to continue?' I said yes then moved on to creating a new DHCP Scope for NIC#2..
My scope is: 10.0.0.110 - 10.0.0.120
003 Router: 192.168.1.1
006 DNS Server: 10.0.0.100
015 DNS Domain Name: mycompany.com
I hit renew on the Mac to refresh my dhcp lease but it doesn't seem to work.. This is what it inherits:
IP: 169.254.180.160
Subnet: 255.255.0.0
Router: 'nothing'
DNS: 'nothing'
So i think my setting's are definetly wrong.. What would you suggest I use for my NIC#2 setup and the Scope for this adapter to work correctly??
What was the warning message about when i attempted to set NIC#2? and finally, under Routing and Remote Access do i need to configure the Address Assignment tab under 'Nat/Basic Firewall'?? B/c right now it seems to have some default setting of IP: 169.254.0.0 and Subnet: 255.255.0.0 I'm not sure if that is interfering with what i'm trying to accomplish.. Thanks again.
I'm not quite sure what that appropriate IP, Subnet, Gateway and DNS i should set up for NIC2 though..
NIC#1 is (which works fine):
IP: 192.168.1.100
Subnet: 255.255.255.0
Gateway: 192.168.1.1
DNS: 192.168.1.100
Here's what i have choosen for NIC#2, but i'm not sure if my choices are correct:
IP: 10.0.0.100
Subnet: 255.0.0.0
Gateway: 192.168.1.1
DNS: 192.168.1.100
It's my understanding that i need to have a different Subnet then NIC#1, correct?? When i hit 'ok' after putting in those settings for NIC#2 it gave me a warning message saying 'Warning - The default Gateway is Not on the same Network Segment that is defined by the IP and Subnet Mask. Do you want to continue?' I said yes then moved on to creating a new DHCP Scope for NIC#2..
My scope is: 10.0.0.110 - 10.0.0.120
003 Router: 192.168.1.1
006 DNS Server: 10.0.0.100
015 DNS Domain Name: mycompany.com
I hit renew on the Mac to refresh my dhcp lease but it doesn't seem to work.. This is what it inherits:
IP: 169.254.180.160
Subnet: 255.255.0.0
Router: 'nothing'
DNS: 'nothing'
So i think my setting's are definetly wrong.. What would you suggest I use for my NIC#2 setup and the Scope for this adapter to work correctly??
What was the warning message about when i attempted to set NIC#2? and finally, under Routing and Remote Access do i need to configure the Address Assignment tab under 'Nat/Basic Firewall'?? B/c right now it seems to have some default setting of IP: 169.254.0.0 and Subnet: 255.255.0.0 I'm not sure if that is interfering with what i'm trying to accomplish.. Thanks again.
Your gateway generally has to be on the same network as the IP address of the NIC or else it can't go anywhere, but If routing is configured the machine will route between the two interfaces as needed.
169.254.0.0 comes from automatic private IP addressing, a feature of the OS that allows very small networks to communicate between machines without benefit of a DHCP server.
So, next step would be to make sure that DHCP is running and bound to interface 2.
Cheers!
169.254.0.0 comes from automatic private IP addressing, a feature of the OS that allows very small networks to communicate between machines without benefit of a DHCP server.
So, next step would be to make sure that DHCP is running and bound to interface 2.
Cheers!
ASKER
I left my computer for about 5min came back and the Mac DHCP lease worked (its just takes a while for it to resolve).. That's the first part of the battle won (i think).. But the internet won't work and neither does my access to the network..
So yes, Looks like DHCP is running and bound to interface 2 but i must have configured something wrong..
What should my gateway be? Do i need to tweak something in my settings specified above?? I'm going to try to assign a gateway to NIC#2 of 10.0.0.1 to see if that works.. I hit 'ok' and this message appears "Multiple default gateways are intended to provide redundancy to a single network. They will not function properly when that are on two separate, disjoint networks. Do you want to save this configuration?"
I'm going to hit Yes and see what happens.. Am I on the right track?
So yes, Looks like DHCP is running and bound to interface 2 but i must have configured something wrong..
What should my gateway be? Do i need to tweak something in my settings specified above?? I'm going to try to assign a gateway to NIC#2 of 10.0.0.1 to see if that works.. I hit 'ok' and this message appears "Multiple default gateways are intended to provide redundancy to a single network. They will not function properly when that are on two separate, disjoint networks. Do you want to save this configuration?"
I'm going to hit Yes and see what happens.. Am I on the right track?
For internet access to work, you'll need to provide a valid DNS server either through the scape or set on the work station manually. Open DNS is a good service and can be reached at 208.67.222.222.
What is using 10.0.0.1? You can't set your gateway to an IP that doesn't exist if you want to get anywhere. The 192.168.1.100 should work as the server will already have that entry in its routing table.
Glad to hear that DHCP kicked in, have the battle is won.
What is using 10.0.0.1? You can't set your gateway to an IP that doesn't exist if you want to get anywhere. The 192.168.1.100 should work as the server will already have that entry in its routing table.
Glad to hear that DHCP kicked in, have the battle is won.
ASKER
I got the internet to work by setting the Gateway to '192.168.1.1' for NIC#2 but i needed to change '003 Router' to 10.0.0.100 (the IP of NIC#2).. To that's great news..
Now all that remains in my network access.. I can see my 'home' server when browsing for it on my Mac, but every time i try to access 'home' it says Connecting Failed.. Do you have any last words of advice to complete my network settings? You've been great help so far.
Now all that remains in my network access.. I can see my 'home' server when browsing for it on my Mac, but every time i try to access 'home' it says Connecting Failed.. Do you have any last words of advice to complete my network settings? You've been great help so far.
Glad to be of help.
can you ping the server that you're trying to reach from the MAC? What are the firewall settings on the server? (try disabling as diagnostic step) Can you still access the shares from another workstation on the same subnet?
can you ping the server that you're trying to reach from the MAC? What are the firewall settings on the server? (try disabling as diagnostic step) Can you still access the shares from another workstation on the same subnet?
ASKER
Yup.. I can ping the server name from my Mac with success.
Under Routing and Remote Access -> IP Routing -> NAT/Basic Firewall it shows 3 Interfaces:
- NIC #1
- NIC #2
- Internal
I think my firewall is disabled on NIC#1 b/c under properties i have disabled 'enable basic firewall for this interface'.. So unless i missed something the firewall is off for this interface.
But for NIC #2, under properties, i don't see any firewall options b/c its set to 'Private Interface Connected to Private Network' (so the basic firewall settings are grayed out).. It would appear that some kind of firewall is stopping me from reaching the shares, b/c i can see the server on the Mac but i just cant connect to it.
With regards to accessing the shares from another workstation on the same subnet, i only have 2 computers.. My Server, then my Mac so i don't think i can test this.
Is this a sub-netting problem?? Or am i missing something else?
Also, when i right click 'NAT / Basic Firewall' then go to properties there are a couple area's of interest i could use some advice about..
1) Address Assignment.. which is currently set to:
Automatically assign IP addresses by using DHCP allocator is set to 'Enabled' (checked)
IP Address: 169.254.0.0
Subnet: 255.255.0.0
2) Name Resolution.. which is currently set to:
Client using Domain Name System (DNS) is set to 'Disabled' (unchecked)
Does the Address Assignment (1) need to be changed? What is this corresponding to? And are the settings in there correct? and for (2) Name Resolution, do i need to do anything here??
Under Routing and Remote Access -> IP Routing -> NAT/Basic Firewall it shows 3 Interfaces:
- NIC #1
- NIC #2
- Internal
I think my firewall is disabled on NIC#1 b/c under properties i have disabled 'enable basic firewall for this interface'.. So unless i missed something the firewall is off for this interface.
But for NIC #2, under properties, i don't see any firewall options b/c its set to 'Private Interface Connected to Private Network' (so the basic firewall settings are grayed out).. It would appear that some kind of firewall is stopping me from reaching the shares, b/c i can see the server on the Mac but i just cant connect to it.
With regards to accessing the shares from another workstation on the same subnet, i only have 2 computers.. My Server, then my Mac so i don't think i can test this.
Is this a sub-netting problem?? Or am i missing something else?
Also, when i right click 'NAT / Basic Firewall' then go to properties there are a couple area's of interest i could use some advice about..
1) Address Assignment.. which is currently set to:
Automatically assign IP addresses by using DHCP allocator is set to 'Enabled' (checked)
IP Address: 169.254.0.0
Subnet: 255.255.0.0
2) Name Resolution.. which is currently set to:
Client using Domain Name System (DNS) is set to 'Disabled' (unchecked)
Does the Address Assignment (1) need to be changed? What is this corresponding to? And are the settings in there correct? and for (2) Name Resolution, do i need to do anything here??
If you can ping, it suggests that the subnets are ok. Did you say that internet access is now working on the MAC? What IP does the MAC have?
Which adapter is the info below corresponding to? This suggests that it is not fully configured.
1) Address Assignment.. which is currently set to:
Automatically assign IP addresses by using DHCP allocator is set to 'Enabled' (checked)
IP Address: 169.254.0.0
Subnet: 255.255.0.0
2) Name Resolution.. which is currently set to:
Client using Domain Name System (DNS) is set to 'Disabled' (unchecked)
Which adapter is the info below corresponding to? This suggests that it is not fully configured.
1) Address Assignment.. which is currently set to:
Automatically assign IP addresses by using DHCP allocator is set to 'Enabled' (checked)
IP Address: 169.254.0.0
Subnet: 255.255.0.0
2) Name Resolution.. which is currently set to:
Client using Domain Name System (DNS) is set to 'Disabled' (unchecked)
ASKER
Yes the internet is now working on the Mac after i set the '003 Router' to 10.0.0.100 in my DHCP scope options.
With regards to (1) Address Assignment and (2) Name Resolution, these are setting i found when going to
Routing and Remote Settings -> IP Routing -> then right clicking on 'NAT/Basic Firewall' and going to properties..
I think i'm just confused with these settings all together so i'm not sure if they are related to the Mac not being able to connect to the server shares..
With regards to (1) Address Assignment and (2) Name Resolution, these are setting i found when going to
Routing and Remote Settings -> IP Routing -> then right clicking on 'NAT/Basic Firewall' and going to properties..
I think i'm just confused with these settings all together so i'm not sure if they are related to the Mac not being able to connect to the server shares..
ASKER
Sorry i forgot to include my DHCP lease assigned to my mac:
IP: 10.0.0.110
Subnet: 255.0.0.0
Router: 10.0.0.100
DNS Server: 10.0.0.100
Domain: mycompany.com
IP: 10.0.0.110
Subnet: 255.0.0.0
Router: 10.0.0.100
DNS Server: 10.0.0.100
Domain: mycompany.com
Oh, you're not using NAT in this case, so no worries there.
At this point with accessing the shares on the windows server, it is time to check for settings related to SMB shares on the MAC. I'm not a MAC person, so I'm fuzzy on that part.
the info below might be of help
>>>
Macintoshes are required to have the Microsoft User Authentication Module (UAM) installed.
This module allows a Mac to send encrypted passwords to a Windows server.
There are different versions of the UAM specific to OS X and prior Mac OS versions.
The UAM is available for download f rom Microsoft.
http://www.microsoft.com/mac/otherproducts/otherproducts.aspx?pid=windows2000sfm
At this point with accessing the shares on the windows server, it is time to check for settings related to SMB shares on the MAC. I'm not a MAC person, so I'm fuzzy on that part.
the info below might be of help
>>>
Macintoshes are required to have the Microsoft User Authentication Module (UAM) installed.
This module allows a Mac to send encrypted passwords to a Windows server.
There are different versions of the UAM specific to OS X and prior Mac OS versions.
The UAM is available for download f rom Microsoft.
http://www.microsoft.com/mac/otherproducts/otherproducts.aspx?pid=windows2000sfm
This might be the ticket! I've ran into the very same problem with DOS clients. ;)
http://allinthehead.com/retro/218/accessing-a-windows-2003-share-from-os-x
http://allinthehead.com/retro/218/accessing-a-windows-2003-share-from-os-x
ASKER
I'm going to read those 2 links you just sent me..
In the mean time, i disconnected my mac cross over cable and plugged into one of the ports on the router to see if i could connect to the server shares.. Sure enough it worked..
It's looking like there's something up with NIC#2 connection.. brb after i read those links :)
In the mean time, i disconnected my mac cross over cable and plugged into one of the ports on the router to see if i could connect to the server shares.. Sure enough it worked..
It's looking like there's something up with NIC#2 connection.. brb after i read those links :)
ASKER
Small Progress report..
i can connect to my shares if i manually mount them... This is now leaning towards a Mac problem.. I will keep you posted.
i can connect to my shares if i manually mount them... This is now leaning towards a Mac problem.. I will keep you posted.
ASKER
And Final Progress Report.
Everything is working now.. Thank you very much for your guidance in getting DHCP working on my second NIC.. I have learned a lot throughout this process and gained valuable knowledge of networking and Windows Server 2003..
The final kink in the puzzle was very simple.. All i had to do was clear my KeyChain settings for smb://home/ then reconnect with my username and password.. Everything is working, even after powering down the mac.
I had a small chuckle after being able to browse the server from my mac.. Check out the default icon Leopard assigns to Windows... ohh poor microsoft :(
So thanks very much Carrng for the support today as well as Jascot.. Hope you have a great day.
Picture-1.png
Everything is working now.. Thank you very much for your guidance in getting DHCP working on my second NIC.. I have learned a lot throughout this process and gained valuable knowledge of networking and Windows Server 2003..
The final kink in the puzzle was very simple.. All i had to do was clear my KeyChain settings for smb://home/ then reconnect with my username and password.. Everything is working, even after powering down the mac.
I had a small chuckle after being able to browse the server from my mac.. Check out the default icon Leopard assigns to Windows... ohh poor microsoft :(
So thanks very much Carrng for the support today as well as Jascot.. Hope you have a great day.
Picture-1.png
ASKER
..looks like i spoke too soon.
To make doubly sure that everything was working properly i decided to shut down both my mac and the server to unsure everything was working after a reset..
Sure enough, problems..
The mac can no longer automatically see 'Home' in my network places and there is a Blue Exclamation Mark on the DHCP scope set for NIC#2..
It has a bunch of DHCP leases listed now.. This is was i get for cracking a joke about the Microsoft Icon :(
Any clues??
To make doubly sure that everything was working properly i decided to shut down both my mac and the server to unsure everything was working after a reset..
Sure enough, problems..
The mac can no longer automatically see 'Home' in my network places and there is a Blue Exclamation Mark on the DHCP scope set for NIC#2..
It has a bunch of DHCP leases listed now.. This is was i get for cracking a joke about the Microsoft Icon :(
Any clues??
I can't seem to remember if the server is also a domain controller. I ask because DHCP servers must be authorized in active directory, so that is one thought.
As for the extra leases, do you have wireless configured anywhere that could be connecting to this network? You can check the MAC addresses that the leased addresses are assigned to and that might provide a clue as well.
As for the extra leases, do you have wireless configured anywhere that could be connecting to this network? You can check the MAC addresses that the leased addresses are assigned to and that might provide a clue as well.
ASKER
Yes there's a domain controller..
When i installed the DHCP service for the first time i authorized it in active directory..
There is a wireless connected to NIC#1 but no one is connected.. It's set up to filter only the MAC address that i specified (which is none at the moment)..
Since i only have 10 leases available lease 1 is correct (its my mac)... But the other 9 entries say:
10.0.0.111 home.mycompany.com infinite DHCP RAS
10.0.0.112 etc
10.0.0.113 etc...
until it stops at .120
Here's something strange.. I can delete all these additional leases without any problems.. But then if i power down my mac, and restart, all these home.mycompany.com leases appear again.. Something is triggering all these leases when the mac starts..
When i installed the DHCP service for the first time i authorized it in active directory..
There is a wireless connected to NIC#1 but no one is connected.. It's set up to filter only the MAC address that i specified (which is none at the moment)..
Since i only have 10 leases available lease 1 is correct (its my mac)... But the other 9 entries say:
10.0.0.111 home.mycompany.com infinite DHCP RAS
10.0.0.112 etc
10.0.0.113 etc...
until it stops at .120
Here's something strange.. I can delete all these additional leases without any problems.. But then if i power down my mac, and restart, all these home.mycompany.com leases appear again.. Something is triggering all these leases when the mac starts..
ASKER
not sure if this information helps at all.. but i noticed in the windows DNS that when my mac connects is add's several Host (A) entires..
mymac Host (A) 172.16.72.1
mymac Host (A) 10.0.0.100
mymac Host (A) 172.16.145.1
i can understand why a entry is made for 10.0.0.100, but what are those other 2 rogue Host A entires doing in there?? If i delete them and reboot the mac, they come back??
mymac Host (A) 172.16.72.1
mymac Host (A) 10.0.0.100
mymac Host (A) 172.16.145.1
i can understand why a entry is made for 10.0.0.100, but what are those other 2 rogue Host A entires doing in there?? If i delete them and reboot the mac, they come back??
Strange, maybe the MAC sends out multiple DHCP requests for some reason?
As for the blue exclamation point, that generally is a problem with AD authorization and I have had them become unauthorized after I authorized them the first time. Its weird, but not unheard of.
As for the blue exclamation point, that generally is a problem with AD authorization and I have had them become unauthorized after I authorized them the first time. Its weird, but not unheard of.
Ah, you might want to look for a setting called "multi-homed" on the MAC's IP settings and disable it.
ASKER
I think i figured out what all those RAS leases were..
https://www.experts-exchange.com/questions/21352130/DHCP-Question-on-a-SBS-2003-server-server-assigning-ips-to-itself-using-RAS-as-unique-ID.html?sfQueryTermInfo=1+id+ra+uniqu
samccarthy's answer regarding VPN takes up 10 leases at a time.. I fixed my problem by increasing my Scope for a total of 20 leases.. Blue Exclamation Marks went away..
Its just strange how when powering on the mac that's when these RAS leases are initiated..
With regards to:
mymac Host (A) 172.16.72.1
mymac Host (A) 10.0.0.100
mymac Host (A) 172.16.145.1
those extra IP's (172.16.x.x) were being caused by a Mac program called VMWare Fusion (its a virtual machine for mac)..
https://www.experts-exchange.com/questions/21352130/DHCP-Question-on-a-SBS-2003-server-server-assigning-ips-to-itself-using-RAS-as-unique-ID.html?sfQueryTermInfo=1+id+ra+uniqu
samccarthy's answer regarding VPN takes up 10 leases at a time.. I fixed my problem by increasing my Scope for a total of 20 leases.. Blue Exclamation Marks went away..
Its just strange how when powering on the mac that's when these RAS leases are initiated..
With regards to:
mymac Host (A) 172.16.72.1
mymac Host (A) 10.0.0.100
mymac Host (A) 172.16.145.1
those extra IP's (172.16.x.x) were being caused by a Mac program called VMWare Fusion (its a virtual machine for mac)..
If RRAS is pulling from your DHCP server, it will take leases in blocks of ten, that is true.
I'd appreciate it if you would accept my answer. :)
ASKER
sorry carrng.. i wanted to test everything over a couple days before i accepted the answer..
On that note, everything does seem to be working thanks to your help.. Cheer's Carrng, have a great day!
On that note, everything does seem to be working thanks to your help.. Cheer's Carrng, have a great day!
Like carrng said, DHCP relay is used when you want the DHCP service on your server to serve out IP assignments to a network on the other side of a router, which would block the broadcast traffic that DHCP uses.