Re: Help! Clients are off the network.
- From: "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx>
- Date: Thu, 1 Jan 2009 13:22:55 +1100
Unfortunately, I need to point out thet 'Good Day' would come from a pom, 'strine (the Australian national language) is more succinct, g'day.
inline
"PWT24" <PWT24@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:7721F070-E8DE-4B2B-BF08-B771EA6A64FE@xxxxxxxxxxxxxxxx
Well Good Day Mate! :) It is good to know you. I hope your New Year was a
joyful one and that 2009 brings you much success and happiness.
Great I will give this a try and see where it takes me. I do have some
questions that I placed in line...
"SuperGumby [SBS MVP]" wrote:
Sydney, AU.
OK, if you would prefer to go to one NIC we can disable the 10/100 (or the
Gb, your choice, and as explained earlier it may be quicker), run the CSIP
wiz, see where that puts us.
Assuming CSIP is change server ip wizard right?
Yea, I will try it using the GB NIC.
yep
I'd leave the router disconnected from the network for the moment.
Well it is connected right now so I should disconect the external nic from
it or just not have it plugged into the netgear switch? (earlier I
disconnected the cable between the router and switch and all the workstations
were fine but my daughter complained that she lost her wireless internet
connectivity with her laptop so I plugged it back in and she was up and
running again.) hmmm?
Whether your router is connected to the switches or not it should supply internet connectivity for her as a wireless client. However, it seems that in your previous config the internal and external networks were physically joined (which should not be the case). As such, DHCP on the router would have been off (or SBS would have complained about an additional DHCP server on the network) and if her PC was getting a DHCP address it would have been getting it from DHCP on the SBS.
This physical connection between the external and internal networks probably explains most of your difficulties.
If the clients don't get DHCP leases we either have a corruption in DHCP or
it's not correctly bound to the NIC. Easiest fix might be to remove DHCP
(add/remove programs, windows components, network something), and put it
back. If doing so I do not expect it critical to restart the server after
removal but PLEASE restart after reinstallation, and if you believe in 'belt
and braces', remove, restart, reinstall, restart. Run the CSIP wiz (to
configure DHCP properly).
With you so far...
Restart a workstation and we should get a DHCP lease from the SBS. If so,
"IPConfig /all" from both server and client. If not we figure out why.
If IP is good we move on to WINS/DNS/fileservices and this is mainly a
matter of ensuring bindings are correct. For the most part these can be
expected to 'fall into place'. It's when they don't that we get into real
troubleshooting :-)
Use a workstation directly attached to the router to reconfigure it suitably
for our end setup, connect router to network, run CEICW.
reconfigure it suitably for our end setup, refers to what an earlier post
where you mention "reconfigure it to operate in the SBS subnet"? Can you
give me an example? Would it be 192.168.16.x?
Yes, 192.168.16.x (SBS on .2, router on .1 acting as default gateway for the network), or whatever subnet is convenient but avoid 192.168.0/1/254.x or the 10.x.y.z blocks if you wish to at any time use VPN, due to these commonly being used by 'home routers'.
Last, of the problems, we deal with the iPhone.
Cool
You can then start on putting your Cisco into place.
Going to Pittsburgh, PA in late January to attend an ASA boot camp so I will
wait to deploy the device after that.
Bit of a shame this has to wait. We are effectively lowering the security model by going from 2 to 1 NIC and relying on simple NAT router ability. We can however check basic firewalling on the device and, personally, I can live with it.
"PWT24" <PWT24@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B81F006A-A856-41D5-912B-177FF2DB3379@xxxxxxxxxxxxxxxx
> No problems. Where are you that it is 0300 next year?? I am in New > York.
>
> Things are going well now. Mysteriously. I still would like to go to > one
> nic but I will think it through before I pull out any nics this time :)
>
> Don't worry the new year won't slow me down. I pretty much work about > 18
> hours a day.
>
> Thanks for all your help SuperG! It is truly appreciated!
>
> Tim
>
>
>
> "SuperGumby [SBS MVP]" wrote:
>
>> Sorry dude, had to go out, and it's now 0300 next year. Just dropped >> in
>> to
>> see how you were doing.
>>
>> more on the morrow. (at which time you may not wish to be dealing with
>> it)
>>
>> "PWT24" <PWT24@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:23B3B3EA-4932-45E9-A985-C35094D36D2B@xxxxxxxxxxxxxxxx
>> > oops forgot to include the workstation ipconfig...
>> >
>> > Windows IP Configuration
>> >
>> > Host Name . . . . . . . . . . . . : user
>> > Primary Dns Suffix . . . . . . . : PrecisionWebTech.local
>> > Node Type . . . . . . . . . . . . : Hybrid
>> > IP Routing Enabled. . . . . . . . : No
>> > WINS Proxy Enabled. . . . . . . . : No
>> > DNS Suffix Search List. . . . . . : PrecisionWebTech.local
>> > PrecisionWebTech.local
>> >
>> >
>> >
>> > Ethernet adapter Local Area Connection 2:
>> >
>> > Connection-specific DNS Suffix . : PrecisionWebTech.local
>> > Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
>> > Connection
>> > Physical Address. . . . . . . . . : 00-13-20-56-0E-D1
>> > Dhcp Enabled. . . . . . . . . . . : Yes
>> > Autoconfiguration Enabled . . . . : Yes
>> > IP Address. . . . . . . . . . . . : 192.168.16.10
>> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> > Default Gateway . . . . . . . . . : 192.168.16.2
>> > DHCP Server . . . . . . . . . . . : 192.168.16.2
>> > DNS Servers . . . . . . . . . . . : 192.168.16.2
>> > Primary WINS Server . . . . . . . : 192.168.16.2
>> > Lease Obtained. . . . . . . . . . : Wednesday, December 31, 2008
>> > 12:22:30
>> > AM
>> > Lease Expires . . . . . . . . . . : Thursday, January 08, 2009 >> > 12:22:30
>> > AM
>> >
>> >
>> >
>> > "SuperGumby [SBS MVP]" wrote:
>> >
>> >> in a two NIC setup the external NICs subnet normally doesn't >> >> matter.
>> >> It
>> >> is
>> >> only the internal subnet that is required to be other than that >> >> used
>> >> by
>> >> 'commodity routers'.
>> >>
>> >> "Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@xxxxxxxxxxxxxxx> wrote >> >> in
>> >> message news:ulyeqyqaJHA.4052@xxxxxxxxxxxxxxxxxxxxxxx
>> >> > Steve is right... you need to get your ip and dhcp straightened >> >> > out.
>> >> >
>> >> > As a rule, you should see every nic in your lan pointed to the
>> >> > internal
>> >> > nic of the SBS for DNS. Secondly, the external nic should be on >> >> > a
>> >> > subnet
>> >> > not commonly used by home based routers, meaning that 192.168.0.x
>> >> > and
>> >> > 192.168.1.x are not good choices. (only relevant if you choose >> >> > to
>> >> > allow
>> >> > VPN direct to the server).
>> >> >
>> >> > Run the change server IP wizard to move it to 192.168.xx.2, (you >> >> > can
>> >> > move
>> >> > it back to .16 if you wish).
>> >> >
>> >> > If desired, move the external nic and the LAN side of the router,
>> >> > but
>> >> > not
>> >> > necessary for this exercise.
>> >> >
>> >> > Then run the CEICW and verify that the workstations can get an ip >> >> > in
>> >> > the
>> >> > same range as the server internal nic.
>> >> >
>> >> > Once that works, than if you can ping the server from the
>> >> > workstations
>> >> > by
>> >> > ip and by name, you should be good to go.
>> >> >
>> >> > If none of this fixes it, give us a new config and look at the
>> >> > properties
>> >> > of the DHCP server and make sure your switch is working. You >> >> > should
>> >> > be
>> >> > able to do that by putting the workstation on static in the same
>> >> > range
>> >> > and
>> >> > ping server ip should then be successful.
>> >> >
>> >> > -- >> >> > Larry
>> >> > Please post the resolution to your
>> >> > issue so that others may benefit.
>> >> >
>> >> >
>> >> > "SteveB" <newsgroup@xxxxxxxxxx> wrote in message
>> >> > news:%23DaCQmqaJHA.1704@xxxxxxxxxxxxxxxxxxxxxxx
>> >> >> In your first post you mentioned changing the server IP address
>> >> >> several
>> >> >> times. Did you use the Change IP wizard to do this? You >> >> >> certainly
>> >> >> need
>> >> >> to
>> >> >> get DHCP running properly on the SBS so that clients can receive >> >> >> a
>> >> >> valid
>> >> >> IP address.
>> >> >>
>> >> >> "PWT24" <PWT24@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> >> news:E05AF564-68B4-4563-A917-F77FB92751E3@xxxxxxxxxxxxxxxx
>> >> >>> Thanks Larry. I would like to fix what I have then go to one >> >> >>> nic
>> >> >>> then
>> >> >>> worry
>> >> >>> about the phones.
>> >> >>>
>> >> >>> Here are the results from the server;
>> >> >>>
>> >> >>>
>> >> >>> Windows IP Configuration
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> Host Name . . . . . . . . . . . . : myservername
>> >> >>>
>> >> >>> Primary Dns Suffix . . . . . . . : mydomainname.local
>> >> >>>
>> >> >>> Node Type . . . . . . . . . . . . : Unknown
>> >> >>>
>> >> >>> IP Routing Enabled. . . . . . . . : Yes
>> >> >>>
>> >> >>> WINS Proxy Enabled. . . . . . . . : Yes
>> >> >>>
>> >> >>> DNS Suffix Search List. . . . . . : mydomainname.local
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> Ethernet adapter Server Local Area Connection:
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> Connection-specific DNS Suffix . :
>> >> >>>
>> >> >>> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT >> >> >>> Network
>> >> >>> Connection
>> >> >>>
>> >> >>> Physical Address. . . . . . . . . : 00-0E-0C-3E-A7-FB
>> >> >>>
>> >> >>> DHCP Enabled. . . . . . . . . . . : No
>> >> >>>
>> >> >>> IP Address. . . . . . . . . . . . : 192.168.1.124
>> >> >>>
>> >> >>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> >> >>>
>> >> >>> Default Gateway . . . . . . . . . : 192.168.1.1
>> >> >>>
>> >> >>> DNS Servers . . . . . . . . . . . : 192.168.16.2
>> >> >>>
>> >> >>> Primary WINS Server . . . . . . . : 192.168.1.124
>> >> >>>
>> >> >>> NetBIOS over Tcpip. . . . . . . . : Disabled
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> Ethernet adapter Local Area Connection 2:
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> Connection-specific DNS Suffix . :
>> >> >>>
>> >> >>> Description . . . . . . . . . . . : Linksys LNE100TX Fast
>> >> >>> Ethernet
>> >> >>> Adapter(LNE100TX v4)
>> >> >>>
>> >> >>> Physical Address. . . . . . . . . : 00-0C-41-E6-32-AA
>> >> >>>
>> >> >>> DHCP Enabled. . . . . . . . . . . : No
>> >> >>>
>> >> >>> IP Address. . . . . . . . . . . . : 192.168.16.2
>> >> >>>
>> >> >>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> >> >>>
>> >> >>> Default Gateway . . . . . . . . . :
>> >> >>>
>> >> >>> DNS Servers . . . . . . . . . . . : 192.168.16.2
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> Here are the results from a workstation;
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> Windows IP Configuration
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> Host Name . . . . . . . . . . . . : username
>> >> >>>
>> >> >>> Primary Dns Suffix . . . . . . . : mydomainname.local
>> >> >>>
>> >> >>> Node Type . . . . . . . . . . . . : Broadcast
>> >> >>>
>> >> >>> IP Routing Enabled. . . . . . . . : No
>> >> >>>
>> >> >>> WINS Proxy Enabled. . . . . . . . : No
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> Ethernet adapter Local Area Connection 2:
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> Connection-specific DNS Suffix . :
>> >> >>>
>> >> >>> Description . . . . . . . . . . . : Intel(R) PRO/100 VE
>> >> >>> Network
>> >> >>> Connection
>> >> >>>
>> >> >>> Physical Address. . . . . . . . . : 00-13-20-56-0E-D1
>> >> >>>
>> >> >>> Dhcp Enabled. . . . . . . . . . . : Yes
>> >> >>>
>> >> >>> Autoconfiguration Enabled . . . . : Yes
>> >> >>>
>> >> >>> Autoconfiguration IP Address. . . : 169.254.50.174
>> >> >>>
>> >> >>> Subnet Mask . . . . . . . . . . . : 255.255.0.0
>> >> >>>
>> >> >>> Default Gateway . . . . . . . . . :
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> "Larry Struckmeyer [SBS-MVP]" wrote:
>> >> >>>
>> >> >>>> Seems we should first fix what you have, than move to one nic >> >> >>>> if
>> >> >>>> you
>> >> >>>> want,
>> >> >>>> or fix the iphone with one or two nics your call.
>> >> >>>>
>> >> >>>> To work on the present issue, please post the unedited results
>> >> >>>> of:
>> >> >>>>
>> >> >>>> ipconfig /all > c:\iptest.txt
>> >> >>>>
.
- References:
- Re: Help! Clients are off the network.
- From: SuperGumby [SBS MVP]
- Re: Help! Clients are off the network.
- From: PWT24
- Re: Help! Clients are off the network.
- Prev by Date: X7SBA Remote managemnet card for SBS2003
- Next by Date: Re: Automating Exchange IMF updates?
- Previous by thread: Re: Help! Clients are off the network.
- Next by thread: Re: Automating Exchange IMF updates?
- Index(es):
Relevant Pages
|
