Re: Changing from 1 NIC to 2 NIC's

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: SuperGumby [SBS MVP] (not_at_your.nellie)
Date: 02/14/05 

Date: Mon, 14 Feb 2005 11:55:50 +1100

tks, better late than never. You can't hardwire those WS's maybe?

I REALLY need to get going.

You're sortta OK for now with your existing setup, things will be going
wrong whether you are noticing them or not, but you're operational. We can
address the rest when time allows.

"susan" <smcrey@mindspring.com> wrote in message
news:u2eZh2iEFHA.2876@TK2MSFTNGP12.phx.gbl...
> ooops...missed something.
>
> 2 workstations that have wireless NIC's instead of cabled into the hub
>
> "susan" <smcrey@mindspring.com> wrote in message
> news:el%23cgmiEFHA.3824@TK2MSFTNGP10.phx.gbl...
>> The ext. nic is connected directly to the wireless router (which has a
>> network cable also from it to the hub)
>> the int. nic is connected to the 24-port hub.
>> workstations are connected to the 24-port hub.
>> nothing else! no phones or print server in the mix except one network
>> printer connected to the 24-port hub.
>>
>> Any clues for you in the above info?
>>
>> So, do i understand you that changing to 192.168.2.x is a sufficient
> enough
>> distinction?
>>
>> I'm setting up another SBS network one in a couple of weeks, so this
>> information is invaluable to me and I am a willing student!
>> Thanks!
>>
>> "SuperGumby [SBS MVP]" <not@your.nellie> wrote in message
>> news:evYRWLiEFHA.480@TK2MSFTNGP10.phx.gbl...
>> > OK, there's what I needed and suspected was the case.
>> >
>> > The workstations are getting their IP's via DHCP from the router. You
> have
>> > not seperated the networks (and I suggest you don't just yet).
>> >
>> > The choice of 10.3.16.x/24 ( /24 is just shorthand for Subnet Mask
>> > 255.255.255.0) is valid, if a little unusual. Many contributors here
> even
>> > prefer such a radical distinction between the internal and external
>> > networks. I DON'T. I don't because I've had problems with equipment
>> > operating in 'classless' IP space. Don't worry if you don't know what
>> > 'classless addressing' is about.
>> >
>> > 192.168.1.x/24 is a distinct subnet from 192.168.2.x/24
>> >
>> > SO, first we have to find out what is connected to what! Please detail
> the
>> > connections between whatever equipment you have.
>> >
>> > ie.
>> > SBS External is connected to router
>> > SBS Internal is connected to switch
>> > Workstations are connected to switch
>> > switch is connected to router (I think, and this is what we want to get
>> rid
>> > of, BUT NOT YET)
>> > and anything else
>> >
>> > THEN, I believe a printserver was mentioned earlier. Is this part of
>> > the
>> > router? or a seperate device?
>> >
>> > Any other non-PC items connected to the network? (Printers? Phone
> Systems?
>> > anything)
>> >
>> > "susan" <smcrey@mindspring.com> wrote in message
>> > news:uqpgrYhEFHA.3824@TK2MSFTNGP10.phx.gbl...
>> > > The workstations point to the int nic for dns and that's all the
>> > > configuration i did on them. Here's sample output:
>> > >
>> > > IP Address. . . . . . . . . . . . : 192.168.1.112
>> > > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> > > Default Gateway . . . . . . . . . : 192.168.1.4
>> > > DHCP Server . . . . . . . . . . . : 192.168.1.1
>> > > DNS Servers . . . . . . . . . . . : 192.168.1.4
>> > > Primary WINS Server . . . . . . . : 192.168.1.4
>> > > Lease Obtained. . . . . . . . . . : Saturday, February 12,
>> > > 2005
>> > > 4:28:56 PM
>> > > Lease Expires . . . . . . . . . . : Tuesday, February 15, 2005
>> > > 4:28:56 PM
>> > >
>> > > Yes, i think I get the picture now on the subnet issue. Will change
> the
>> > > internal nic to a 10.3.16.x configuration. That should work, right?!
>> > >
>> > > Any ideas for me are very very very welcomed!
>> > >
>> > > "SuperGumby [SBS MVP]" <not@your.nellie> wrote in message
>> > > news:%23YSD0%23gEFHA.2508@TK2MSFTNGP09.phx.gbl...
>> > >> I'm sometimes a hard a b.
>> > >>
>> > >> We still don't have the ipconfig of the workstation.
>> > >>
>> > >> You still have a problem in that the internal and external networks
> are
>> > >> in
>> > >> the same subnet, 192.168.1.x, this is not a valid configuration. I
> also
>> > >> suspect that the physical connections between the server, router,
>> > >> and
>> > >> PC's
>> > >> may not be correct. This is why I have asked for the info.
>> > >>
>> > >> "susan" <smcrey@mindspring.com> wrote in message
>> > >> news:OdZ1%23pgEFHA.464@TK2MSFTNGP15.phx.gbl...
>> > >> > Yes yes and yes: this is the result: I very much want your input:
>> > >> >
>> > >> > Windows IP Configuration
>> > >> > Host Name . . . . . . . . . . . . : companyname01
>> > >> > Primary Dns Suffix . . . . . . . : companyname.local
>> > >> > Node Type . . . . . . . . . . . . : Unknown
>> > >> > IP Routing Enabled. . . . . . . . : Yes
>> > >> > WINS Proxy Enabled. . . . . . . . : Yes
>> > >> > DNS Suffix Search List. . . . . . : companyname.local
>> > >> >
>> > >> > Ethernet adapter Server Local Area Connection:
>> > >> >
>> > >> > Connection-specific DNS Suffix . :
>> > >> > Description . . . . . . . . . . . : Broadcom NetXtreme 5751
> Gigabit
>> > >> > Controller
>> > >> > Physical Address. . . . . . . . . : 00-11-11-BE-77-43
>> > >> > DHCP Enabled. . . . . . . . . . . : No
>> > >> > IP Address. . . . . . . . . . . . : 192.168.1.4
>> > >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> > >> > Default Gateway . . . . . . . . . :
>> > >> > DNS Servers . . . . . . . . . . . : 192.168.1.4
>> > >> > Primary WINS Server . . . . . . . : 192.168.1.4
>> > >> >
>> > >> > Ethernet adapter Network Connection:
>> > >> >
>> > >> > Connection-specific DNS Suffix . :
>> > >> > Description . . . . . . . . . . . : Intel 8255x-based PCI
> Ethernet
>> > >> > Adapter (10/100)
>> > >> > Physical Address. . . . . . . . . : 00-A0-C9-59-B1-1D
>> > >> > DHCP Enabled. . . . . . . . . . . : No
>> > >> > IP Address. . . . . . . . . . . . : 192.168.1.3
>> > >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> > >> > Default Gateway . . . . . . . . . : 192.168.1.1
>> > >> > DNS Servers . . . . . . . . . . . : 192.168.1.4
>> > >> > Primary WINS Server . . . . . . . : 192.168.1.4
>> > >> >
>> > >> > "SuperGumby [SBS MVP]" <not@your.nellie> wrote in message
>> > >> > news:eSSMtegEFHA.2508@TK2MSFTNGP09.phx.gbl...
>> > >> >> Please give us the full output of 'ipconfig /all >
> c:\ipconfig.txt'
>> > > from
>> > >> > the
>> > >> >> server and one workstation.
>> > >> >>
>> > >> >> The edited info you are giving us is not enough. I will not ask
>> again.
>> > >> >>
>> > >> >> "Susan" <Susan@discussions.microsoft.com> wrote in message
>> > >> >> news:78FC26F8-FB4C-4166-A269-A03DE0F3FE23@microsoft.com...
>> > >> >> > Hi...i'd LOVE for you to check this and see if it's optimally
>> > >> > configured.
>> > >> >> > Here's what i've got:
>> > >> >> > Here's what i've got:
>> > >> >> > Int NIC:
>> > >> >> > 192.168.1.4
>> > >> >> > 255.255.255.0
>> > >> >> > no gateway
>> > >> >> > 192.168.1.1 (router ip)
>> > >> >> > 192.168.1.4 (int nic ip)
>> > >> >> >
>> > >> >> > EXT NIC:
>> > >> >> > 192.168.1.3
>> > >> >> > 255.255.255.0
>> > >> >> > 192.168.1.1 (gateway)
>> > >> >> > 192.168.1.4 (dns)
>> > >> >> >
>> > >> >> > what do you think? does it look okay?
>> > >> >> >
>> > >> >> >
>> > >> >> >
>> > >> >> > "SuperGumby [SBS MVP]" wrote:
>> > >> >> >
>> > >> >> >> but I want your ipconfigs 'coz I'm not sure you are optimally
>> > >> > configured.
>> > >> >> >>
>> > >> >> >> "Susan" <Susan@discussions.microsoft.com> wrote in message
>> > >> >> >> news:F4B8CA47-D971-448A-8CA2-24C0A3BC648E@microsoft.com...
>> > >> >> >> > Hi SuperGumby!
>> > >> >> >> > Posted somewhere in this thread is an appreciative thank you
> to
>> > > you
>> > >> > for
>> > >> >> >> > "mentioning" i might have to reboot the workstations and
>> > >> >> >> > that
>> > > solved
>> > >> >> >> > the
>> > >> >> >> > problem i was having with them -- and all else, with the
>> > >> >> >> > help
>> of
>> > >> >> >> > you,
>> > >> >> >> > Wes
>> > >> >> >> > and
>> > >> >> >> > Marina, worked out and I lived thru this latest crisis.
>> > >> >> >> >
>> > >> >> >> > I probably shouldn't admit this -- but I obviously need way
>> more
>> > >> >> >> > training
>> > >> >> >> > (LOL!) ...
>> > >> >> >> >
>> > >> >> >> > Thank you all again so much. You're always there to help and
> i
>> > > truly
>> > >> >> >> > appreciate it.
>> > >> >> >> >
>> > >> >> >> > "SuperGumby [SBS MVP]" wrote:
>> > >> >> >> >
>> > >> >> >> >> OK, what we need at this point is to take stock.
>> > >> >> >> >>
>> > >> >> >> >> Please give us the full output of 'ipconfig /all >
>> > > c:\ipconfig.txt'
>> > >> >> >> >> from
>> > >> >> >> >> the
>> > >> >> >> >> server and one workstation. You do not have to be concerned
>> > >> >> >> >> about
>> > >> >> >> >> disclosing
>> > >> >> >> >> 'hacker' information, the router and your use of private IP
>> > > ranges
>> > >> >> >> >> (192.168.etc) makes the info of little value to anyone but
>> those
>> > >> >> >> >> helping.
>> > >> >> >> >>
>> > >> >> >> >>
>> > >> >> >> >>
>> > >> >> >>
>> > >> >> >>
>> > >> >> >>
>> > >> >>
>> > >> >>
>> > >> >
>> > >> >
>> > >>
>> > >>
>> > >
>> > >
>> >
>> >
>>
>>
>
>

Relevant Pages

  • Re: Network Connections x 2 PCs
    ... The setup is quite ... >>> If you have a broadband router, run XP's Network Setup Wizard on both ... tell it that the computers connect to the ... >>> If you have a hub, the setup depends on how many IP addresses you get ...
    (microsoft.public.windowsxp.general)
  • Home network setup
    ... My current home network consists of several PC connected to a Netgear ... wireless router. ... using the "hub" would just plug into one of the four LAN ports. ... The second will serve the DMZ and have ...
    (Ubuntu)
  • Re: The netwrok path was not found
    ... This is the same setup I have and have had no problems. ... your homeportal was connected to a hub? ... It works fine and I have never had an intrusion onto my network. ... > DSL connection and have run the home netwrok setup wizard to connect my ...
    (microsoft.public.windowsxp.network_web)
  • Re: Network DSL Problems and related XP problems
    ... In the initial setup the network were just two desktops using a small ... Cisco managed hub before connecting to DSL. ... I ran the new connection wizard for the DSL modem and then the network ...
    (microsoft.public.windowsxp.network_web)
  • Re: Networking with hub
    ... > I have set up a network with a hub. ... Here is the setup ...
    (microsoft.public.windowsxp.network_web)