Forums Connection Issues Connecting to two different severs

When i try and connect to two different severs I have a problem with the second sever i connect to it connects several times to the same sever and room. I am using this in my remotes
on *:START: {
server 1
server -m sever 2}

then in my perform list on connect i have this.
/msg NickServ IDENTIFY password
/join #room 1
/join #room 2

Is there something here causing my problem

on *:START:{
server blah.blah.net -j #room
server -m blah2.blah2.net -j #room
}
Possibly!

Hi!

Each connection to an IRC server has its "ID", $scon and its alias /scon
mIRC's help file is really helpful: /help $scon

The -a switch on /scon performs the command on all connection ids instead of looping each one.

So here's a script:
/scon -a /alias

and your /alias {
/msg NickServ IDENTIFY password
/join #room 1
/join #room 2
}

No no, you do NOT "/msg NickServ IDENTIFY password" on every connection.
Also it is much safer to use: /nickserv identify passwd

/nickserv is not a valid command on every server...
You could check for NickServ's whois or /msg [email]nickserv@services.host.of.your.server[/email] if it is supported.

/nickserv is supported on most networks (that have nickserv), if it isn't you will get a "421 Unknown command" and thn you know to use the alternative.
Whether you use "/nickserv" or "/msg [email]nickserv@blahblah"[/email] , the main point of my post was that it should NOT be part of a "/scid -a" routine.
BTW "/scid -a" will fail if one cid is not connected, (if cid1 is not connected, or cid2 isn't and you have a cid3) "/scid -at1" for all connected cids.

I agree with Iori. In fact, I wouldn't have any form of the identify command put in remotes or the Perform section for top password security.

The biggest network with NickServ is DALnet and /msg NickServ is not supported (due to security reasons).

My 2 cents.

Regards,