I understand now. And what you describe for a delay is
what I have been doing. I don't know if you saw the my
initialization code I posted earlier, it is broken up
into two parts. The first ifconfig is called right
after powerup, it sets a default IP address and
netmask. Then, every 5-seconds it checks pd_havelink
to see if its connected to a network. If it is, then
it either does a DHCP request, or if its in static IP
mode, brings the interface up with the static IP
address.
Steve
--- Dave Moore <dmoore@dmoo...> wrote:
> Steve Trigero wrote:
> > --- Dave Moore <dmoore@dmoo...> wrote:
> >
> >>> On Jan 31, 2005, at 2:17 PM, Steve Trigero
> wrote:
> >>>> I did find one problem with my code. It seems
> that
> >>>> pd_havelink() does not return true when
> connected peer-to-peer.
> >>
> >> It may take a while to negotiate it...stick a
> delay in there.
> >>
> >
> > Stick a delay where?
> >
>
> After the initial sock_init and ifconfig. After you
> start everything up,
> the ethernet chip has to negotiate the physical
> link. The dhcp process may
> be masking that time delay for you. The static ip
> call may be somewhat
> instantaneous. Make your call to ifconfig, delay 3
> secs or so, then check
> pd_havelink. You should also be able to see the
> link light on the rcm3000.
> pd_havelink should be reflecting that status.
>
> If you want, connect both the PC and the rabbit
> using "normal" cables to a
> hub. Then you don't have to worry about the
> cross-over cable maybe causing
> you problems.
Using Static IP mode
Started by ●January 31, 2005
Reply by ●February 1, 20052005-02-01
Reply by ●February 1, 20052005-02-01
Hi, I m new to this product. Can anyone show me how
RC2600Wolf handles multiple-users with same PortNo?
__________________________________
RC2600Wolf handles multiple-users with same PortNo?
__________________________________
Reply by ●February 1, 20052005-02-01
Steve Trigero wrote:
> I understand now. And what you describe for a delay is what I have
> been doing. I don't know if you saw the my initialization code I
> posted earlier, it is broken up into two parts. The first ifconfig is
> called right after powerup, it sets a default IP address and netmask.
> Then, every 5-seconds it checks pd_havelink to see if its connected
> to a network. If it is, then it either does a DHCP request, or if its
> in static IP mode, brings the interface up with the static IP
> address.
>
Maybe take the DHCP stuff out and just do the static to see if the DHCP
mangles the static? Or course, it shouldn't but you're in diagnostic mode.
Do you have the LINK led on the RCM3000? If it's not on, then you might
have a bum cable.
> I understand now. And what you describe for a delay is what I have
> been doing. I don't know if you saw the my initialization code I
> posted earlier, it is broken up into two parts. The first ifconfig is
> called right after powerup, it sets a default IP address and netmask.
> Then, every 5-seconds it checks pd_havelink to see if its connected
> to a network. If it is, then it either does a DHCP request, or if its
> in static IP mode, brings the interface up with the static IP
> address.
>
Maybe take the DHCP stuff out and just do the static to see if the DHCP
mangles the static? Or course, it shouldn't but you're in diagnostic mode.
Do you have the LINK led on the RCM3000? If it's not on, then you might
have a bum cable.
Reply by ●February 1, 20052005-02-01
This is what MSDN says about 10061:
Connection refused.
No connection could be made because the target computer actively refused it.
This usually results from trying to connect to a service that is inactive on
the foreign hostthat is, one with no server application running.
It seems that Rabbit does not listen to the port your WinSock application is
trying to open. Try to open the port (from the PC) using telnet instead,
e.g.
telnet 192.168.100.1 12345
-----Original Message-----
From: Steve [mailto:seecwriter@seec...]
Sent: Monday, January 31, 2005 11:55 AM
To: rabbit-semi@rabb...
Subject: [rabbit-semi] Using Static IP mode
I've got an RCM3000 module configured for ethernet. If I set it to use
DHCP, and connect it to a network server, it works fine. But when I
set it to Static IP mode, set the IP address, and connect it to a PC
directly via a cros-over cable I am unable to connect. The PC is set
to static IP mode as well.
On the PC side I get the following error message:
Error No: 10061
Descr: Connection is forcefully rejected
Scode: -2146818227
Source: C:\Windows\System\MSWINSCK.OCX
I'm not sure if this is a PC issue or a Rabbit issue. Any suggestions?
Steve
Yahoo! Groups Links
Connection refused.
No connection could be made because the target computer actively refused it.
This usually results from trying to connect to a service that is inactive on
the foreign hostthat is, one with no server application running.
It seems that Rabbit does not listen to the port your WinSock application is
trying to open. Try to open the port (from the PC) using telnet instead,
e.g.
telnet 192.168.100.1 12345
-----Original Message-----
From: Steve [mailto:seecwriter@seec...]
Sent: Monday, January 31, 2005 11:55 AM
To: rabbit-semi@rabb...
Subject: [rabbit-semi] Using Static IP mode
I've got an RCM3000 module configured for ethernet. If I set it to use
DHCP, and connect it to a network server, it works fine. But when I
set it to Static IP mode, set the IP address, and connect it to a PC
directly via a cros-over cable I am unable to connect. The PC is set
to static IP mode as well.
On the PC side I get the following error message:
Error No: 10061
Descr: Connection is forcefully rejected
Scode: -2146818227
Source: C:\Windows\System\MSWINSCK.OCX
I'm not sure if this is a PC issue or a Rabbit issue. Any suggestions?
Steve
Yahoo! Groups Links
Reply by ●February 1, 20052005-02-01
It seems that your Rabbit is deaf - can't listen to the port you are
trying
to connect to.
As Bob suggested, a packed sniffer is a must. When you obtain it, make sure
you are isolated from the rest of the world, and use a hub (not a switch)
for interconnect.
-----Original Message-----
From: Steve Trigero [mailto:seecwriter@seec...]
Sent: Monday, January 31, 2005 12:37 PM
To: rabbit-semi@rabb...
Subject: RE: [rabbit-semi] Using Static IP mode
Telnet gives me error message: Could not opa a
connection to 192.168.1
telnet 192.168.100.1 2000
Steve --- George Georgiev <g...@g.ge...> wrote:
> This is what MSDN says about 10061:
> Connection refused.
> No connection could be made because the target
> computer actively refused it.
> This usually results from trying to connect to a
> service that is inactive on
> the foreign hostthat is, one with no server
> application running.
>
> It seems that Rabbit does not listen to the port
> your WinSock application is
> trying to open. Try to open the port (from the PC)
> using telnet instead,
> e.g.
> telnet 192.168.100.1 12345
>
> -----Original Message-----
> From: Steve [mailto:seecwriter@seec...]
> Sent: Monday, January 31, 2005 11:55 AM
> To: rabbit-semi@rabb...
> Subject: [rabbit-semi] Using Static IP mode >
>
> I've got an RCM3000 module configured for ethernet.
> If I set it to use
> DHCP, and connect it to a network server, it works
> fine. But when I
> set it to Static IP mode, set the IP address, and
> connect it to a PC
> directly via a cros-over cable I am unable to
> connect. The PC is set
> to static IP mode as well.
>
> On the PC side I get the following error message:
>
> Error No: 10061
> Descr: Connection is forcefully rejected
> Scode: -2146818227
> Source: C:\Windows\System\MSWINSCK.OCX
>
> I'm not sure if this is a PC issue or a Rabbit
> issue. Any suggestions?
>
> Steve >
>
> Yahoo! Groups Links >
>
Yahoo! Groups Links
to connect to.
As Bob suggested, a packed sniffer is a must. When you obtain it, make sure
you are isolated from the rest of the world, and use a hub (not a switch)
for interconnect.
-----Original Message-----
From: Steve Trigero [mailto:seecwriter@seec...]
Sent: Monday, January 31, 2005 12:37 PM
To: rabbit-semi@rabb...
Subject: RE: [rabbit-semi] Using Static IP mode
Telnet gives me error message: Could not opa a
connection to 192.168.1
telnet 192.168.100.1 2000
Steve --- George Georgiev <g...@g.ge...> wrote:
> This is what MSDN says about 10061:
> Connection refused.
> No connection could be made because the target
> computer actively refused it.
> This usually results from trying to connect to a
> service that is inactive on
> the foreign hostthat is, one with no server
> application running.
>
> It seems that Rabbit does not listen to the port
> your WinSock application is
> trying to open. Try to open the port (from the PC)
> using telnet instead,
> e.g.
> telnet 192.168.100.1 12345
>
> -----Original Message-----
> From: Steve [mailto:seecwriter@seec...]
> Sent: Monday, January 31, 2005 11:55 AM
> To: rabbit-semi@rabb...
> Subject: [rabbit-semi] Using Static IP mode >
>
> I've got an RCM3000 module configured for ethernet.
> If I set it to use
> DHCP, and connect it to a network server, it works
> fine. But when I
> set it to Static IP mode, set the IP address, and
> connect it to a PC
> directly via a cros-over cable I am unable to
> connect. The PC is set
> to static IP mode as well.
>
> On the PC side I get the following error message:
>
> Error No: 10061
> Descr: Connection is forcefully rejected
> Scode: -2146818227
> Source: C:\Windows\System\MSWINSCK.OCX
>
> I'm not sure if this is a PC issue or a Rabbit
> issue. Any suggestions?
>
> Steve >
>
> Yahoo! Groups Links >
>
Yahoo! Groups Links
Reply by ●February 1, 20052005-02-01
Flip the ends of the cable over so you can see the colors of the wires and orient them the same way. On a standard cable, the order of the wire colors will be the same on both connectors. On a x-over cable, several wires will switched around from one connector to the other. Make sure they gave you a x-over cable, don’t trust what they say. The jacket color of the cable has no bearing on what type of cable it is…..
Bob
From: Steve
Trigero
[mailto:s...@yahoo.com]
Sent: Monday, January 31, 2005
11:14 PM
To:
r...@yahoogroups.com
Subject: Re: [rabbit-semi] Using
Static IP mode
The PC and the Rabbit are connected
peer-to-peer,
there is no hub involved. And the cable I'm
using
is
supposed to be a cross-over coble. I asked our
IT
department for a cross-cable and this is what
they
gave me. Its a different color (orange) than all
the
other ethernet cables if seem
around.
And I verified with the debugger that
pd_havelink()
never returned true when connected peer-to-peer.
But
if the cable is wrong...well, that's something
I'll
have to verify tomorrow morning when I get in to
work.
As I mentioned before, if I change the Rabbit
to
operate in DHCP mode, all is well. I can connect
and
communicate with no problem. The only difference
is
the initialization code, specifically, the call
to
ifconfig().
Steve
--- Tom Collins <t...@tomlogic.com>
wrote:
> On Jan 31, 2005, at 2:17 PM, Steve Trigero
wrote:
> > I did find one problem with my
code. It seems
> that
> > pd_havelink() does not return true
when connected
> > peer-to-peer.
>
> It should.
>
> Are you connecting the Rabbit and PC to a hub
and
> getting link lights
> for both?
>
> If you're connecting them directly to
each
other,
> you need to use an
> Ethernet crossover cable (pin 1 to 3 and 2 to
6)?
>
> --
> Tom Collins -
t...@tomlogic.com
> Rabbit Software Developer/Consultant based in
Napa,
>
California
> Info on the Sniffter hand-held Network
Tester:
> http://sniffter.com/
>
>
Reply by ●February 1, 20052005-02-01
Steve,
If you rely on IT guys to configure the stuff for you, pay attention what
they are doing. It is best for your development if you can have isolated
network segment (isolated hub) consisting of just Rabbit, and your target
OCX Win98 PC, and (probably) your development DC workstation with EtherReal
connected. If you cannot afford to live without your DC box connected to
Internet, connect separate network card to your development workstation, and
use this card for Ethereal. Dump Win98 as a development platform (both
Rabbit and Visual Studio), stick to Win2k or XP.
p.p. I just saw Dave Moore giving similar advice.
Regards,
George
-----Original Message-----
From: Steve Trigero [mailto:seecwriter@seec...]
Sent: Monday, January 31, 2005 8:22 PM
To: rabbit-semi@rabb...
Subject: RE: [rabbit-semi] Using Static IP mode
--- Dave Moore <dmoore@dmoo...> wrote:
> > On Jan 31, 2005, at 2:17 PM, Steve Trigero wrote:
> >> I did find one problem with my code. It seems
> that
> >> pd_havelink() does not return true when
> connected peer-to-peer.
>
> It may take a while to negotiate it...stick a delay
> in there.
>
Stick a delay where?
Steve
Yahoo! Groups Links
If you rely on IT guys to configure the stuff for you, pay attention what
they are doing. It is best for your development if you can have isolated
network segment (isolated hub) consisting of just Rabbit, and your target
OCX Win98 PC, and (probably) your development DC workstation with EtherReal
connected. If you cannot afford to live without your DC box connected to
Internet, connect separate network card to your development workstation, and
use this card for Ethereal. Dump Win98 as a development platform (both
Rabbit and Visual Studio), stick to Win2k or XP.
p.p. I just saw Dave Moore giving similar advice.
Regards,
George
-----Original Message-----
From: Steve Trigero [mailto:seecwriter@seec...]
Sent: Monday, January 31, 2005 8:22 PM
To: rabbit-semi@rabb...
Subject: RE: [rabbit-semi] Using Static IP mode
--- Dave Moore <dmoore@dmoo...> wrote:
> > On Jan 31, 2005, at 2:17 PM, Steve Trigero wrote:
> >> I did find one problem with my code. It seems
> that
> >> pd_havelink() does not return true when
> connected peer-to-peer.
>
> It may take a while to negotiate it...stick a delay
> in there.
>
Stick a delay where?
Steve
Yahoo! Groups Links
Reply by ●February 1, 20052005-02-01
That's wise advise. And it turns ou that the cable I
was given was not a cross-over cable as I was told.
So I've jetisoned the direct-connect approach and I'm
using a brand new Netgear hub between the PC and the
Rabbit. I am also using brand new cables, right out of
the bag. The PC shows up on the hub's connection light
but the Rabbit's light is dead. And I still can't
connect or communicate to the Rabbit.
And Ethereal on the PC never captures any packets. So
what does that mean?
Steve --- Bob Hohentanner <bhohentanner@bhoh...> wrote:
> Flip the ends of the cable over so you can see the
> colors of the wires
> and orient them the same way. On a standard cable,
> the order of the wire
> colors will be the same on both connectors. On a
> x-over cable, several
> wires will switched around from one connector to the
> other. Make sure
> they gave you a x-over cable, don't trust what they
> say. The jacket
> color of the cable has no bearing on what type of
> cable it is.....
>
> Bob
>
> ________________________________
>
> From: Steve Trigero [mailto:seecwriter@seec...]
> Sent: Monday, January 31, 2005 11:14 PM
> To: rabbit-semi@rabb...
> Subject: Re: [rabbit-semi] Using Static IP mode
>
> The PC and the Rabbit are connected peer-to-peer,
> there is no hub involved. And the cable I'm using is
> supposed to be a cross-over coble. I asked our IT
> department for a cross-cable and this is what they
> gave me. Its a different color (orange) than all the
> other ethernet cables if seem around.
>
> And I verified with the debugger that pd_havelink()
> never returned true when connected peer-to-peer. But
> if the cable is wrong...well, that's something I'll
> have to verify tomorrow morning when I get in to
> work.
>
> As I mentioned before, if I change the Rabbit to
> operate in DHCP mode, all is well. I can connect and
> communicate with no problem. The only difference is
> the initialization code, specifically, the call to
> ifconfig(). > Steve >
> --- Tom Collins <tom@tom@...> wrote:
>
> > On Jan 31, 2005, at 2:17 PM, Steve Trigero wrote:
> > > I did find one problem with my code. It seems
> > that
> > > pd_havelink() does not return true when
> connected
> > > peer-to-peer.
> >
> > It should.
> >
> > Are you connecting the Rabbit and PC to a hub and
> > getting link lights
> > for both?
> >
> > If you're connecting them directly to each other,
> > you need to use an
> > Ethernet crossover cable (pin 1 to 3 and 2 to 6)?
> >
> > --
> > Tom Collins - tom@tom@...
> > Rabbit Software Developer/Consultant based in
> Napa,
> > California
> > Info on the Sniffter hand-held Network Tester:
> > http://sniffter.com/
> >
> >
> ________________________________
>
> > .
>
was given was not a cross-over cable as I was told.
So I've jetisoned the direct-connect approach and I'm
using a brand new Netgear hub between the PC and the
Rabbit. I am also using brand new cables, right out of
the bag. The PC shows up on the hub's connection light
but the Rabbit's light is dead. And I still can't
connect or communicate to the Rabbit.
And Ethereal on the PC never captures any packets. So
what does that mean?
Steve --- Bob Hohentanner <bhohentanner@bhoh...> wrote:
> Flip the ends of the cable over so you can see the
> colors of the wires
> and orient them the same way. On a standard cable,
> the order of the wire
> colors will be the same on both connectors. On a
> x-over cable, several
> wires will switched around from one connector to the
> other. Make sure
> they gave you a x-over cable, don't trust what they
> say. The jacket
> color of the cable has no bearing on what type of
> cable it is.....
>
> Bob
>
> ________________________________
>
> From: Steve Trigero [mailto:seecwriter@seec...]
> Sent: Monday, January 31, 2005 11:14 PM
> To: rabbit-semi@rabb...
> Subject: Re: [rabbit-semi] Using Static IP mode
>
> The PC and the Rabbit are connected peer-to-peer,
> there is no hub involved. And the cable I'm using is
> supposed to be a cross-over coble. I asked our IT
> department for a cross-cable and this is what they
> gave me. Its a different color (orange) than all the
> other ethernet cables if seem around.
>
> And I verified with the debugger that pd_havelink()
> never returned true when connected peer-to-peer. But
> if the cable is wrong...well, that's something I'll
> have to verify tomorrow morning when I get in to
> work.
>
> As I mentioned before, if I change the Rabbit to
> operate in DHCP mode, all is well. I can connect and
> communicate with no problem. The only difference is
> the initialization code, specifically, the call to
> ifconfig(). > Steve >
> --- Tom Collins <tom@tom@...> wrote:
>
> > On Jan 31, 2005, at 2:17 PM, Steve Trigero wrote:
> > > I did find one problem with my code. It seems
> > that
> > > pd_havelink() does not return true when
> connected
> > > peer-to-peer.
> >
> > It should.
> >
> > Are you connecting the Rabbit and PC to a hub and
> > getting link lights
> > for both?
> >
> > If you're connecting them directly to each other,
> > you need to use an
> > Ethernet crossover cable (pin 1 to 3 and 2 to 6)?
> >
> > --
> > Tom Collins - tom@tom@...
> > Rabbit Software Developer/Consultant based in
> Napa,
> > California
> > Info on the Sniffter hand-held Network Tester:
> > http://sniffter.com/
> >
> >
> ________________________________
>
> > .
>
Reply by ●February 1, 20052005-02-01
My IT guys are asking about the gateway setting in the
Rabbit. They seem to think that this is very important
and that if its not set right no packets would be
processed. I've never touched the gateway setting.
Could that be why Static IP mode is not functioning?
Is there a sample Static IP program I can try? I can't
seem to find one. The one example, static.c, is for a
web server.
Steve
Rabbit. They seem to think that this is very important
and that if its not set right no packets would be
processed. I've never touched the gateway setting.
Could that be why Static IP mode is not functioning?
Is there a sample Static IP program I can try? I can't
seem to find one. The one example, static.c, is for a
web server.
Steve
Reply by ●February 1, 20052005-02-01
Steve,
Now I’m not sure what’s going on, is there any chance you connected the Rabbit to the “Uplink” port on the hub.
The gateway setting shouldn’t have any effect on the basic handshaking between the Rabbit and the hub and the link LED should light at a minimum. It’s almost seems like the Rabbit is not initializing the Ethernet chip correctly and it’s not even trying to connect.
Have you tried one of the basic TCP/IP samples that came with the Rabbit and use static addressing yet?
Bob
From: Steve
Trigero
[mailto:s...@yahoo.com]
Sent: Tuesday, February 01, 2005
12:59 PM
To:
r...@yahoogroups.com
Subject: RE: [rabbit-semi] Using
Static IP mode
That's wise advise. And it turns ou that the cable
I
was given was not a cross-over cable as I was
told.
So I've jetisoned the direct-connect approach
and
I'm
using a brand new Netgear hub between the PC and
the
Rabbit. I am also using brand new cables, right
out of
the bag. The PC shows up on the hub's
connection
light
but the Rabbit's light is dead. And I still
can't
connect or communicate to the
Rabbit.
And Ethereal on the PC never captures any packets.
So
what does that mean?
Steve
--- Bob Hohentanner
<b...@acromag.com> wrote:
> Flip the ends of the cable over so you can
see the
> colors of the wires
> and orient them the same way. On a standard
cable,
> the order of the wire
> colors will be the same on both connectors.
On a
> x-over cable, several
> wires will switched around from one connector
to the
> other. Make sure
> they gave you a x-over cable, don't trust
what they
> say. The jacket
> color of the cable has no bearing on what
type of
> cable it is.....
>
> Bob
>
>
________________________________
>
> From: Steve Trigero
[mailto:s...@yahoo.com]
> Sent: Monday, January 31, 2005 11:14
PM
> To:
r...@yahoogroups.com
> Subject: Re: [rabbit-semi] Using Static IP
mode
>
> The PC and the Rabbit are connected
peer-to-peer,
> there is no hub involved. And the cable
I'm
using is
> supposed to be a cross-over coble. I asked
our IT
> department for a cross-cable and this is what
they
> gave me. Its a different color (orange) than
all the
> other ethernet cables if seem
around.
>
> And I verified with the debugger that
pd_havelink()
> never returned true when connected
peer-to-peer. But
> if the cable is wrong...well, that's
something I'll
> have to verify tomorrow morning when I get in
to
> work.
>
> As I mentioned before, if I change the Rabbit
to
> operate in DHCP mode, all is well. I can
connect and
> communicate with no problem. The only
difference is
> the initialization code, specifically, the
call to
> ifconfig().
>
>
> Steve
>
>
>
> --- Tom Collins <t...@tomlogic.com>
wrote:
>
> > On Jan 31, 2005, at 2:17 PM, Steve
Trigero wrote:
> > > I did find one problem with
my code. It seems
> > that
> > > pd_havelink() does not return
true when
> connected
> > > peer-to-peer.
> >
> > It should.
> >
> > Are you connecting the Rabbit and PC to
a hub and
> > getting link lights
> > for both?
> >
> > If you're connecting them directly
to
each other,
> > you need to use an
> > Ethernet crossover cable (pin 1 to 3 and
2 to 6)?
> >
> > --
> > Tom Collins -
t...@tomlogic.com
> > Rabbit Software Developer/Consultant
based in
> Napa,
> >
California
> > Info on the Sniffter hand-held Network
Tester:
> > http://sniffter.com/
> >
> >
>
>
>
>
________________________________
>
> >
.
>
