Strange Network Issues - Help!?

[cartdan]

I bought my controller long ago, and have been very slow to get it going. My problem originally was connecting to it via the network. Seemed to give me random problems, but I thought I had figured out what I was doing wrong and set the IP address manually and turned off DHCP on the box. Got busy and set it aside until recently.

Found some time and thought I'd get it running, but now as I look back at it, I still have some very strange network issues. Here's is how I have it set up and the issues I'm having, maybe someone can advise me on how to proceed. Any help is appreciated.

I set the BCS to 192.168.1.69 and turned off DHCP. Hooked it on my work network, and was able to access it and control everything. The main work router is 192.168.1.1. I brought it home and hooked it on the network here, where the router has the same IP address. I can't see it via the browser (Firefox) or ping it. Brought it back to work and it is still at the IP address that I had set and it is working fine.

Brought it back home, disconnected my computer (XP) from the main network and hooked up the BCS and that computer to a 4 port hub. Manually set the home computer to 192.168.1.68 so that they should be able to see each other. But, I still can't see the BCS. Can't ping it either. Turned off the windows firewall and the virus software, but I still can't see it.

Not sure how to proceed from here, anyone have any ideas?

Thanks in advance,

- Dan

[ECC]

Hi Dan. Not sure what's going on there.. Can you connect the BCS-460 directly to your computer (with the computer's ip address set to 192.168.1.68)? The 4-port hub shouldn't interfere, but one less thing...

[Sizz]

You may have issues with your tcp routing table. Go to the command prompt ("start menu -> run -> cmd") and then type the following commands and paste the results here.

ipconfig /all
netstat -a
netstat -r

[cartdan]

Interesting - I did manage to hook it up directly last night to the PC and was able to access it. Of course that keeps me from being able to get online and will also keep me from connecting remotely.

I will try the commands at the command prompt tonight when I get home and post those results.

Thanks for the help guys.

- Dan

[mpilchuk]

Interesting - I did manage to hook it up directly last night to the PC and was able to access it. Of course that keeps me from being able to get online and will also keep me from connecting remotely.

I will try the commands at the command prompt tonight when I get home and post those results.

Thanks for the help guys.

- Dan

I purchased a cheap 4 port hub to replace a wireless belkin hub. The cheap hub would not pass the signal to the BCS. Went back to the belkin, worked fine. Some of the stuff I buy for my own use is so cheap it is a wonder that my network works at all. Good luck with this problem.

[cartdan]

type the following commands and paste the results here.
ipconfig /all
netstat -a
netstat -r

Here are the results from typing the above commands from the system in my brewshed that I will be using to control the bcs. (The incoming network cable is going into the Netgear EN104 10baset four port hub and from there to the computer. The BCS is not currently attached):

Windows IP Configuration

Host Name . . . . . . . . . . . . : straighttoale
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)
Physical Address. . . . . . . . . : 00-04-5A-46-5F-F6
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.6
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
63.238.52.2
Lease Obtained. . . . . . . . . . : Tuesday, July 14, 2009 4:14:32 AM
Lease Expires . . . . . . . . . . : Wednesday, July 15, 2009 4:14:32 AM

Active Connections

Proto Local Address Foreign Address State
TCP straighttoale:epmap straighttoale:0 LISTENING
TCP straighttoale:microsoft-ds straighttoale:0 LISTENING
TCP straighttoale:1400 straighttoale:0 LISTENING
TCP straighttoale:3389 straighttoale:0 LISTENING
TCP straighttoale:8001 straighttoale:0 LISTENING
TCP straighttoale:12083 straighttoale:0 LISTENING
TCP straighttoale:14834 straighttoale:0 LISTENING
TCP straighttoale:17984 straighttoale:0 LISTENING
TCP straighttoale:1032 straighttoale:0 LISTENING
TCP straighttoale:1249 localhost:10080 CLOSE_WAIT
TCP straighttoale:1310 localhost:1311 ESTABLISHED
TCP straighttoale:1311 localhost:1310 ESTABLISHED
TCP straighttoale:1314 localhost:1315 ESTABLISHED
TCP straighttoale:1315 localhost:1314 ESTABLISHED
TCP straighttoale:1328 localhost:10080 ESTABLISHED
TCP straighttoale:5000 straighttoale:0 LISTENING
TCP straighttoale:8628 straighttoale:0 LISTENING
TCP straighttoale:10080 straighttoale:0 LISTENING
TCP straighttoale:10080 localhost:1312 TIME_WAIT
TCP straighttoale:10080 localhost:1316 TIME_WAIT
TCP straighttoale:10080 localhost:1328 ESTABLISHED
TCP straighttoale:10080 localhost:1332 TIME_WAIT
TCP straighttoale:10080 localhost:1336 TIME_WAIT
TCP straighttoale:10080 localhost:1338 TIME_WAIT
TCP straighttoale:10080 localhost:1346 TIME_WAIT
TCP straighttoale:10080 localhost:1348 TIME_WAIT
TCP straighttoale:10080 localhost:1350 TIME_WAIT
TCP straighttoale:10080 localhost:1352 TIME_WAIT
TCP straighttoale:10080 localhost:1354 TIME_WAIT
TCP straighttoale:10080 localhost:1356 TIME_WAIT
TCP straighttoale:10080 localhost:1358 TIME_WAIT
TCP straighttoale:10080 localhost:1360 TIME_WAIT
TCP straighttoale:10110 straighttoale:0 LISTENING
TCP straighttoale:13128 straighttoale:0 LISTENING
TCP straighttoale:18080 straighttoale:0 LISTENING
TCP straighttoale:netbios-ssn straighttoale:0 LISTENING
TCP straighttoale:1329 ag-in-f100.google.com:http ESTABLISHED
UDP straighttoale:microsoft-ds *:*
UDP straighttoale:isakmp *:*
UDP straighttoale:1026 *:*
UDP straighttoale:1028 *:*
UDP straighttoale:1038 *:*
UDP straighttoale:1085 *:*
UDP straighttoale:1086 *:*
UDP straighttoale:1087 *:*
UDP straighttoale:1088 *:*
UDP straighttoale:1089 *:*
UDP straighttoale:1340 *:*
UDP straighttoale:1341 *:*
UDP straighttoale:1400 *:*
UDP straighttoale:1900 *:*
UDP straighttoale:4500 *:*
UDP straighttoale:7000 *:*
UDP straighttoale:ntp *:*
UDP straighttoale:1025 *:*
UDP straighttoale:1900 *:*
UDP straighttoale:ntp *:*
UDP straighttoale:netbios-ns *:*
UDP straighttoale:netbios-dgm *:*
UDP straighttoale:1900 *:*
UDP straighttoale:4344 *:*

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 04 5a 46 5f f6 ...... Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4) - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.6 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.6 192.168.1.6 30
192.168.1.6 255.255.255.255 127.0.0.1 127.0.0.1 30
192.168.1.255 255.255.255.255 192.168.1.6 192.168.1.6 30
224.0.0.0 240.0.0.0 192.168.1.6 192.168.1.6 30
255.255.255.255 255.255.255.255 192.168.1.6 192.168.1.6 1
Default Gateway: 192.168.1.1
===========================================================================
Persistent Routes:
None

Route Table

I'm totally lost looking at the above info, so if you can offer any advice, please do!

Thanks,

- Dan

[Sizz]

Route table looks normal. What router are you using? Some routers don't like it when you allocate a static IP in its DHCP range. Get on your router's configuration web page and note the range. Change the BCS IP to something out of that range (My DHCP range is 192.168.1.100+, so my PC is *.100(DHCP) and BCS is *.2(static)).

If that doesn't work, then go to the command prompt and try to add a route entry manually using this format:

arp -s bcs_ip bcs_mac pc_ip
so for example:
arp -s 192.168.1.2 00-90-55-00-23-21 192.168.1.100
if I remember correctly, the mac address of the bcs is on the sticker.
verify entry with: arp -a

Not sure where to go if that fails. Maybe configure the BCS back to DHCP mode. I'm still unclear about the 'random problems' you had in that configuration. Did the BCS manage to DHCP successfully?

Good luck!

[cartdan]

I'm still unclear about the 'random problems' you had in that configuration. Did the BCS manage to DHCP successfully?

I'll try your suggestions when I get home tonight, thanks!

When I had the DHCP on, I could connect sometimes, and sometimes I couldn't. Not sure if it was the BCS or the network.

- Dan

[gbrewer]

What is the range of IP that you use for your router? Is it possible that the address you assigned to the BCS is outside the range that is recognized by your router? How many PC's do you have connected to your router? When you use DHCP for connection, you may simply be dealing with a new address being assigned to the BCS when it is logged on. (providing you have other PC's on the network that log on and off at various times)

I am going to guess since you have been able to access the BCS in the manner you have explained, it is a range issue. The IP address assigned is outside the range you allowed on your router. Just a guess from the outside looking in.

[cartdan]

I verified that I was allocating a static IP that was in the routers DHCP range. The range was set from 192.168.1.2 to 192.168.1.254. I changed the range to 192.168.1.2 to 192.168.1.60, so the BCS would be out of the range at 69.

Unfortunately I didn't get to test it yet, but will do that first thing when I get home tonight (stupid job always gets in the way).

I'm hopeful that this will clear things up. Will post when I know for sure.

- Dan