Damnit, it was something stupid, the netmask was set to 255.255.0.0 rather than
255.255.255.0. You gotta hate when you overlook something so obvious. Thanks
for the pointer.
Eric W. Cowperthwaite
From: Ric Castagna [SMTP:firstname.lastname@example.org]
Sent: Tuesday, April 14, 1998 10:54 AM
Subject: Re: problems routing to new NT server
If it were me, I'd start at the really stupid stuff...
1) Does the new server see all of the other machines on the network/domain?
2) Is the subnet mask different on the new machine than on the others? (ie.
new one => 255.255.255.0 rest of network => 255.255.255.192)
3) Is the IP address correct in the new machine?
4) Is it looking to be authenticated and become a member of the same domain
that the dial-up users do?
Those would be the easiest places to look at...
At 09:50 AM 4/14/98 -0700, you wrote:
>I have implemented a new NT server for RADIUS and POP3/SMTP services.
>My dial-in customers and non-routed ISDN customers can see the new
>server just fine. However my routed ISDN customers cannot see the
>server at all. My Portmaster3 authenticates to the server just fine. So the
>problem is not that the remote access hardware can't see the server. This
>server is inside the same network segment as all my other servers and my
>routed ISDN customers can see the other servers. My assumption is that
>the new server is where the problem is at. (it is the only new hardware in
>The server is running the following services and protocols:
>RIP for Internet Protocol
>My network uses the following equipment:
>Cisco 2500 series router (gateway router)
>Livingston PM3 (remote access router)
>Intel Pentium II servers running NT 4.0/IIS 4.0/RadiusNT/Post.Office
>Any ideas? Anyone had this problem before?
>Eric W. Cowperthwaite
NTISP Mailing List email@example.com