connection refused!!!!

[defsrg]

i had my turbonet card up and running well using my NICS and a crossover cable. then i installed a dsl router for multiple dsl use in the home. unhappy with the speed of extracting with the router i installed another nics card to use my crossover cable again now i get connection reufsed in both teraterm and telnet from the c prompt. i used the standard ip address of 192.168.1.100.subnet 255.255.255.0 gateway of 192.168.1.1. i can ping the tivo and i can get bash from my serial cable but my ip refuses the connection. any ideas cuz i have seen multiple posts dealing with similiar things some are easy some aren't so i would like to do the right thing from the start. i hope it is just as easy as putting a 23 at the end of my addy in the rc.remote-login.please let me know and thanx!!!

[BubbleLamp]

You probably didn't assign an IP address to the other NIC. The one that's connected to the router may be 192.168.1.100, but the one directly connected via the cross-over cable won't/can't be. So you have to put it on a different network, and change the Tivo to match it.

[defsrg]

no i dont think so LAC #3 is the first nics card with static ip addy of 192.168.1.102, LAC #4 which is the new nics card is the standard tivo 192.168.1.100. so im still stuck

[BubbleLamp]

Originally posted by defsrg
no i dont think so LAC #3 is the first nics card with static ip addy of 192.168.1.102, LAC #4 which is the new nics card is the standard tivo 192.168.1.100. so im still stuck

You can't have two NICs on the same network number, which is what you have. The PC doesn't know where to send the data. You MUST change the network number on one of them. Make it 192.168.2.100 and the Tivo 192.168.2.xxx.

[zabs]

Originally posted by BubbleLamp
You can't have two NICs on the same network number, which is what you have. The PC doesn't know where to send the data. You MUST change the network number on one of them. Make it 192.168.2.100 and the Tivo 192.168.2.xxx.

To be completely fair the part about two nics on the same network is not entirely true. You could have two nics on the same Class C set of IP's, but the subnets would have be different.
Ie. you could have one NIC handle 192.168.1.0-127 and another nic handle 192.168.1.128-255.

Then again I have only ever done something like this in Linux. I'm pretty sure it could be done in windows, but it is probably best to take BL's advice and keep it simple.

[zabs]

Possibly check out the "route" command in windows.......you could setup a default route to your tivo's address for the NIC that is linked to it via the crossover cable. Just another possibility.

You know it may also be a good idea to look into a better Hub or personally I prefer a nice Switch, then you wouldn't have to deal with another nic in the windows box. A nice 8 port "smart switch" can be obtained for under 50$ on most days.

[BubbleLamp]

Originally posted by zabs
To be completely fair the part about two nics on the same network is not entirely true. You could have two nics on the same Class C set of IP's, but the subnets would have be different.
Ie. you could have one NIC handle 192.168.1.0-127 and another nic handle 192.168.1.128-255.

Then again I have only ever done something like this in Linux. I'm pretty sure it could be done in windows, but it is probably best to take BL's advice and keep it simple.

Windows has no way of doing it with NetBIOS, it's braindead. It can be done with NetBT and TCP/IP with some assistance (3rd party software to create load sharing/failover protection). This for NT4 and up, not Win3x/98.

And yes, I'm aware of the subnetting possibilities, but I really ain't about to go down that rat trap here. If you wish to hand-hold through the explanation of mask bits and class designations, have at it.:eek:

[zabs]

Originally posted by zabs
....but it is probably best to take BL's advice and keep it simple.

I certainly meant no offense (I hope none was taken.) I guess I was just pointing out the possibilities. Your way would certainly be the easiest.

[defsrg]

sorry fellas didnt mean to start an arguement. bubblelamp yes i agree your way is easiest just want to be sure this is whta i am going to do:
1) set nics card ip to 192.168.2.99
2) set tivo ip to 192.168.2.100
3) subnet mask 255.255.255.0
4) gateway stays the same? not sure currently at 192.168.1.1
would i have to change this to 192.168.2.1?? like i said just want to be sure dont want to screw anything up furthur.
thanx to both your input guys

[defsrg]

this is my rc.remote-login :
ifconfig net0 192.168.2.100 netmask 255.255.255.0
route.tivonet delete default 2> /dev/null
route.tivonet add default gw 192.168.1.1 netmask 0.0.0.0 dev net0

#!/bin/bash
echo "Starting Telnet"
tnlited 23 /bin/bash -login &

echo "Starting fixdemo"
if [ -e /tvbin/fixdemo.tcl ]; then
/tvbin/fixdemo.tcl >> /dev/null &
fi

echo "Starting TiVoWeb"
if [ -e /tivoweb-tcl/httpd-tt.tcl ]; then
/tivoweb-tcl/httpd-tt.tcl >> /dev/null &
fi

echo "Starting TiVoFTPD"
if [ -e /tivo-bin/tivoftpd ]; then
/tivo-bin/tivoftpd >> /dev/null &
fi

echo "Starting SMBFS"
if [ -e /lib/modules/smbfs.o ]; then
insmod -f /lib/modules/smbfs.o
fi

echo "Starting NFS"
if [ -e /lib/modules/nfs.o ]; then
insmod -f /lib/modules/nfs.o
fi

echo "Enabling Showcases"
if [ -e /tvbin/sc.tcl ]; then
/tvbin/sc.tcl &
fi

echo "Unscrambling"
if [ -e /lib/modules/noscramble.o ]; then
insmod -f /lib/modules/noscramble.o
fi

echo "Remounting / ReadOnly"
mount -o remount,ro /

echo "Starting fixsub"
if [ -e /etc/SubTest ]; then
if [ -x /tvbin/fixsub.tcl ]; then
/tvbin/fixsub.tcl &
fi
fi

[BubbleLamp]

Originally posted by defsrg
sorry fellas didnt mean to start an arguement. bubblelamp yes i agree your way is easiest just want to be sure this is whta i am going to do:
1) set nics card ip to 192.168.2.99
2) set tivo ip to 192.168.2.100
3) subnet mask 255.255.255.0
4) gateway stays the same? not sure currently at 192.168.1.1
would i have to change this to 192.168.2.1?? like i said just want to be sure dont want to screw anything up furthur.
thanx to both your input guys

The gateway address has to be that of your NIC connected to the Tivo, so 192.168.2.99. Keep in mind this means your Tivo can't "phone home" over the Internet. Hope you didn't need that.

[defsrg]

no didn't need it to phone home but i think i screwed it up anyways. i sz'd the rc.remote-login to textpad to modify it. then i went "rm /etc/rc.d/rc.remote-login" ,w/o the quotes of course,to remove the current one in the file. i went " cd / enter" " rz" sent the new rc.remotelogin to the tivo,but now when i go to bring it up, like for example if i was going to edit it,joe /etc/rc.d/rc.remote-login, the file is blank and it says new file.
1) did i do the wrong thing by sending it to the root directory?
2) should it have gone to the /var/hack dir.?
3)i sent it in binary form using the z modem and tera term, should it have not have been binary? please help i have never screwed up like this b4, dont want to have to do a new 25xtreme and lose my recorded programs. thanx

[BubbleLamp]

Originally posted by defsrg
no didn't need it to phone home but i think i screwed it up anyways. i sz'd the rc.remote-login to textpad to modify it. then i went "rm /etc/rc.d/rc.remote-login" ,w/o the quotes of course,to remove the current one in the file. i went " cd / enter" " rz" sent the new rc.remotelogin to the tivo,but now when i go to bring it up, like for example if i was going to edit it,joe /etc/rc.d/rc.remote-login, the file is blank and it says new file.
1) did i do the wrong thing by sending it to the root directory?
2) should it have gone to the /var/hack dir.?
3)i sent it in binary form using the z modem and tera term, should it have not have been binary? please help i have never screwed up like this b4, dont want to have to do a new 25xtreme and lose my recorded programs. thanx

So login, and type ls / and see if the file is there. If so, then type

mv /rc.remote-login /etc/rc.d/rc.remote-login
chmod +x /etc/rc.d/rc.remote-login

[defsrg]

thanx bubble forgot i had to make the file execute thats ok now with the rc.remote-login but even after all teh changes i still get connection refused. heres where i stand as im about to do some more reading
under network settings on the nics card:
IP address: 192.168.2.100
subnet: 255.255.255.0
default gateway: 192.168.2.99
heres my rc-remote login:
ifconfig net0 192.168.2.100 netmask 255.255.255.0
route.tivonet delete default 2> /dev/null
route.tivonet add default gw 192.168.2.99 netmask 255.255.255.0 dev net0

#!/bin/bash
echo "Starting Telnet"
tnlited 23 /bin/bash -login &

echo "Starting fixdemo"
if [ -e /tvbin/fixdemo.tcl ]; then
/tvbin/fixdemo.tcl >> /dev/null &
fi

echo "Starting TiVoWeb"
if [ -e /tivoweb-tcl/httpd-tt.tcl ]; then
/tivoweb-tcl/httpd-tt.tcl >> /dev/null &
fi

echo "Starting TiVoFTPD"
if [ -e /tivo-bin/tivoftpd ]; then
/tivo-bin/tivoftpd >> /dev/null &
fi

echo "Starting SMBFS"
if [ -e /lib/modules/smbfs.o ]; then
insmod -f /lib/modules/smbfs.o
fi

echo "Starting NFS"
if [ -e /lib/modules/nfs.o ]; then
insmod -f /lib/modules/nfs.o
fi

echo "Enabling Showcases"
if [ -e /tvbin/sc.tcl ]; then
/tvbin/sc.tcl &
fi

echo "Unscrambling"
if [ -e /lib/modules/noscramble.o ]; then
insmod -f /lib/modules/noscramble.o
fi

echo "Remounting / ReadOnly"
mount -o remount,ro /

echo "Starting fixsub"
if [ -e /etc/SubTest ]; then
if [ -x /tvbin/fixsub.tcl ]; then
/tvbin/fixsub.tcl &
fi
fi
andthis are the lines from my rc.sysinit no expert but this doesnt look right

if /sbin/ifconfig eth0 hw ether $mac $ipaddr || [ "$tnforce" = true ] ; then
PATH=/bin:/sbin:/tvbin:/devbin
export PATH
echo "Starting network ..."
gw=`getprom -gateway`
if [ ! $gw = 0.0.0.0 ]; then
route add -net 192.168.0.0 gw $gw netmask 255.255.0.0
fi

export TMK_DEBUGGER=sleep
export DEBUG_BOARD=true
echo "Starting Telnet Listener..."
if [ -x /bin/bash ] ; then
tnlited 23 /bin/bash -login &
else
export TIVOSH_POOLSIZE=800000
tnlited 23 /tvbin/tivosh -login &
fi

echo "Starting /proc Listener..."
procd

# if [ -x /sbin/thttpd ]
# then
# echo "Starting http daemon..."
# thttpd
# ifconfig lo up
# fi
fi
sorry man im not much with networking but ill keep at it with the reading cuz from what i have read so far this should be working.
thanx
ps yes i can ping it

[defsrg]

i cant get this what so ever so i think im gonna try a kraven uninstall then reinstall see what happens

[BubbleLamp]

Originally posted by defsrg
i cant get this what so ever so i think im gonna try a kraven uninstall then reinstall see what happens

If you can ping it, then try going in over serial port and typing ps aux to see if the telnet daemon (tnlited) is running.

If not, then try to load it manually from bash

tnlited 23 /bin/bash -login &

If that doesn't work, you've some work to do tracking down why.

[defsrg]

yeah its there in the ps aux right below MfsDaemon. so im lost im not that good at tracking things down i would probaly be better off just doing an uninstall on Kraven and starting from scratch.

[BubbleLamp]

This is wrong

route add -net 192.168.0.0 gw $gw netmask 255.255.0.0

Having that in rc.sysinit is wiping out what you have in rc.remote-login. Furthermore, if the rest of your network is subnetted with 255.255.255.0, then this mask would have to match as well.

You can either remove this line altogether (recommended), or change it to

route add -net 192.168.2.0 gw $gw netmask 255.255.255.0

Wat do you see if you type ifconfig?

[defsrg]

bash-2.02# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0

net0 Link encap:Ethernet HWaddr 00:0B:AD:23:70:D4
inet addr:192.168.2.100 Bcast:192.168.2.255Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Interrupt:29
this is what i get ,while your looking im gonna change that rc.sysinit

[defsrg]

i have no idea how that smiley face got there it should be
70:D4 lol
what the???? its capital d
hey something else too bubble
this is what i get doing an ls on my /etc/rc.d directory
finishinstall.tcl rc.net rc.sysinit
init.d rc.remote-login rc.sysinit.bak
rc.arch rc.remote-login~ rc.sysinit~


the ~ actually sets a little higher on the last letter like even with the top

[BubbleLamp]

Originally posted by defsrg
bash-2.02# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0

net0 Link encap:Ethernet HWaddr 00:0B:AD:23:70:D4
inet addr:192.168.2.100 Bcast:192.168.2.255Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Interrupt:29
this is what i get ,while your looking im gonna change that rc.sysinit

Wrong command. Try this route.tivo -n and see what it shows.

[defsrg]

um not to seem brain dead but add the lines to rc.remote-login or rc.sysinit??

[BubbleLamp]

Originally posted by defsrg
um not to seem brain dead but add the lines to rc.remote-login or rc.sysinit??

Re-read my post, I screwed up on the command to show the routes!

[defsrg]

i get this lovely message:
bash: route.tivo: command not found

[BubbleLamp]

Originally posted by defsrg
i get this lovely message:
bash: route.tivo: command not found

Ok, just try route instead.

[defsrg]

k here it is doesnt look good from my little bit of knowledge that i have:
route_info, afname=inet, options=33
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
Illegal Instruction

[BubbleLamp]

Originally posted by defsrg
k here it is doesnt look good from my little bit of knowledge that i have:
route_info, afname=inet, options=33
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
Illegal Instruction

Ugg. I meant route, but you still need to use the -n on it.

Should look like this:

[/var/tmp]$ route -n
route_info, afname=inet, options=37
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
111.111.0.0 0.0.0.0 255.255.0.0 U 32767 0 0 net0
0.0.0.0 111.111.111.149 0.0.0.0 UG 0 0 0 net0
[/var/tmp]$

[defsrg]

here's mine net0 are on thesame line in the tivo just wouldnt fit right here
route_info, afname=inet, options=37
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.2.99 255.255.0.0 UG 0 0 0 net 0
192.168.2.0 0.0.0.0 255.255.0.0 U 32767 0 0 net0

[BubbleLamp]

Originally posted by defsrg
here's mine net0 are on thesame line in the tivo just wouldnt fit right here
route_info, afname=inet, options=37
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.2.99 255.255.0.0 UG 0 0 0 net 0
192.168.2.0 0.0.0.0 255.255.0.0 U 32767 0 0 net0

Three things wrong here. On the top and bottom lines, the mask should be 255.255.255.0. On the bottom line, the Iface should be that of your Tivo, which is 192.168.2.100.

Type these two lines manually,

route delete default 2> /dev/null
route add default gw 192.168.2.99 netmask 255.255.255.0 dev net0

then type route -n again and see if it looks right. If so, then try to telnet in. If that works, then do this:

cp /sbin/route /sbin/route.tivo

Now reboot, and run route.tivo -n and confirm they are still correct. If so, send a cold sixpack. then see if you can telnet.:D

[defsrg]

k bubble it fixed the genmask to 255.255.255.0, but the iface is still showing 192.168.2.0 not the 198.168.2.100 like its suppose to, so im still getting a connection refused. thanx

[BubbleLamp]

Originally posted by defsrg
k bubble it fixed the genmask to 255.255.255.0, but the iface is still showing 192.168.2.0 not the 198.168.2.100 like its suppose to, so im still getting a connection refused. thanx

Then you need to triple check the file where the IP address and default gateway are being assigned, and make SURE they are correct. After that, I'm gonna have to bow out.

[defsrg]

This is wrong



code:--------------------------------------------------------------------------------route add -net 192.168.0.0 gw $gw netmask 255.255.0.0--------------------------------------------------------------------------------


Having that in rc.sysinit is wiping out what you have in rc.remote-login. Furthermore, if the rest of your network is subnetted with 255.255.255.0, then this mask would have to match as well.

You can either remove this line altogether (recommended), or change it to


code:--------------------------------------------------------------------------------route add -net 192.168.2.0 gw $gw netmask 255.255.255.0--------------------------------------------------------------------------------


Wat do you see if you type ifconfig?
not for nothing but if i changed theline in the rc.sysinit like you said in this post shouldnt' i have changed it to 192.168.2.100 and not 192.168.2.0 like you said in the above post?or maybe 192.168.2.99 which is my gateway???
and i really appreciate everything that u have done!!! thanx

[BubbleLamp]

Originally posted by defsrg
This is wrong



code:--------------------------------------------------------------------------------route add -net 192.168.0.0 gw $gw netmask 255.255.0.0--------------------------------------------------------------------------------


Having that in rc.sysinit is wiping out what you have in rc.remote-login. Furthermore, if the rest of your network is subnetted with 255.255.255.0, then this mask would have to match as well.

You can either remove this line altogether (recommended), or change it to


code:--------------------------------------------------------------------------------route add -net 192.168.2.0 gw $gw netmask 255.255.255.0--------------------------------------------------------------------------------


Wat do you see if you type ifconfig?
not for nothing but if i changed theline in the rc.sysinit like you said in this post shouldnt' i have changed it to 192.168.2.100 and not 192.168.2.0 like you said in the above post?or maybe 192.168.2.99 which is my gateway???
and i really appreciate everything that u have done!!! thanx

The line in rc.sysinit shouldn't affect the net0 interface, but maybe the route command is still messing things up. Comment out the route statement in rc.sysinit with #.

#echo "Starting network ..."
#gw=`getprom -gateway`
#if [ ! $gw = 0.0.0.0 ]; then
#route add -net 192.168.0.0 gw $gw netmask 255.255.0.0

[defsrg]

i am going to post both my rc.sysinit's that i have. the first is the that is located in the /var/hack directory. i hope some can see something i'm not as my head is very sore from hitting my desk.

[defsrg]

and this one is from my /etc/rc.d directory. now mind u in thsi directory there is also a rc.sysinit~ and a rc.sysinit.bak.
i know its titled rc1.sysinit but thats just the default form downloading both of them to the same file location. a very big special thanx goes out to bubblelamp who has tried very hard to help me fix this!! thanx bro!!
and this might be an issue too,
ifconfig net0 192.168.2.100 netmask 255.255.255.0

I get this :
bash-2.02# ifconfig net0 192.168.2.100 netmask 255.255.255.0
IP struct was not filled in!
sa is: 0x20000 0xc0a80264 0x7ffffbf4 0x7ffffc0c
sa.sin_addr = 0x7ffffb58 a sockaddr is 16 bytes

[BubbleLamp]

Do me a favor and zip up the following files and post them here. They are all in /etc/rc.d

rc.sysinit
rc.arch
rc.net
rc.remote-login

Also, do an ls -l /sbin/ro* and tell me what's there.

[defsrg]

here u go man

[defsrg]

oh sorry and this from the other thing u wanted

-rwxr-xr-x 1 0 0 37024 aug 24 2001 /sbin/route
-rwxr-xr-x 1 0 0 37024 jan 4 16:33 /sbin/ route.tivo
-rwxr-xr-x 1 501 501 37024 jan 4 15:54 /sbin/route.tivonet

[BubbleLamp]

Ok, that helps. I've got to run out for a few hours, but should have some ideas for you when I get back. I'm pretty sure I know what's up now. Since I've never used Kraven's update myself, I just have to work through his scripts.

[defsrg]

i think i see wht your seeing but im gonna wait just in case. just so u know that's all new i did a fresh reinstall of kraven last night however still have the same problem. however this time i did not recreate my /var/hack directory like i did with the first kraven install. its funnny how my rc.arch looks alot like the section out of my rc.sysinit i posted from the hack directory a couple of days ago. i may be wrong but ill wait to hear from you.
for those of following this great saga i am referring to this...
This is wrong



code:--------------------------------------------------------------------------------route add -net 192.168.0.0 gw $gw netmask 255.255.0.0--------------------------------------------------------------------------------


Having that in rc.sysinit is wiping out what you have in rc.remote-login. Furthermore, if the rest of your network is subnetted with 255.255.255.0, then this mask would have to match as well.

You can either remove this line altogether (recommended), or change it to


code:--------------------------------------------------------------------------------
like i said that section was in my /var/hack/rc.sysinit and now it sets in my rc.arch after the kraven reinstall
also when i do i route -n i still get my destination as 192.168.2.0 instaed of the 192.168.2.100 likeits suppose to be

[BubbleLamp]

Well let's go back to basics. Here's what I'd like you to do.

For rc.remote-login, delete the stuff in red:
ifconfig net0 192.168.2.100 netmask 255.255.255.0
route.tivonet delete default 2> /dev/null
route.tivonet add default gw 192.168.2.99 netmask 255.255.255.0 dev net0

For rc.net, comment out the stuff shown by adding the red #:
if [ "$DEBUG_BOARD" != true -o "$dhcp" == true ]; then
if detectDynamicNet; then
# mkdir -p /var/state/dhcp
# /sbin/dhclient -q "$DYNAMIC_NET_DEV" 2>/dev/null &
fi
fi

Reboot after making these changes. Type ifconfig net0 and see if it looks like this:
[/var/tmp]$ ifconfig net0
net0 Link encap:Ethernet HWaddr 00:0B:AD:01:23:45
inet addr:192.168.2.100 Bcast:192.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1938 errors:0 dropped:0 overruns:0 frame:0
TX packets:1116 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Interrupt:29

[/var/tmp]$

Type ifconfig eth0 and make sure it shows this:
[/var/tmp]$ ifconfig eth0
eth0: unknown interface.
[/var/tmp]$


Then type route.tivo -n, make sure you see:
[/var/tmp]$ route.tivo -n
route_info, afname=inet, options=37
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 32767 0 0 net0
0.0.0.0 192.168.2.99 0.0.0.0 UG 0 0 0 net0
[/var/tmp]$

If that still doesn't work, junk Kraven's stuff and do it manually. ;)

Lemme know.

BTW, the rc files in /var/hack aren't used.

[defsrg]

um my net0 is like gone now dude i get net0 unknown interface and when i type ifconfig i just get the display for the lo nothing for the net0 its like i wiped it out.

[BubbleLamp]

Originally posted by defsrg
um my net0 is like gone now dude i get net0 unknown interface and when i type ifconfig i just get the display for the lo nothing for the net0 its like i wiped it out.

More details please. What do you see if you type ifconfig eth0? What do you see when you type route -n?

[defsrg]

same thing as on the first man "eth0:unknown interface" and route -n just shows the columns titles no numbers like this:
Kernel IP routing table
destination gateway Genmask etc... etc......
all my kraven directories are in the /root dir. am i reallly gonna do any harm by deleting them all and trying one more time from scratch?

[BubbleLamp]

Originally posted by defsrg
same thing as on the first man "eth0:unknown interface" and route -n just shows the columns titles no numbers like this:
Kernel IP routing table
destination gateway Genmask etc... etc......
all my kraven directories are in the /root dir. am i reallly gonna do any harm by deleting them all and trying one more time from scratch?

Well I could do a bunch more tests if I had it here, just so I could get to the bottom of it. But this has dragged on long enough. My bet is you are using the newer version of the driver, which is not hardcoded for net0, but I can't be sure. When you reinstall, add -u to the cpio command line options to force it to overwrite the files that already exist.

[defsrg]

i understand bl and thanx for the help but i am going to keep posting my results in the effort to help someone in the future.
when i do this
For rc.net, comment out the stuff shown by adding the red #:

code:--------------------------------------------------------------------------------if [ "$DEBUG_BOARD" != true -o "$dhcp" == true ]; then
if detectDynamicNet; then
# mkdir -p /var/state/dhcp
# /sbin/dhclient -q "$DYNAMIC_NET_DEV" 2>/dev/null &
fi
fi
thats when i get this
Type ifconfig net0 and see if it looks like this:
um my net0 is like gone now dude i get net0 unknown interface and when i type ifconfig i just get the display for the lo nothing for the net0 its like i wiped it out
so i took the # back off and everything looks the way it should but still same connection refused!!!! i will fix this i swear!!
if kraven is reading this,any ideas would be much appreciated!!!!

[defsrg]

just an update cannot get ,#401 to work says call failed,cannot get it to make a test call with or w/o the ,#401 prefix however is seems to be making its daily calls. back to work

[defsrg]

just so everyone knows i ended up rextreming and lost all my programs to get back to normal sorry wish i had better news!!