Cannot connect to lobby
Speaking to the issue of fowarding ports being a security problem, in general no, especially not for these ports. In order for it to be a security issue, something has to be listening on your end on the forwarded port. In this case only older dplay games should be listening, and if they do try and connect on one of these ports, 'alleg' isn't hackable in the sense they cannot connect to it and make it do 'something bad'.

DOG PROPERTY LAWS:
2. If it's in my mouth, it's mine.
[unless it tastes bad, then it is yours.]
I don't worry at all about opening ports because, as Dogbones says, there has to be a program on your machine listening for it ... and that program needs to be vulnerable to pentration.
As for what ports to forward...
Darklight, I can't tell how your network is designed, but here is a shot ...
Internet -> Modem -> PC
Forward the Modem ports to your end-PC.
IF you are using connection sharing it gets complicated.
Internet -> Modem -> ICS PC -> Game PC
Forward the Modem ports to the ICS PC and then forward the same ports from the ICS PC to the Game PC.
Just think of the ports as a pass-off. If you can hand the packets to the Game PC directly .. do it. If you have to hand them to a 'middle' PC ... do that first and then pass from the 'middle' PC to the final PC.
As for what ports to forward...
Darklight, I can't tell how your network is designed, but here is a shot ...
Internet -> Modem -> PC
Forward the Modem ports to your end-PC.
IF you are using connection sharing it gets complicated.
Internet -> Modem -> ICS PC -> Game PC
Forward the Modem ports to the ICS PC and then forward the same ports from the ICS PC to the Game PC.
Just think of the ports as a pass-off. If you can hand the packets to the Game PC directly .. do it. If you have to hand them to a 'middle' PC ... do that first and then pass from the 'middle' PC to the final PC.
<Note: We might have a new version out in 1-2 weeks that will fix this problem, but ...>
We must be missing something, because this should work ...
Can you post 2 screenshots to start...
1) The router configuration screen where you have the port forwarding rules
2) The output of
Start -> Run -> 'cmd' -> 'ipconfig' on your PC
We must be missing something, because this should work ...
Can you post 2 screenshots to start...
1) The router configuration screen where you have the port forwarding rules
2) The output of
Start -> Run -> 'cmd' -> 'ipconfig' on your PC
http://www.hccmagazine.nl/index.cfm?fuseac...en&id=46729
If you scroll down to the end you can see a picture about the NAPT forwarding.
As for the cmd thing:
Windows IP configuration
Ethernet-adapter LAN connection:
Connectionspec: LAN
IP adress: - (not needed)
Subnetmask: - (not needed)
Standard gateway - (router IP adress).
If you scroll down to the end you can see a picture about the NAPT forwarding.
As for the cmd thing:
Windows IP configuration
Ethernet-adapter LAN connection:
Connectionspec: LAN
IP adress: - (not needed)
Subnetmask: - (not needed)
Standard gateway - (router IP adress).
If I am reading the screen shots correctly you can only forward 1 port at a time?
e.g. 2300 External
2300 Internal
2301 External
2301 Internal
If that is true then you will need to forward 2300 and 2301 (UDP and TCP) AND run a program called DXport to force Allegiance to use ports 2300 and 2301.
Other than that ... you should be good.
If that doesn't work I ask you patience until we get the new version of Allegiance out.
e.g. 2300 External
2300 Internal
2301 External
2301 Internal
If that is true then you will need to forward 2300 and 2301 (UDP and TCP) AND run a program called DXport to force Allegiance to use ports 2300 and 2301.
Other than that ... you should be good.
If that doesn't work I ask you patience until we get the new version of Allegiance out.