What I would probably do . . .

Post #230,076 by Andrew Grygus 10/19/05 1:53:40 PM Reply	What I would probably do . . . . . is set up two networks with a router in between and use a router that can also be the DHCP server for one side. The 192.168.n.n is a special address set intended to support 254 addresses and I'm not sure if there will be problems trying to expand that by changing the mask. Others may have different opinions. The 10.n.n.n series (mask 255.0.0.0) supports a whole lot more and there's one in between but I can never remember the numbers. [link\|http://www.aaxnet.com\|AAx]
Post #230,079 by Yendor 10/19/05 2:15:54 PM Reply	The other one... [mike@oftheother Shared]$ whois 172.16.0.0\n\nOrgName: Internet Assigned Numbers Authority\nOrgID: IANA\nAddress: 4676 Admiralty Way, Suite 330\nCity: Marina del Rey\nStateProv: CA\nPostalCode: 90292-6695\nCountry: US\n\nNetRange: 172.16.0.0 - 172.31.255.255\nCIDR: 172.16.0.0/12\nNetName: IANA-BBLK-RESERVED\nNetHandle: NET-172-16-0-0-1\nParent: NET-172-0-0-0-0\nNetType: IANA Special Use\nNameServer: BLACKHOLE-1.IANA.ORG\nNameServer: BLACKHOLE-2.IANA.ORG\nComment: This block is reserved for special purposes.\nComment: Please see RFC 1918 for additional information.\nComment:\nRegDate: 1994-03-15\nUpdated: 2002-09-12\n\nOrgAbuseHandle: IANA-IP-ARIN\nOrgAbuseName: Internet Corporation for Assigned Names and Number\nOrgAbusePhone: +1-310-301-5820\nOrgAbuseEmail: abuse@iana.org\n\nOrgTechHandle: IANA-IP-ARIN\nOrgTechName: Internet Corporation for Assigned Names and Number\nOrgTechPhone: +1-310-301-5820\nOrgTechEmail: abuse@iana.org\n\n# ARIN WHOIS database, last updated 2005-10-18 19:10\n# Enter ? for additional hints on searching ARIN's WHOIS database. -YendorMike "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759 Historical Review of Pennsylvania
Post #230,090 by Steve Lowe 10/19/05 3:28:09 PM 10/19/05 3:30:10 PM Reply	Isn't that somewhat deprecated now? I thought the concepts of class A, B, and C networks were deprecated in favor of CIDR. Using subnetting like he wants to with a 192.168.x.x (formerly class C internal) should work in that case. If not, then changing to a 172.[16-31].x.x (formerly class B internal) network would work, or sticking the router in between would do it. I'd attempt the proposed solution then switch to the 172 network as a contingency. edit: fixed misspeeling in sujbect -- Steve [link\|http://www.ubuntulinux.org\|Ubuntu] Edited by Steve Lowe Oct. 19, 2005, 03:30:10 PM EDT Expand All History
Post #230,093 by andread 10/19/05 3:38:53 PM Reply	Re: Isn't that somewhat deprecated now? That was my general understanding gotta like a guy who agrees with me I'll try it on Friday (network shutdown is already announced) and will post the results A Play I Some Music w/ Papa Andy Saturday 8 PM - 11 PM ET All Night Rewind 11 PM - 5 PM Reggae, African and Caribbean Music [link\|http://wxxe.org\|Tune In]
Post #230,105 by folkert 10/19/05 4:25:57 PM Reply	You realize... CIDR makes a network mask of anything a doable. (well except your subnet mask == fish or something) you want a /23 CIDR network. (255.255.255.254.0 is th old stle associated with Class A B C stuff) 512 addresses total 510 usable. Unless you have very bad ethernet "shared" hubs and have ZERO switches... you should be alraight. Especially now a days with GigE uplinks and so on. Old Netw-orking stuffs: 192.168.3.0 == network 192.168.3.255 == broadcast 255.255.255.0 == netmask 192.168.3.1 == default gateway New netw-orking stuffs: 192.168.2.0 == network 192.168.3.255 == broadcast 255.255.254.0 == netmask 192.168.3.1 == default gateway Eventually everything will be on the new stuff. Just make sure you change the servers and routers manually to the new netmask. It'll be a bit weird, but only for a bit. And BTW, this will work despite what others tell you. It is never mentioned, mainly because it is messy to explain why it will work. The only reall thing you need to make sure happens is the default route stays the same value. Variable netmasks on the same network is supported by most networking gear made since CIDR has been around. The only downside, is it'll be a bit chatty for a while. Most everything else will correct themselves within a short time. The thing about it is, change the DHCP server conf. Don't revoke the leases. Let them renew, or when Windows reboots (as seldom as that happens... ) as long as the DHCP server is responding... you are good to go. One last thing, if the servers are on the 192.168.3 netowrk right now... do not put them on the 192.168.2 network until everything is settled. -- [link\|mailto:greg@gregfolkert.net\|greg], [link\|http://www.iwethey.org/ed_curry\|REMEMBER ED CURRY!] @ *i_wethey* Freedom is not FREE. Yeah, but 10s of Trillions of US Dollars? SELECT * FROM scog WHERE ethics > 0; 0 rows returned.
Post #230,106 by andread 10/19/05 4:33:32 PM Reply	Re: You realize... thanks for the message Actually, one of the major points of doing this was to avoid changing the IP addresses of the servers each Citrix client needs the IP address of at least one server to find the farm A Play I Some Music w/ Papa Andy Saturday 8 PM - 11 PM ET All Night Rewind 11 PM - 5 PM Reggae, African and Caribbean Music [link\|http://wxxe.org\|Tune In]

Welcome to IWETHEY!