Okay, maybe I was being too simplistic. It's not really
an "invalid" IP range, it's a "reserved" IP address range: the
whole range of 169.254.0.0/16 is what a network interface card
will give *itself* when a DHCP request fails. Usually, a DHCP
lease will include not just an IP address, but default gateway
info, and maybe even DNS info as well. Additionally, some aspects
of how your OS deals with "reserved IP address" might not be
normal. So if your network interface card fails on DHCP...I'm
not wholly confident that anything about that interface will
work correctly. That's all I was saying.
You can set a static IP address in the Network Control
panel. Open TCP/IP properties for your ethernet interface, turn
off "get IP address automatically" and fill in something static
(eg, 192.168.0.1, mask 255.255.255.0 for one machine, 192.168.0.2,
mask 255.255.255.0 for the other).
Hope this helps!
-Scott
On Thu, 20 Feb 2003, Pedro Goncalves wrote:
> Scott,
>
> Thank you very much for the reply.
> Tell me, why isn't 169.254.x.x a valid IP address range? It is
> dynamically attributed and I've got only 2 computers connected. No
> Internet connections.
>
> Anyway, how do you configure/set your IP? Is it with winipcfg in
> win98? It doesn't seem to let me do it... Maybe Control Panel/Network ?
>
> Pedro Goncalves
>
> On Wed, 19 Feb 2003, Scott C. Best wrote:
>
> > Pedro:
> >
> > Heya. I think you may have a simple problem: the IP
> > address range "169.254.x.x" isn't a valid IP address range, so
> > your PC might be refusing to initiate a connection to it. This
> > address range is what you'll get when a DHCP lease request fails.
> > The legit "private IP" ranges are:
> >
> > 10.0.0.0 -- 10.255.255.255
> > 172.16.0.0 -- 172.31.255.255
> > 192.168.0.0 -- 192.168.255.255
> >
> > In general, the 192.168.x.y range is the most popular.
> > Try giving your 2 PC's their own static IP address in that range.
> > Or, alternatively, replace your Ethernet hub with an Ethernet
> > router that has a DHCP server built-in.
> >
> > Good luck!
> >
> > -Scott
> >
> > > Hi.
> > > My problem seems simple. I've got two computers connected directly
> > > (ethernet) and I use 169.254.x.x IP scheme.
> > > I'd like to access services in the WIN98 computer from the WinXP
> > > one - server in win98 and client in XP.
> > > The problem is this persistent "Failed to Connect to Server" which
> > > I can't get fixed.
> > > I've already tried pinging both computers from the other and
> > > everything seems fine. Telnet through port 5900 doesn't seem to
> > > work. What else am I missing here?
> > >
> > > Thanks in advance,
> > >
> > > Pedro Goncalves
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
