Re: Cannot Use LAN IP Addresses

From: Phillip Windell (_at_.)
Date: 11/19/04

  • Next message: Cyskon: "Re: Cannot Use LAN IP Addresses" 
    Date: Fri, 19 Nov 2004 08:14:31 -0600

    I haven't seen problems with Netbios names,...they usually work. I've only
    seen the problem with using IP#s in the URL instead of the Netbios name or
    FQDN. I though I remembered reading somewhere that the way a name is
    recognized as a FQDN as opposed to a Netbois name is by the fact that the
    FQDN has "dots" in it. since the IP# has "dots" in it, it get falsely
    interpreted to be a FQDN instead of the raw IP#. 

    -- 
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"A.Klimkin" <aklimkin at mail dot ru> wrote in message
news:uS%239D9gzEHA.1392@TK2MSFTNGP14.phx.gbl...
> You're right, Phillip.
> I believe it's a serious bug in firewall client/ISA2004 because there are
> some cases when you're not able to use netbios or dns names in the url
> string (like script-generated urls, for example).
> I think it can be fixed by allowing firewall clients to resolve names by
> their own, rather than by firewall service. But I can't find the
appropriate
> configuration option. Does anyone know if there is some registry value?
>
> Regards,
> Andrew
>
> "Phillip Windell" <@.> wrote in message
> news:eTw7INczEHA.1204@TK2MSFTNGP10.phx.gbl...
> > Ah! I saw this right after I sent my other post,...check it
out....(hehe).
> >
> > It is seeing the "dots" in the IP# and treating it as a FQDN (treats the
> > numbers as if they were letters). It then trys to process it that way
and
> > creates a mess.
> >
> > Keep in mind that *all* FQDNs are *assumed* to be out on the Internet
> until
> > after they are resolved to an IP#,...so they always are proccessed by
the
> > proxying service. Once they are resolved and determined to be on the
> Private
> > side of the LAN the "proxying services" bail out and let it transit to
the
> > destination directly. If it improperly interprets the IP# in the URL to
be
> a
> > FQDN instead,...well the problem becomes obvious.
> >
> > MS Exchange and the IIS SMTP Service will also do this and require that
a
> > raw IP# be enclosed in [  ]  such as, [192.168.1.3] to indicate that
they
> > are simply a raw IP# and not a FQDN. But I doubt that would work with
ISA
> if
> > you did that in the browser's address bar.
> >
> > Unfortunately, I'm not sure what causes it and I have no idea where the
> > problem is happening either to even know what to blame.
> >
> > -- 
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> > "Cyskon" <cyskon@msn.com> wrote in message
> > news:OMqoxjZzEHA.3028@TK2MSFTNGP10.phx.gbl...
> > > I should also let you know that, if I type in the NetBIOS name for the
> > > resource I can get access to it, but NOT via the IP address.
> > >
> > > "Cyskon" <cyskon@msn.com> wrote in message
> > > news:#zeJ$hLzEHA.260@TK2MSFTNGP11.phx.gbl...
> > > > Hello Newsgroup,
> > > >
> > > > Here's my problem. My test workstations that I have installed the
FWC
> on
> > > > cannot access other machines on the network using their IP address.
> > > >
> > > > I have a few web servers within my network that I access at times
> using
> > > the
> > > > local IP address of the machine. Now I am unable to do this.
> > > >
> > > > Can someone tell me why and how to resolve the issue?
> > > >
> > > > Thanks
> > > >
> > > >
> > >
> > >
> >
> >
>
>
  • Next message: Cyskon: "Re: Cannot Use LAN IP Addresses"

    Relevant Pages

    • Re: Name resolution vs. multiple NICs
      ... how exactly do you obtain it from a NetBIOS name? ... All you can physically get is what is FQDN as it appears to ... > with their ISP's domain suffix attached to it, ... > any domain suffix. ...
      (microsoft.public.win32.programmer.networks)
    • Re: Weird Behaviour Accessing MS CA Web Site
      ... I've tried adding FQDN and NETBIOS into intranet ... When you use IP you are forcing that Kerberos not be used. ... is configured to record login failures? ...
      (microsoft.public.windows.server.security)
    • Re: Map the FQDN to a content source issue
      ... This error is usually because of the proxy settings. ... > content sources to the netbios name. ... > pointing the FQDN to the internal IP returns an error in the gatherer log ...
      (microsoft.public.sharepoint.portalserver)
    • Re: Cannot Use LAN IP Addresses
      ... I haven't seen problems with Netbios names,...they usually work. ... recognized as a FQDN as opposed to a Netbois name is by the fact that the ... Phillip Windell www.wandtv.com "A.Klimkin" wrote in message ... >> after they are resolved to an IP#,...so they always are proccessed by the>> proxying service. ...
      (microsoft.public.isaserver)
    • Re: NT4/2K3 DNS Domain Name - Fallback Issues
      ... I think the name is not changed, just the FQDN are added. ... Are you meaning the NetBIOS Name ... >> Microsoft MVP - Directory Services ... >>> If the upgrade is successful in production this would be fine, ...
      (microsoft.public.windows.server.active_directory)
    Loading