Running out of IP Addresses 1

[mishbaker]

I have begun to receive the Event Log Warning that my current Subnet is running low on IP Addresses to hand out. I've looked at SuperScoping and Supernetting. I think Superscope looks like what I want so I've tried to set it up.

I created a superscope and put my 192.168.2.0 and 192.168.3.0 scopes within it. I've added the ip addresses to my NIC (server IP's are now 192.168.2.101 and 192.168.3.101). The gateway (router) is 192.168.2.1 and 192.168.3.1.

Problem. When I try to access shares from a 3.xxx client on a 2.xxx client it says I cannot connect. (And vice versa). I can ping those computers by name and IP Address successfully.

I can connect to internet on them and access shares on the servers (2.1 and 3.1), just not clients.

I'm sure I missed a step or something somewhere along the line. All computers are on the same physical LAN.

All lessons learned from the School of Hard Knocks........at least tuition is cheap.

 

[mishbaker]

Ok....I would like to start off this post by apologizing to everyone who has spent any time helping me. I am Sorry!

The server I'm working on right now just came online to replace our old Windows 2000 server (which was on it's very last leg). I had alot of problems with the 2k to 2k3 switchover because of the issues on the old 2000 server. It wouldn't transfer roles and all kinds of things. Apparently it also infested itself in my DHCP Authorized Servers.

I had to use ADSIedit to remove the old server and now everything works fine. Again, I am VERY sorry. Thank you all for your help, feel free to verbally/typographically abuse me.

Serbtastic, I was running the results of your last post when it just hit me like a ton of bricks to check that.

Thanks alot to WhoKilled Kenny as well. You guys really helped me alot in understanding this whole ordeal.

All lessons learned from the School of Hard Knocks........at least tuition is cheap.

 

[Serbtastic]

Can you at least post the results of the test for me? I'm dying to know the answer, and I don't feel like setting it up in my test environment.

Thanks.

 

[WhoKilledKenny]

Glad to hear you resolved the issue....

What WhoKilledKenny describes above is not possible. If you can ping and UNC to an address on a different subnet, something has to be routing, it just doesn't work like he describes it.

Serbastic...
Just because two machines have two different IP addresses (192.168.1.x and 192.168.2.x) does not mean that they are physically on separate subnets. Would you not agree that you can possibly misconfigure a workstation with the wrong IP address? Let's say this was the case. In a test I have a single subnet of 10.0.1.x/24 and I place a machine on the physical subnet but purposely set the IP to 10.0.2.202/24. From machine 10.0.1.204/24 I am able to ping 10.0.2.202 and I am able to \\10.0.2.202, because SMB is a broadcast and all clients on the same wire (including 10.0.2.202) will hear that broadcast.

For the reasons of sanity I tested this and from 10.0.1.204, I was able to PING and UNC to 10.0.2.202. If you doubt me, please test for yourself...

 

[mishbaker]

The Trace Route from 192.168.3.111 using the command tracert 192.168.2.125 was:

Tracing Route to olrit.arsc [192.168.2.125] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms olrit.arsc[192.168.2.125]

Trace Complete.

I got an error message when using the name.

All lessons learned from the School of Hard Knocks........at least tuition is cheap.