No, you don't want to do that. The idea of an IDENTITY field is that it is a unique identifier of a row
within a table - and multiple tables will have different rows with different identities.
The only time you would want or need the same row identity for each row in two different tables is when you have badly designed your system, creating two tables where one is needed. The solution to that is simple: make it one table. If you don't, then the multiuser aspect of SQL Server is going to bite you - and badly - when you get to production.
If there is intended to be a correlation between the two tables, then that's simple: each table had a separate ID value (which doesn't have to be the same) but one table has a column which contains a Foreign Key relationship with the other and which contains the ID of the row in the second table:
CustNames
ID INT, IDENTITY
CName NVARCHAR(255)
ID Cname
1 Jones Designs
2 Smiths Instruments
3 Joes Chips
CustAddresses
ID INT, IDENTITY
Addr NVARCHAR(1024)
CID INT, FOREIGN KEY to CustNames.ID
ID Addr CID
1 Smiths House, Smiths Lane 2
2 JonesTown 1
3 High Street, Potato Town, Idaho 3
See what I mean?