Card sharing help

[dssexpert]

OK. I am a little confused here. I was assuming auxshare wasnt only to pretend to be an auxed card, but was also set up to share 1 aux card between multiple instances of st19xl.

I cant figure out how to set it up to do that...

My auxed card is on COM9
My Dish1 is on COM2
My Dish2 is on COM4

[dssexpert]

I set up superforge instead. Kind of pointless to use a server/client setup on the same PC, but its working....I'd still like to figure out how to get auxshare to work - or what the point of using it is if you have an aux card...

[Fignewton]

Auxshare was developed for those that do not have a card for ST19XL to use. (A cardless alternative to CEMU.)

[eyeless]

Auxshare actually does allow the sharing of an Aux card between 2 receivers, the directions to do so are explained in the readme included in the package. I would rather use superforge myself as you can also share your Aux over your LAN as well as the Internet.

Also when you are creating you bat files for Superforge you can use the "title" command to name your dos windows. They are easier to keep track of that way, for an example of my Superforge server bat file here it is:

title SERVER
SUPERFORGE -com=2 -port=xxxx (removed port #)


This names the dos window "SERVER" instead of "c:\windows\...etc"

[dssexpert]

Eyeless, actually in the readme it specifically says the following

- Version 0.1.4 -
...
- Added support for smartcard again, but this is
still fully untested as mapcalls aren't in use
at the moment. I will add the ability to share
the card between multiple clients when there is a
need.

Up to 0.21 it does not mention the ability to use auxshare with multiple clients, and actually states that it isnt even fully tested with real smartcard support....so it looks like auxshare is more aimed toward cardless.

I added a USB to Serial adapter on my PC and set up superforge, so right now it looks like superforge is the best bet and working good.

I wonder if superforge will work over WAN? I cant see why not if router and port forwarding are set up properly...

[badbrains]

I wonder if superforge will work over WAN? I cant see why not if router and port forwarding are set up properly...

Superforge works over WAN. I'm connected to the superforge server over internet then through my wireless router, then to my client pc wireless.

[eyeless]

Didn't realize Auxshare was no longer supporting the sharing of an Aux for multiple IRDs. I have been using superforge since its release and has been working more or less %100. There was a recent freezing issue that the newest version fixed for me. I have 2 people sharing my Aux over the Internet, both in the same province, but both are using different ISPs and can share with no problems.

Sort of changing the topic, anybody know the limit to number of shares per Aux card using superforge? I have 3 shares locally (2bev and 1dish) and 2 over the internet (both bev) with no problems sharing one card.

[badbrains]

I have heard someone tested 10 irds, all of them over internet, and they worked smoothly.

[eyeless]

Good to know, thanks

[chemlab]

Version 0.1.5.2 should support far more clients than previous versions.

[sledmanjones]

Can any of you guys give me some tips on sharing across the net thru wireless routers.I have a wrt54gs at the server side and at client side a wrt54g,and I can't get the client to see the server.The server is located on my home LAN,with 2 laptops,and 2 desktop,including the EMU PC.Each PC has a static IP starting at 192.168.1.100.The client side router has only two PC's,both with static IP's as well.I have port forwarded the port I use with Superforge(5757) to each PC(server and client)My server.dat file has the Current IP address given to my router by my ISP,the port to use(5757) and the username and password I use.Can anyone give me any insight into what I'm doing wrong?Or what you did right to make your setup work?

[rg6a]

Can any of you guys give me some tips on sharing across the net thru wireless routers.I have a wrt54gs at the server side and at client side a wrt54g,and I can't get the client to see the server.The server is located on my home LAN,with 2 laptops,and 2 desktop,including the EMU PC.Each PC has a static IP starting at 192.168.1.100.The client side router has only two PC's,both with static IP's as well.I have port forwarded the port I use with Superforge(5757) to each PC(server and client)My server.dat file has the Current IP address given to my router by my ISP,the port to use(5757) and the username and password I use.Can anyone give me any insight into what I'm doing wrong?Or what you did right to make your setup work?

Interesting set up you have there and can't help you but my Cable outfit makes Dave look like a Philanthropist. I had to Clone the MAC, Bastards throttled me right down after finding out I had a router <same as yours>.

Did you do that, perhaps you should give it a try, good luck.

PS router was only used for home internet networking not anything else, Bastards want Subs to Rent one for $10/month.........yeah sure..when pigs can fly!

[badbrains]

Can any of you guys give me some tips on sharing across the net thru wireless routers.I have a wrt54gs at the server side and at client side a wrt54g,and I can't get the client to see the server.The server is located on my home LAN,with 2 laptops,and 2 desktop,including the EMU PC.Each PC has a static IP starting at 192.168.1.100.The client side router has only two PC's,both with static IP's as well.I have port forwarded the port I use with Superforge(5757) to each PC(server and client)My server.dat file has the Current IP address given to my router by my ISP,the port to use(5757) and the username and password I use.Can anyone give me any insight into what I'm doing wrong?Or what you did right to make your setup work?
If I'm reading your question right you are trying to share over a LAN, not internet.
If that is the case, there is no need to use any ip's other than the local 127.0.0.1

So your server.dat file should look like this:
127.0.0.1,(open router port),user,password

This will allow superforge to run locally on your LAN.

edit: I see now after rereading your post that you are sharing over the net. Don't see how I missed that....

[badbrains]

Just a thought, have you edited the users.dat file on the server pc to match the servers.dat file on the client pc?

[eyeless]

127.0.0.1 would allow a computer to connect to itself, that is if you were running both the server and a client on the same computer. If you are sharing between two computers on a LAN you would have to use the assigned internal IP (usually in the 192.168.xxx.xxx range)

If sharing on the Internet you will have to connect to the aux server using the IP address assigned to the router that the server is connected to, and then correctly map the port to point to the internal IP of the server. Make sure any firewall installed on the server is also updated to allow connections on your chosen port.

When troubleshooting I have been using hxxp://canyouseeme.org simple website, automatically grabs your IP, you enter the port in the box and it will tell you if it can connect to your service or not.

[badbrains]

You're right, eyeless. I was comparing a known working setup on a friends machine, which doesn't apply in this case. My bad...
Router assigned addy must be used to work over LAN and ISP assigned addy must be used to communicate over internet.

[sledmanjones]

Thanks for all your tips guys,I'm sure others will benefit from them as well.I got this setup going.Turns out it was a setup issue on the router on the serverside.The port was not forwarded properly to the right PC on the LAN.Once I was able to verify it was open using the webpage that eyeless suggested,the rest was very straightforward.Watching it now,
Thanks again