I just got a new machine here at work. I am finally going from WinNT to Win2K. It is a Dell P4 3.06Ghz w/ 1Gb ram , integrated ethernet...yada yada. When I got the computer I installed a D-link ethernet card. I am connecting to the company network through the integrated ethernet connection. I want to now connect to my Empeg using the other card and a crossover cable. I installed the card, installed the driver. I set the IP address of the new connection to 10.0.0.1 with a subnet mask of 255.255.255.0. I set the player to 10.0.0.2 with a subnet mask of 255.255.255.0. I set the addressing in Emplode using USB and then I synched. I still can not seem to get Emplode to see the network connection though.

On my home PC I am running WinXP and two network cards, one for my home network and one for my Empeg through a crossover cable with the same addressing scheme and it works just fine. Is there something in Win2k that has to be set that I am missing? Be aware I can still hook up through USB. I am stumped. Ideas? Do I have to fool with the Gateway? I know the Gateway for my Company network is set but, I didn't think that it needs it for such a simple connection.

I forgot to mention that when I unplug the crossover cable from the player, it shows up in the task bar that the network connection is unplugged.

You may need to force your network card in the PC to 10Mbps at half-duplex.

It shows up in Properties as 10 Mbps. Half Duplex? I am sorry I do not understand if that is another setting altogether, or part of the setting the PC to 10 Mbps.

Go into the properties of the network card and you will see something like this:



This screen shot is from WindowsXP, but I think it's the same in Win2K.

I have had problems with auto_config in the past, that is why I always recommend fixing the values specifically.

Dave,

I just set my empeg up here at home using the same method, on Win2K. I ended up using the Specific Address: option to connect to my player with emplode. For some reason, the default Network Broadcast only worked the first time.

When I go into the advanced tab, there are 8 different properties that can be altered.
Early Tx Threshhold
Link Down Power Saving
Link Speed/Duplex Mode
Network Address
Recieve Buffer Size
Wake Up on ARP/PING
Wake up on Link Change
Wake Up using APM Mode

I set the Link Speed/Duplex Mode to "10 Half Mode".
Is that what you are talking about?

Yes.

Emplode still does not find the network connection. I have Find Specific Address checked in options with the address of the player entered as 10.0.0.2. Could it have anything to do with the Gateway?

I don't think it has to do with the gateway.

- Any firewalls installed on your machine?
- Probably you have HiJack installed and it is set on ;@home rather than ;@work ?

Can you ping the player at all?

How do I ping the player?

Okay I typed ping 10.0.0.2 on a command line and got:
---------------------------
Pinging 10.0.0.2 with 32 bytes of data:

Reply from 10.0.0.2: bytes=32 time<10ms TTL128
Reply from 10.0.0.2: bytes=32 time<10ms TTL128
Reply from 10.0.0.2: bytes=32 time<10ms TTL128
Reply from 10.0.0.2: bytes=32 time<10ms TTL128

Ping statistics for 10.0.0.2:
Packets: Sent = 4, Recieved = 4, Lost = 0 (0% Loss),
Approximate round trip times in milliseconds:
Minimum = 0ms, Maximum = oms, Average = 0ms
-----------------------

Now is this good or bad? I am guessing that this means it is seeing the player, correct?

open Win2k command prompt and type:

PING 10.0.0.2 

and you'll get something like this:

Pinging 10.0.0.2 with 32 bytes of data:



Reply from 10.0.0.2: bytes=32 time<1ms TTL=254

Reply from 10.0.0.2: bytes=32 time<1ms TTL=254

Reply from 10.0.0.2: bytes=32 time<1ms TTL=254

Reply from 10.0.0.2: bytes=32 time<1ms TTL=254



Ping statistics for 10.0.0.2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms

If you get lost packets, then there's no ethernet conenction to your player.

I figured that out as soon as I replied. You can see my results in the edited post above. Comparing the results to yours, it looks like I have a good connection and that there is something not configured correctly on the PC. But what?

The player is "There", then. The problem must be in emplode, for some reason. If you don't have a firewall preventing emplode from reaching the player, then probably you should just wait some more? On large networks it may take a while before emplode finds the player, to my experience....

I have a much more base-level question:

Why are you even trying to use two network cards? Why not just plug the empeg into the main hub in each of these situations?

I set the IP address of the new connection to 10.0.0.1 with a subnet mask of 255.255.255.0. I set the player to 10.0.0.2 with a subnet mask of 255.255.255.0. I set the addressing in Emplode using USB and then I synched. I still can not seem to get Emplode to see the network connection though.

Open a command window and type "route print", then post the results.

Peter

Like I said, I am at work and I do not have easy access to the server room with all the hubs for the facility. So, the easiest way to otherwise set up ethernet is a second network card. You are correct,
the best scenario would be to hook it into the main network. The powers at be in my deapartment don't have any problems with me doing things like this as long as my "experiments" stay within the walls of the department...otherwise my boss will have to deal with a crap load of BS from pompous VP's and the like who have no real idea how things actually get done....in other words....a lot of Politics.

I did what you asked and posted below are the results:



Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 0c f1 87 92 e8 ...... Intel(R) PRO/1000 MT Network Connection
0x2000004 ...00 05 5d 50 f9 e2 ...... D-Link DFE-530TX+ PCI Adapter

===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.250 10.0.0.244 1
10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1 1
10.0.0.0 255.255.255.0 10.0.0.244 10.0.0.244 1
10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 1
10.0.0.244 255.255.255.255 127.0.0.1 127.0.0.1 1
10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 1
10.255.255.255 255.255.255.255 10.0.0.244 10.0.0.244 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 224.0.0.0 10.0.0.1 10.0.0.1 1
224.0.0.0 224.0.0.0 10.0.0.244 10.0.0.244 1
255.255.255.255 255.255.255.255 10.0.0.244 10.0.0.244 1
Default Gateway: 10.0.0.250
===========================================================================
Persistent Routes:
No


SORRY ABOUT THE FORMATTING.... IT LOOKS FINE IN THE PREVIEW POST PAGE BUT GETS ALL WHACKED OUT ONCE THE POST IS ACTUALLY MADE. I TRIED MOVING EVERYTHING INTO NICE COLUMNS BUT THEY WILL NOT STAY THAT WAY.

All of your interfaces appear to have 10 net IP addresses. Not shockingly, the subnet mask you've set means both interfaces would be for the same set of addresses, and so you lose.

I suggest using one of the class B local address blocks, instead of net 10, for your private stuff.

10.0.0.1
10.0.0.244

Bingo, your work lan is 10/8 and your Empeg mini-lan is also 10/8. Odds are, when you pinged 10.0.0.2 and it responded, it wasn't your car-player at all!

You'll need to set your Empeg and second network card to a different IP range altogether -- say, 192.168.1.1 and 192.168.1.2.

Peter

Looks like (if I'm reading that correctly) your original network card is already on the 10.0.0.0 network. You can't (generally) have two network cards on the same network.

Configure your new network card to 192.168.x.y, netmask 255.255.255.0 and the empeg to 192.168.x.z, netmask 255.255.255.0

Pick any numbers (1-254) for x, y and z. I suggest x=1, y=1, z=2.

I changed the two addresses earlier to 192.168.0.1 on the PC and 192.168.0.2 on the Empeg to see if that would work and it didn't....even though then I had no idea why I was doing it except to say that I thought it could maybe have some effect. It didn't work when I tried that. But now that you bring it up again, I tried it again and used 192.168.1.1 for the PC, 192.168.1.2 for the Empeg. Changed settings in Emplode via USB and synched. It still only seems to pick up the Empeg on USB. I shut the computer down and even rebooted it. What you are saying makes sense. It should show up. Do any file sharing settings need to be changed or anything of the like?

When I ping the player I get:

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>ping 192.168.1.2

Pinging 192.168.1.2 with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time=16ms TTL=255
Reply from 192.168.1.2: bytes=32 time<10ms TTL=255
Reply from 192.168.1.2: bytes=32 time<10ms TTL=255
Reply from 192.168.1.2: bytes=32 time<10ms TTL=255

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 16ms, Average = 4ms


And when I now type Route Print on the command line it shows like this:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 0c f1 87 92 e8 ...... Intel(R) PRO/1000 MT Network Connection
0x1000004 ...00 05 5d 50 f9 e2 ...... D-Link DFE-530TX+ PCI Adapter

===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.250 10.0.0.244 1
10.0.0.0 255.255.255.0 10.0.0.244 10.0.0.244 1
10.0.0.244 255.255.255.255 127.0.0.1 127.0.0.1 1
10.255.255.255 255.255.255.255 10.0.0.244 10.0.0.244 1
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.1 192.168.1.1 1
192.168.1.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.1.255 255.255.255.255 192.168.1.1 192.168.1.1 1
224.0.0.0 224.0.0.0 10.0.0.244 10.0.0.244 1
224.0.0.0 224.0.0.0 192.168.1.1 192.168.1.1 1
255.255.255.255 255.255.255.255 10.0.0.244 10.0.0.244 1
Default Gateway: 10.0.0.250
===========================================================================
Persistent Routes:
None

Edited for spelling.

Like I said, I am at work and I do not have easy access to the server room with all the hubs for the facility.

Ah, so your problem is... Number of available network plugs at your desk.

Too bad they only give you one plug. When I spec'd the wiring for our local LAN in our new building (well, it was new at the time), I made sure everyone had at least two available plugs, and more for certain offices. Sorry your facilities people didn't have the foresight to do that.

Anyway, you could theoretically solve that by getting a cheap hub and sticking it at your desk, dasy chaining into your corporate network. But since you've already got the second network card installed, I guess the best thing to do is just continue diagnosing the problem with that card.

Have you got the specific address box filled in? Or are you still trying to find the empeg with a broadcast? I can't remember whether broadcast discovery works with multiple network cards.

The advantage of having it on a seperate interface is that it's totally isolated from the corporate network. Some places are kind of touchy about what you plug into the network. It also stops coworkers from messing around with it.

I agree that's an advantage. I was just trying to suggest simplifying the connection scheme to get it working at all in the first place.

I think most employers that are touchy about what gets attached to their network will also be touchy about installing extra network cards in workstations.

--Dan.

Good point. Getting it all working and then shifting it over would eliminate a lot of possible problems.

I think most employers that are touchy about what gets attached to their network will also be touchy about installing extra network cards in workstations.

They may not if it was a usb nic or something non-intrusive. Although, some might even get antsy about the one extra set of drivers.