Re: I've killed my domain. (and it was far too easy) :~(
From: Cardman (do-not_at_spam-me.com)
Date: 03/16/04
- Next message: Ricardo: "DHCP Scope"
- Previous message: Aks: "Re: internet connection sharing performance issue"
- In reply to: Cardman: "Re: I've killed my domain. (and it was far too easy) :~("
- Next in thread: Cardman: "Re: I've killed my domain. (and it was far too easy) :~("
- Reply: Cardman: "Re: I've killed my domain. (and it was far too easy) :~("
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 16 Mar 2004 21:34:17 +0000
On Tue, 16 Mar 2004 06:56:32 +0000, Cardman <do-not@spam-me.com>
wrote:
>I expect that I will get there soon enough, but getting this new link
>working in my network's IP range is a lot harder than what I believed
>it would be.
Oh silly me! As of course adding this new wireless NIC is not like
plugging my WAP into my existing network and it being allocated an IP
address within the existing range.
My problem was that the entire 192.168.0.* range is already owned by
my wired NIC on 192.168.0.1. And so trying to share this range was
unhelpful, when this non-flexible system can only route one way.
Anyway, since it would take too long to sub divide this range into
areas, then I decided to start my new wireless network on the IP range
of 192.168.1.* with this NIC being 192.168.1.1.
Kind of wasteful having this entire range for an ad-hoc wireless link
that can only consist of two and no more, but there you go.
Sure enough my Laptop1 computer popped to life and can now see the
server on this NIC. Only problem is that DCHP has yet to allocate my
Laptop1 computer an IP address within this new range.
Setting it manually works, but DCHP starts complaining about an Bad IP
address being used. Maybe it just wants to save 192.168.1.10 for
something else being the first IP address to be allocated, but I hope
that DCHP is limited to allocating IP address only within the servers
IP address range of 192.168.0.*.
I may have even got my wired and wireless networks seeing each other
by adding my two scopes under a super scope, when they can certainly
ping each other, but with all the issues with Laptop1's DCHP and my
old USB problem coming back (My server has old USB v1.0 ports that
like to completely fail USB devices now and again) it is hard to say
for sure at this second.
The Internet connection and connection to the server works fine at
least from both network segments. Except when USB support dies on my
server, which makes me think that I should switch off these first
generation USB ports on this motherboard and buy a USB 2.0 plug in
card.
Also I have discovered Win2k3's basic firewall addition to my Cable
Modem connection, which makes one more problem solved, when I can now
allocate ports through it. Maybe I should give the more advanced
firewall a shot, when allocating a small range to be used to each of
my computers is a very long process one port at a time.
I also have had further developments in my netlogon service startup
problem, when despite confirming the automatic start setting this
service would not auto start on boot.
So I thought it was time for radical action, which is why I deleted
all NICs and all Network services and started this lot from fresh. And
fortunately Microsoft Windows Networking remembered to handle the
netlogon service during following boots.
And so not a bad day for sorting out all my server problems, which has
been causing problems for months. Just have to solve the problem of
what is going on with my problem WAP and my USB ports, where I am then
all solved.
I have just also fished re-establishing all of the 20 shares lost
during this netlogon problem, which puts my small network back in
action.
Cardman.
- Next message: Ricardo: "DHCP Scope"
- Previous message: Aks: "Re: internet connection sharing performance issue"
- In reply to: Cardman: "Re: I've killed my domain. (and it was far too easy) :~("
- Next in thread: Cardman: "Re: I've killed my domain. (and it was far too easy) :~("
- Reply: Cardman: "Re: I've killed my domain. (and it was far too easy) :~("
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|