Re: Still Have Problem on Internal Adapter
From: Peter (me_at_privacy.net.au)
Date: 04/05/04
- Next message: Javier Gomez [SBS MVP]: "Re: Problem installing Terminal Server on SBS2003 Std."
- Previous message: Anthony Mariniello: "Re: Stop Error 0x00000050"
- In reply to: Daniel Sun: "Re: Still Have Problem on Internal Adapter"
- Next in thread: David Southern: "Re: Still Have Problem on Internal Adapter"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 5 Apr 2004 10:01:19 +1000
So is 192.168.16.2 your server? It should also be the default gateway on
your LAN.
What device is 192.168.16.110? Is this a client you configured with a
static address?
"Daniel Sun" <anonymous@discussions.microsoft.com> wrote in message
news:177d501c418ee$115988e0$a301280a@phx.gbl...
When clients are configured with DHCP, ipconfig /all shows
the following:
DHCP Enabled: Yes
Autoconfiguration Enabled: Yes
Autoconfiguration IP address: 169.254.58.130
Subnet Mask: 255.255.0.0
Default Gateway:
DNS Server:
When I punched in static IP, ipconfig /all shows:
DHCP Enabled: No
IP address: 192.168.16.110
Subnet Mask: 255.255.255.0
Default Gateway:
DNS Server: 192.168.16.2
With either settings, clients can't get onto the Internet,
nor can it ping the server (name or ip), or vice versa.
Thanks.
>-----Original Message-----
>What does the client ipconfig /all show? how are the
clients set as far as
>gateway etc is concerned for the nic?
>
>
>"Daniel Sun" <anonymous@discussions.microsoft.com> wrote
in message
>news:176d901c418da$88411400$a301280a@phx.gbl...
>I have SBS 2003 standard edition (without ISA, dynamic IP
>address) running on my server, a router connected between
>DSL modem and the server. Now I installed an internal NIC
>on the server and connect it to a switch (plug-and-play)
>and to my workstations. My server can get onto the
>Internet, but the workstations can't, and neither can
>they talk to the server. Workstations have 169.x.x.x
>address. Here is how the configuration was done:
>1. Router's DHCP - Disabled.
>2. Internal NIC property - checked all the following:
>· Microsoft Client for Networks
>· Network load Balancing
>· File and Printer Sharing
>· Internal Protocol (TCP/IP)
>3. External NIC property - checked only TCP/IP
>4. From Advanced Settings: Internal NIC bind File
>and Printer Sharing and Client for Microsoft Networks to
>TCP/IP
>5. From Advanced Settings: External NIC binding:
>unchecked all
>6. DHCP setup.
>· Address Pool: 192.168.16.1 to 192.168.16.254
>· Scope Options:
>· 003 Router 192.168.16.2
>· 006 DNS Servers 192.168.16.2
>· 015 DNS Domain Name mycompany.local
>· 044 WINS/NBNS Servers 192.168.16.2
>· 046 WINS/NBT Node Type 0x8
> 7. Authorized DHCP server.
> 8. In DHCP console, the server has a green arrow point
>up on its left, and the status is Running.
> The scope (192.168.16.0) status is Active.
> 9. Run the Change Server IP Address Wizard to change
>the server IP address.
> 10. Run ICW.
>
>On server, ipconfig /all shows the following:
>Ethernet adapter Local Area Connection 2:
>DHCP Enabled: No
>IP address: 192.168.16.2
>Subnet Mask: 255.255.255.0
>Default gateway:
>DNS servers: 192.168.16.2
>Primary WINS Server: 192.168.16.2
>
>Ethernet adapter Server Local Area Connection 2:
>DHCP Enabled: No
>IP address: 192.168.0.10
>Subnet Mask: 255.255.255.0
>Default gateway: 192.168.0.1
>DNS servers: 192.168.16.2
>
>When I do ipconfig /renew from the client, I get message:
>DHCP server unreachable.
>
>Please help. Thanks.
>
>
>.
>
- Next message: Javier Gomez [SBS MVP]: "Re: Problem installing Terminal Server on SBS2003 Std."
- Previous message: Anthony Mariniello: "Re: Stop Error 0x00000050"
- In reply to: Daniel Sun: "Re: Still Have Problem on Internal Adapter"
- Next in thread: David Southern: "Re: Still Have Problem on Internal Adapter"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
